addie

An interesting assertion. A full install of 3.11 was about 8 MB or so, and all of the 8086 / -186 / -286 / -386 code will have been thrown away a long time ago. I doubt there's much of PROGMAN left, and all the fonts and art assets are long superseded. So in terms of total code, it can't be much. But on the other hand, the code that you write for an event loop or to handle driver interrupts hasn't changed conceptually very much in that time. Most programmers would reimplement the basics in a very similar way, so there's not much point in redoing it.

When I used to work in the water industry, we still had programmable logic controllers (PLCs) controlling pumpsets from the 1950s. The last person that could have modified them had retired and since died more than 30 years before. But deciding which pumps to run in order to best fill a reservoir is not logic that needs updating every day, not even every decade. Still working fine, don't touch it. So I still laugh at my colleagues that can't touch code that was written a few years ago in an unfashionable library. That's not tech debt. Try, written by your grandparents for CPUs that had stopped being made before you were born.

And I remember 3.11 being perfectly good enough at the time, anyway. Wasn't any Linux at that point.

Six legs, and a tail split into two for what looks to me like flight. I think you'll find that's a beautiful Butterfly Cat.

Plain old Vim, with YouCompleteMe, NERDTree and TagBar installed; plus a few bindings to the leader key, is a much better IDE than anything else I've found. Sometimes it would be nice to a couple of the buttons that Eclipse or IDEA provide, but for pure text editing it's unbeatable.

I've also found that "fancy Git dialogs" just get in the way, and learning how to use it properly from the command line stomps them all hands down. Plus, you can still use all your skills in a remote terminal.

I just don't see the thinking here.

• buy a decent steak
• leave it out at room temperature for an hour so that it will cook properly. During this time, prepare the vegetables, potatoes, sauce that will go with it.
• cook the steak for two minutes a side in a heavy frying pan on high heat
• let the steak rest somewhere warm for ten minutes while you finish assembling everything else.

I could spend a fucking fortune, enough to live on for months, to cook my steak upright in a toaster for 90 seconds instead, for a worse end result, and it would save me zero time, because cooking the steak is not the time-critical step here.

Would only save you time if you're buying the kind of steak that can be cooked in 90 seconds, and taking it straight from the fridge, cooking it, and then putting it in sandwich, and anyone who thinks that sounds a good idea frankly doesn't deserve to have a decent steak.

They're quite versatile computers for general purposes, but their i/o performance is dreadful. Mine all max out at about ten megabytes per second. That will not do, for server purposes.

Fortunately, there's businesses all over that are chucking out all their old mini PCs since they won't run Win11. I got an extremely decent one for £20 and it's my new home server. Absolutely storms it, while just sipping at electricity.

... which is ironic, since SystemD is what happens when someone comes up with a problem to fix your solution.

Negative value would indicate "paying you to take them", which doesn't make any sense, unless there's a forfeit associated with having any.

Really, share prices should be on a logarithmic graph. You care whether your shares are now worth eg. twice as much or half as much as you paid for them originally. The actual number of shares that you could buy with a given amount of money isn't as interesting.

Dang. If only they had some kind of security scanning tool that could catch that kind of thing.

It was quite prone to crashing-to-desktop and certain PC configurations had bizarre graphics issues, but I did play through it on hardcore in the week of release and had a great time with it. Just needed to quicksave a lot.

The kind of bugs that it did not have a lot of were quest bugs. Bethesda's own games are 'wide but shallow', and very few quests in the world seem to interlink with each other, but despite that, they're very easy to break accidentally, or cannot be completed due to flag issues. Oblivion managed to wrangle up a complex plot with tonnes of interrelated parts, and it mostly just worked.

What F:NV could have been if it had been made in a good engine... Most of the times where it got dinged in review scores were for bugginess and instability. Trying to build a castle upon sand; there's only so much you can do before all the cracks appear.

The fruit was originally called a norange, from Spanish naranja, but that sounds a bit awkward in English so the n moved over to make it an orange instead.

Alas, no.

I call mine 'little Elvis', because that's what Elvis called his, and it's always struck me as a good name for it.