jynelson

6 ms·

1.
by jynelson 9d ago
> What is it? Can it be this autonomous terrifying entity or can it not be? the difference between attack and defense is that attacks can be throwaway code. it's much easier to let an llm hack out a prototype than to get it to build
2.
by jynelson 1mo ago
that is not what the policy says. it says "authors must disclose", "reviewers don't need to play detective", and "if a reviewer is not sure whether a post is LLM-created they should handle it privately, consult
3.
by jynelson 1mo ago
yes. there's a reason there's exactly two things in the policy that are marked as moderation consequences and they're directly next to each other. "no harassment" doesn't work if people are paranoid that any PR
4.
by jynelson 1mo ago
you're very welcome!
5.
by jynelson 1mo ago
> New contributors do not have community connections. I don't know any rust-lang/rust reviewer. > What is the correct procedure for this? there's a #llm-mentoring [0] Zulip stream linked in the dev-guide [1]. [0]: http
6.
by jynelson 4mo ago
it says “that’s right” in bold red cursive font. i know what the policy says, i wrote it, you nincompoop.
7.
by jynelson 4mo ago
https://i.imgur.com/129TCNu.png
8.
by jynelson 4mo ago
if an LLM says "I can't open a PR automatically until you solicit a review from a maintainer", i think that's good actually. likewise for proactively following the rest of the rules.
9.
by jynelson 4mo ago
i'm not a man.
10.
by jynelson 9mo ago
> Ultimately that's something the hook author has to solve, not the framework which runs them. correct. i'm saying that hook authors almost never do this right, and i'd rather they didn't even try and moved their chec
11.
by jynelson 9mo ago
this completely breaks `git add -p`.
12.
by jynelson 9mo ago
the pre-commit framework does not abstract away “hooks shouldn’t be run during a rebase”, nor “hooks should be fast and reliable”, nor “hooks should never change the index”.
13.
by jynelson 9mo ago
i think you would be interested in demoscene, it’s about exactly this thing: making art out of extremely harsh requirements.
14.
by jynelson 9mo ago
tbh i think you just hate trans people but you're afraid to say it directly
15.
by jynelson 9mo ago
> Software should be an engineering field, which exists to help humans, not as some personal art project for your self expression it makes me sad that you see these things as somehow in conflict with each other :(
16.
by jynelson 9mo ago
> it's often that the amount of time i've spent thinking about something (a lot) is totally disproportionate to the time i spend typing my thoughts up (a little) oh, this is a really good way of putting it! that’s exactly what
17.
by jynelson 10mo ago
you could build an emacs frontend for this model! the thing i am trying to describe is “getting out of the box”. imagine a terminal session that is shared between emacs, iTerm, and a mobile phone ssh’d in over the network, that’s my vision.
18.
by jynelson 10mo ago
omg i've wanted something like shelter for literal years it "cheats" a little because it requires the underlying filesystem to support snapshots but it's still really really cool, thank you for the link!
19.
by jynelson 10mo ago
> Great, now you just need to build and maintain shims for every tool in existence, force your users to use your own custom tools that support these features, and ensure that everything interoperates smoothly. Yes, this is the work. htt
20.
by jynelson 10mo ago
whoa this looks fascinating, i've never heard of it before! thank you for the link :)
21.
by jynelson 10mo ago
this is really cool omg! i didn't know that, i'll do some research. one of the strange things to me about the terminal landscape is how little knowledge sharing there is compared to other domains i'm familiar with. iTerm has
22.
by jynelson 10mo ago
i would describe the main idea of the post as opening up the data model of the terminal. the list of wishes are an example of things you can build once you've done that, not the primary reason that opening the data model is useful.
23.
by jynelson 10mo ago
yeah! so i somehow forgot to include this in the post, but one of the thing i would want as part of this is tab complete that integrates with the shell, essentially it would make an RPC call (in the step 3 sense). there’s things that work l
24.
by jynelson 1y ago
I think so, yes. If you remove any of the things in the “core” I mention in the post, the language hangs together much worse even though it’s smaller; enums without pattern matching is a simple example. I’m not just saying that I want to
25.
by jynelson 1y ago
I think we are using different meanings of the term "cohere" and I am not sure how to reconcile them. I agree that Rust with async is a more useful language. I don't think being useful implies anything about how coherent a la
26.
by jynelson 1y ago
note that RAII in Rust is not as simple as calling drop() at the end of each lexical scope, because of drop flags.
27.
by jynelson 1y ago
you were reading very closely, well done. yes, that is my claim, Rust was smaller and cleaner before async and const. I was so indirect about it because many of my best friends work on those features and I wasn’t sure how to word it. fortun
28.
by jynelson 1y ago
> I understand the point they’re trying to make, that being that rust forces you to explicitly deal with the complexity of the problem rather than implicitly This is not the point I am trying to make.
29.
by jynelson 1y ago
I think I disagree that you can have a Rust program that doesn't use all these concepts, at least outside of very basic tutorial material. You will very very quickly run into compiler errors that mention them the second you write you
30.
by jynelson 1y ago
no. the JS program has obvious syntax bugs that TS wouldn't compile. commentors above are right that I was just lazy (ty for the callout, I have since fixed the JS program).

More ›