avgcorrection

6 ms·

1.
by avgcorrection 3y ago
I’ll try to do better in the next life.
2.
by avgcorrection 3y ago
> But go ahead and use the FFI and things aren't so rosy. Usually the GC can cooperate with allocated memory from the other side of the FFI, but this requires care and attention to detail, or you get memory bugs, and just like that,
3.
by avgcorrection 3y ago
What was difficult about what I wrote?
4.
by avgcorrection 3y ago
> Back to TCP. Earlier for the sake of simplicity I told a little fib, and some of you have steam coming out of your ears by now because this fib is driving you crazy. I said that TCP guarantees that your message will arrive. It doesn’t,
5.
by avgcorrection 3y ago
Ok. That could work if you found a group of people who are interested in such an all-in-one package. Gitlab is apparently working on a sort of cross-forge protocol (probably motivated by connecting Gitlab instances) and it seems that some G
6.
by avgcorrection 3y ago
Amendment: I just found out that I do have at least one use for git-stash, which is when I am stuck in the middle of a rebase somewhere and made an edit intended for another point (commit).
7.
by avgcorrection 3y ago
And Fossil is an entirely different VCS. What’s the alternative? That at least N projects cooperate and agree on a common design before they do the implementation? (Then maybe someone can complain about design-by-committee.)
8.
by avgcorrection 3y ago
My comment was totally unclear. By primitive I mean that it scales from very primitive operations (just snapshot) to supporting high-level workflows (refactoring, testing, verifying). And by primitive I mean that I want to be able to comm
9.
by avgcorrection 3y ago
IMO you don’t need anything more than commits. The by-hand is writing WIP in the commit message. If that is an inconvenience then I’ll make a commit alias. The index + commits is flexible enough. The stash concept is not needed for me. See:
10.
by avgcorrection 3y ago
I think that you (like me) prefer to use commits in places where many others prefer to stash. Personally I think the stash command is too primitive to bother with for all things except maybe an push+pop that happens within half a minute. An
11.
by avgcorrection 3y ago
https://news.ycombinator.com/item?id=39357068 The submitter unhelpfully didn’t mention the name in the title.
12.
by avgcorrection 3y ago
You don’t have to interpret it as you-always-do-this. Just sometimes you want a worktree (or clone): maybe the bug fix needs to be applied to an old, old release which would invalidate all the indexes in your project. So then you can make
13.
by avgcorrection 3y ago
“Not in a position to commit” in Git makes as much sense as “not in a position to save the file” (in your editor) in 2024. Git is in a sense a primitive tool: only about snapshotting, not about high-falutin things like “passes the tests”, “
14.
by avgcorrection 3y ago
This is the way. Just commit. You can undo it later or whatever, but at least it’s there. Just one concept instead of (1) commits (2) stash (3) oh these changes, eh, I don’t know what to do with them... let’s think about it after lunch.
15.
by avgcorrection 3y ago
> The thing that annoys me about worktrees is that you can't have two checked out to the same commit at the same time Checking out the same commit is fine. You just can’t checkout the same branch. This is not a problem for me beca
16.
by avgcorrection 3y ago
The first big thread on GitButler (recent) left me scratching my head. All the material with jargon like “virtual branches” just left me confused. It was like jumping into a how-to on why choose a Ferrari without first understanding what a
17.
by avgcorrection 3y ago
Maybe there could be some utility for a decently general Graph type that can be used for high-level testing and verification. Maybe you could implement your efficient graph per-problem and then validate it with a more high-level and declara
18.
by avgcorrection 3y ago
The private key that I would hypothetically sign commits with? Then signing commits is compromised too. I’m not sure what point you’re making. On the other hand if I don’t sign my commits then any signed commits (from my stolen private key
19.
by avgcorrection 3y ago
It doesn’t seem hard to attribute 1/5 commit in a PR to another person. Then you publish it, no one checks out the individual commits (because that’s how forges are like in my experience), and it gets merged because the 2,000 line diff
20.
by avgcorrection 3y ago
Why are you afraid of identity theft in this context?
21.
by avgcorrection 3y ago
I am also able to pee in my office mate’s coffee cup. What should we do to mitigate that threat model?
22.
by avgcorrection 3y ago
Completely correct that you should have a reason for signing something which goes beyond the vacuous “why not”. In my own work, the surrounding context is sufficient verification. By the way: patch attestation [1] is perhaps somewhat relate
23.
by avgcorrection 3y ago
Report it.
24.
by avgcorrection 3y ago
You struggle to imagine a programmer passing a value of the wrong type to a function?
25.
by avgcorrection 3y ago
“Enumeration” according to a handy dictionary: “the act or process of making or stating a list of things one after another” I am—for some reason—reminded of philosophers who go looking for metaphysical problems, disputes, etc. where there
26.
by avgcorrection 3y ago
It’s funny to emphasize the vibes of a language contra other ones when you’re supposed to be on the supposedly pragmatic side. Haskell and Rust are popular on “message boards”? Better not mention them among my peers and risk my blue collar
27.
by avgcorrection 3y ago
Author actually replies that Go, Java, Rust , Swift are options depending on the context, and that general considerations like security are relevant as well. But whatever helps you grind your axe!
28.
by avgcorrection 3y ago
No to all of the above. I already made the point that a search engine can just search for the given string and not muck about with user-specific data… that’s what the user expects a lot of the time.
29.
by avgcorrection 3y ago
The author considered the Go pattern for “enums”. Found it lacking. Made their own code generator for their preferred pattern. That’s two options. What are the others that are meaningfully different? You have to be able to deal with simple
30.
by avgcorrection 3y ago
The best-case IMO is a test suite where writing the test is almost as easy (or maybe easier?) than doing the equivalent manual test. The test code is maybe 2–4x longer than the change. The worst case is… arbitrarily bad, to the point of bei

More ›