I don't think they're wildly different purposes. They're the same purpose (to set shell settings) with different scopes (all users, one user, interactive shells only, etc.).
Most will at least want something like https://brew.sh/ to get you current versions of standard Linux utilities rather than the bundled ones and then maybe even set up a separate profile in your terminal of choice (iTerm2 is a great option as well) which defaults to using them so you don't break normal system usage which assumes the built in utilities.
Even then, if your use case requires using standard Docker images, assumes certain features of the kernel, or assumes common distro environments rather than just you wanting a posixy feeling terminal you'll still need to run a Linux VM in the background.
The "LLMs shouldn't be writing code" take is starting to feel like the new "we should all just use No-Code."
We’ve been trying to "build a better layer" for thirty years. From Dreamweaver to Scratch to Bubble, the goal was always the same: hide the syntax so the "logic" can shine. But it turns out, the syntax wasn't the enemy—the abstraction ceiling was.
Pretty sure santa works east-west, starting at the international date line. He stretches Christmas day into 48 hours. This is how he can do so many deliveries in a single date.
In that case, the code is obviously temporarily commented out, but go's formatting will make it so that if you comment it out like that, fmt, and then uncomment it and forget to re-add the parens, you get shot in the foot.
I've hit that far more times than it's uhh... I dunno, I guess removed parenthesis I didn't want? I don't write them if I don't want them.
FWIW, in that scenario, for the reasons you've called out, I would normally dupe the if line and comment the original one for reference. Mind you, none of that would ever get committed, but for a temp local change it's fair game.
go is generally hostile to temporarily commenting out code. The if syntax issue you call out is just one aspect. Another is the inability to have unused variables.
I love RDP! It really is an impressive technology. I work in-office somewhere, and when I'm on campus, RDPing into my desk laptop from a conference room client has native performance, with audio even.
reply