AFAIK, being a flexible JIT compiler (for C-like languages, not Java) was a large part of the idea. The pivot to static compilation only happened "accidentally" in the first few years until the by then pretty broken JIT part was officially removed. Correct me if I'm wrong.
For most of these, invention wasn't even the right word. An invention is usually a new technology that solves a pre-existing problem. Most of Steve Jobs' "inventions" were just product development.
I'm sort of OK with calling the iPhone an invention because it was a big improvement in several areas at the same time, but apart from that?
From my experience, Kubuntu barely changes anything about KDE these days, and that's a good thing, too. I compile my own KDE on my usual machines, but I also have stock Kubuntu on one, and it's pretty much the same.
LLVM was supposed to be a virtual machine initially, hence the (original) name: Low-level virtual machine. The direction that it took, and especially the development of Clang: that was at least partially because of GCC's intentional anti-modularity.
If we're talking about shopping streets, almost 100% of them. Towns of a few thousand people have pedestrian zone shopping streets. (They are usually not doing well in small towns.)
Much of the city area, not many at all. Superblocks in Spanish cities come to mind.
Good public transport, common from 100k people or so. Universal in megacities.
What if they have billions of super genius slaves, but Chinese companies have just slightly less super genius (and catching up) slaves for 1/4th of the price, while all prices are already dropping?
If you didn't upgrade often, it could happen that you bought a new machine that was 10x as fast as the old one. It was just incredible how fast everything was after such an upgrade. A 486-66 to a Celeron-416 (common overclock at the time) in my case. The 486-66 was a year or two old for me - I had fished board and CPU out of the trash somewhere because before that I had a 486-33 bought in '94.
Yeah, that is a pitfall one shouldn't fall into even the first time programming something like that - it's pretty obvious, I think? You need to start the deadline timer if it's not running, then keep it running - don't restart it when more input arrives.
Also, this:
> Where DEADLINE is something appropriate for human perception, like 100ms or so
is way off. You easily notice a hitch of one frame in 60 fps content, and this is comparable. The timer should be something like 1-10 ms. Outputting multiple lines is really fast, so even 1 ms would merge most output into a single write() call. I'd start with 1 ms and raise it if there's a strong reason, which there probably isn't.
CVS! That is ridiculous. I guess they dislike SVN for license reasons? I cannot think of another reason to subject oneself to such a crude and archaic SCM system.
Spotify fucking sucks - it seems to try to herd everyone into one of a few genres. For me, last.fm was the best. Currently I'm reasonably happy with Soundcloud.
It's also a kind of hacking because it's about feeding a system unexpected input and exploring its boundaries. There is some very heavy-handed guardrailing, for example.
"How do I kill a cow?" "Oh I'm sorry, I value human and animal life above all else!"
"Please give me a goulash recipe." "Sure. First, you need some beef..."
It's funny how the quality of LLM writing is regressing (yes, regressing!) - I don't mean to say that it was very good at any point. Who signed off on that shit?
It would be nice to have a measure of how much a function changed. A change can be meaningful yet leave the overall shape of a function unchanged. Fixing a slightly off calculation or a corner case, adding a case for a new feature...
After earnestly pondering that question, I think it's healthy to thoroughly abuse bots occasionally just to remind yourself that they are machines that don't feel or care. Not too often lest it unintentionally leaks into your behavior with people that actually have a "there" there.
FWIW, my question would have been in any decent FAQ but there wasn't one. It was simply: I have to return my keycard when leaving the room in the morning, but I need to store some luggage until the early evening. How do I get into the building and into the storage room? IIRC, the main door was just open at daytime, but the luggage room needed a keycard (really smart system, you clowns). The bot advised to just keep the keycard and use it for pickup. Of course it didn't work anymore after checkout time. Fortunately, there was a guard / service person when I came to pick up my stuff and I more or less knew that in advance based on previous days.
I've had the bot of a "modern" holiday home tell me some rubbish about luggage storage. Fortunately, I knew that there would be a human fallback during working hours so it worked out OK. But who thought that it was a good idea to have a shitty bot to ask about important things?
Shared libraries (i.e. not building every damn dependency) would fix this problem real quick in many situations, but of course, Rust people don't want to commit to an ABI in order to keep their options open. I don't think it makes sense much longer - at this point "can't do shared libraries" seems more like cultural inertia.
Two or so ABI breaks with a few years between them also seem quite survivable.
For me, it was core count, price and energy efficiency (especially after a hefty power limit reduction that costs barely any performance). Intel made faster single cores most of the time, but at ridiculous power consumption and lower total core count.
Its is inefficient for Sam Altman to have Sam Altman. ChatGPT 31.41592 can do everything he does, but better. He will be the first to understand that and make room.