My favorite feature is the built-in distinction between what's mutable and what's immutable in my history. I can freely modify any commits I make locally without issue, since no one else would be able to depend on them, but if I push something or fetch it from a coworker, I have the safety of not needing to be careful when doing the equivalent of an amend or rebase because it will fail with an error telling me to use a flag to bypass the immutability protection if that's what I actually want.

Not having to stage changes in lieu of them automatically getting picked up was a bit of a learning curve for me, but now that I've gotten used to it I like it a lot better and I don't think I could go back. The equivalent of the reflog pretty much always has my changes in it if I accidentally lose them without manually saving due to the snapshotting, and I have no need for a stash because commits and branches are essentially just recording a checkpoint rather than being things that feel "heavyweight".

As an added bonus, dealing with conflicts is a lot less annoying because each commit records its conflicts separately, so fixing them doesn't require doing a stateful pipeline of changes in a big rebase; I can just do them piecemeal, in any order I want, and even just check out other stuff and work on them before coming back later if I feel like it.

I was "that guy" who would sometimes have coworkers come for help with git problems (https://xkcd.com/1597/ alt text). I've forgotten most of that knowledge (and all of that muscle memory) and didn't have to learn nearly as much to replace it with the ability to do a lot more with a lot fewer mistakes.

I didn't even realize those were recent! The first time I tried to look for how to use worktrees in jj, they were already available

They also started developing Fleet several years back and made a few alpha releases, only to shutter it before it ever was ever fully released for reasons that essentially seemed to boil down to "we want to focus on our core IDEs instead, which didn't really explain what changed. I was interested in Fleet, so at this point I can't help but be skeptical of anything new they've done since then because it's not clear to me why the same logic for discontinuing Fleet couldn't apply to pretty much anything else.

Fleet was tragic. I was so excited for it but it was a perpetual WIP.

I suppose they were in a tough spot regardless though. They started developing it before the AI age, so they would have to pivot either way.

Many of the improvements and refreshed design were "backported" into the traditional IDEs.

And fleet was made to attract the VSCode generation, who they were starting to lose new user momentum to. But VSCode is no longer the biggest threat.

Part of their schtick is wearing those costumes right? So you don't even know who's performing. The only song of theirs that I know is a collab with a different singer and has a guitar part from Niles Rodgers, so while they probably do have some impact on the music, it's not clear to me how one would be able to tell this hasn't always been the case.

I don't know how you can judge them knowing only one song (one of their worst).

Check their first albums, the more recent stuff they're most famous for in America is just pop crap.

which actually makes the hypothesis that the members changed credible and relieving

This logic would work just as well to ban all mentions of automatic transmission because some people complain that they lost their love of driving once they stopped driving manual. If the complaints are annoying and low-effort, you could just ban the complaints.

Just quiz any of these AI detractors on pure asm + CPU implementation details. Oh what's this? You're writing this in Rust? Can you please tell me how the compiler optimizes this code and what assembly will it produce. Oh what's that, you can't do it? Well, it's obviously because you're not a true engineer™ and you're relying on the slop your compiler gives you.

That seems completely unrelated to what I was responding to and what my response was. All I said was that the one specific rationale in the parent comment seemed flimsy to me; I didn't claim anything about other potential rationales.

Yeah, even when the choice itself might be exempt from critique, stating one thing and then doing another surely isn't. Misleading posturing which can't be proven to be dishonesty but is impossible to differentiate from it seems surprisingly common for reasons I can't wrap my head around.

This happened years ago with the V programming language making a bunch of claims about the existing feature set that were not accurate and future roadmap that did not at all reflect how things went down, and it was all very bizarre and seemingly avoidable if the developer were truly committed to communicating better.

Another development process this reminds me of is the development by modders to port Oblivion to the Skyrim engine. After maybe a decade, the developers made a huge deal at the end of 2024 that they were going to finally release by the end of 2025 and made a lot of noise about it, but by the fall when no more details had been announced, someone asked in Discord about it and the lead developer directly said that it was not going to happen, with an announcement that it was "delayed" to 2026 not getting made until after people posted screenshots of this. We're now in October of 2026 and it's not clear it will be out this year, but trying to give feedback on the communication gets construed shouted down with exhortations to "let them cook". As far as I can tell, a large number of people seem to think that a suggestion that it's fine for the developers to just not keep announcing when things will be done so that they can take as much time as they want without confusing people is synonymous with telling them they need to release immediately.

I have no clue how common an experience this is, but I quite literally get goosebumps when listening to music sometimes if it inspires strong enough emotion for me. I mentioned this to my friend who I played in a band with once, and later when we were listening to something I really liked I held up my arm to show him, and he was shocked because I guess he thought I did not mean literally literally. The hair on my arms genuinely stands up at the end and produces goosebumps purely because of what I feel when listening to music that resonates strongly enough with me; some sections of some songs produce it fairly reliably if I haven't listened to it recently.

> The sensation can occur as a mildly to moderately pleasurable emotional response to music

If goosebumps are only "mildly to moderately pleasurable", I really need to know what kind of music the author listens to!

TIL! Thanks for the reference

This happens to me all the time! I'll be in the car with my wife and a song I really like will come up, and the section hits and I'll say "Goosebumps!" and show her my arm. She also did not believe me until I physically showed her.

They are often songs that are attached to important emotional events in my life, sure, but there are also songs that come out of nowhere and still give me goosebumps. Some things are just that moving!

Same for me; the frisson at particular passages of a song or piece is almost completely predictable. There might be a few dozen such passages for me; I haven't really thought about it.

There are also certain frequencies you can use to instill fear in people subconsciously.

How would you even know whether you knew the facts? It sounds like what you knew was more than just consistent with there being no embargo, you were explicitly told there was no embargo. After a certain point, there's a limit to how far up the chain any of us can be expected to follow the logical chain of what we genuinely think are true, and this doesn't seem like a glaringly obvious case where you were being reckless.

We're all (well, I guess not all, but the group that's worth caring about, and I hope it's at least most) just operating the best we can on the information we have and trying to make decisions based on that. As long as you're acting in good faith on information that you had genuine basis for believing is true, it seems like it would be unreasonable to expect someone in your situation to somehow intuit that you were given false information or grossly misunderstood what sounds like a pretty straightforward declaration of fact from someone you didn't have any reason to doubt.

At the risk of some armchair paycholoanalysis because it does seem like you genuinely feel some guilt over this: I can emphathize feeling guilty about the outcome of an action that in a vacuum would not have been hard to make differently, but my experience is that those of us who have a nasty habit of beating ourselves up over things when we really don't have much blame will often recognize when on the other side that it would not be fair to hold someone else to that standard. I struggle a lot with how sometimes knowing something is true doesn't always make it feel true, and even though hearing someone else saying it doesn't magically make it all better, I still think it's valuable to hear it from someone else, so if I happen to be right about how you're feeling, nothing about all of this is your fault, and to the extent that you're able to, try not to beat yourself up over your misfortune to get caught in the middle of all this due to circumstances that realistically were outside your control.

I read something a while back about curse words more commonly using hard, visceral consonants because it's a lot more satisfying to say them in anger or frustration. Really hitting the end of the f-bomb or the beginning of "crap" feels better than saying something like "aw, jelly belly". Even something like "gosh" instead of "god" just doesn't feel as satisfying.

None of this is scientific (at least, not my attempts to describe it), and I don't have a good explanation for every swear or epithet, but I don't think it would be as satisfying to say "that's lubu!" instead of "that's caca!"

Some "soft" sounding words can feel pretty insulting too, like shush :)

Yeah, this is far from a hard rule, and more just a general trend that seems like it might bear out statistically, but I don't recall the source where I heard it from, so it's possible that it was not rigorous.

Sounds like we need a sequel to https://xkcd.com/378/