The biggest issue for me was that 3rd-party config broke a few times; I think carapace
(which I no longer use anyway, for other reasons) was a major one.
I think that's fine; I don't usually orphan background jobs, but I do relatively often have reason to have them while I do something else. And relying on pueue
for more complex uses seems more than reasonable.
I didn't realize Nu had gotten any form of job control; that was one of the limitations that forced me back to a traditional shell last time I tried it.
Looks like they're still making frequent breaking changes, though, which was another thing I found difficult to manage.
They explained pretty clearly that they use Linux exclusively for work.
Nah, this is society if we move past needing so many passwords. Passkeys, federated logins, and one-time login codes are all preferable.
So...like an old fashioned camera iris?
All the others are not very butthole-ish, though.
There are definitely more experienced programmers using it. I can't find the post at the moment, but there was a recent-ish blog post citing a bunch of examples. [edit: found it: https://registerspill.thorstenball.com/p/they-all-use-it ]
Personally, I don't use AI much, but I do occasionally experiment with it (for instance, I recently gave Claude Sonnet the same live-coding interview I give candidates for my team; it...did worse than I expected, tbh). The experimenting is sufficient for me to recognize these phrases.
It's not in C, if that's what you mean.
It's a "stream manipulator" function that not only generates a new line, it also flushes the stream.
None of the features discussed are aesthetic only.
Nope. It links to an explanation of what that poster is:
This is the UNIX Magic Poster, originally created by Gary Overacre in the mid-1980s and published by UniTech Software.
I feel like we're talking past each other. My impression was that 30% towards your living situation is a pretty decent target; what would you expect the percentage to be?
Okay, what I meant was, is rent taking 30% really indicative of a low standard of living?
Rent eating 30-40% of your income is extremely normal, isn't it? Or is that only true in the US (where it has recently become much more than that for many people)?
Lots of acronyms no longer stand for anything due to losing their original associations. LLVM, AT&T, SAT (the test, not the programming problem), etc.
Probably moreso for expressing the opinion so strongly without actually knowing any of the three languages.
Edit: I'm just guessing why a different comment got downvotes. Why am I getting downvotes?
Doesn't the first edition use K&R style parameter lists and other no-longer-correct syntax?
If you mean the box at the top, with "Larger Text", "Default", and "More Space", mouse-over shows a resolution spec. Is it actually just scaling "as if" the screen had the given resolution?
Even so, I can understand how a Mac user would be confused by this and expect the equivalent feature in a different OS to be called "resolution".
Based on the headline, they've probably maladapted to Mac OS, which doesn't actually have a scaling setting.
(This is somewhat baffling to me, since Apple clearly cares a lot about their display hardware and about having good screen resolution.)

Small Data (a new KRAZAM video)
YouTube Video
Click to view this content.

Who's working on a "smaller Rust"?
Almost five years ago, Saoirse "boats" wrote "Notes on a smaller Rust", and a year after that, revisited the idea.
The basic idea is a language that is highly inspired by Rust but doesn't have the strict constraint of being a "systems" language in the vein of C and C++; in particular, it can have a nontrivial (or "thick") runtime and doesn't need to limit itself to "zero-cost" abstractions.
What languages are being designed that fit this description? I've seen a few scripting languages written in Rust on GitHub, but none of them have been very active. I also recently learned about Hylo, which does have some ideas that I think are promising, but it seems too syntactically alien to really be a "smaller Rust."
Edit to add: I think Graydon Hoare's post about language design choices he would have preferred for Rust also sheds some l