Oh man, I loved my OG Droid.

Oh! My favorites!

This seems both awesome and dangerous. The two analogies that come to mind are home canning and home brewing. They’re both generally safe and easy. But every so often someone gives their family botulism.

Then Diogenes comes rolling through in an RV.

While the priors seemed to suggest it could float, the update step showed that was an outlier.

I’ll show myself the door.

Exactly, the same way I handle all my credentials.

And… they’re basically all correct. Linux does run on all sort of machines, even really ancient ones. It has a solid command line environment, or rather lots of them. And it’s astounding powerful. Windows does still blue screen, is currently the best place for gaming, and wow is MS fucking you with Win11. Macs can have a cool setup, are really simplified for most users and expensive.

Forty years too late, but I guess better than never.

I’m one of them. For a lot of reasons my partner and I want to move, but we have a 3% mortgage. Even though we have a large amount of equity, we still can’t afford to buy now. I’m looking a getting a loan from my parents, which is ridiculous considering our situation but almost 8% interest rates mean our payment would just about double from what we have now.

I’ve only worked on a few embedded systems where C++ was even an option, but they allowed 2, 4, 5, and 7. Though, for the most part most classes were simple interfaces to some sort of SPI/I2C/CAN/EtherCAT device, most of which were singletons.

Take a look at what even the proposer is saying wouldn’t be allowed in:

 (1) new and delete.  There's no way to pass GFP_* flags in.

 (2) Constructors and destructors.  Nests of implicit code makes the code less
     obvious, and the replacement of static initialisation with constructor
     calls would make the code size larger.

 (3) Exceptions and RTTI.  RTTI would bulk the kernel up too much and
     exception handling is limited without it, and since destructors are not
     allowed, you still have to manually clean up after an error.

 (4) Operator overloading (except in special cases).

 (5) Function overloading (except in special inline cases).

 (6) STL (though some type trait bits are needed to replace __builtins that
     don't exist in g++).

 (7) 'class', 'private', 'namespace'.

 (8) 'virtual'.  Don't want virtual base classes, though virtual function
     tables might make operations tables more efficient.

C++ without class, constructors, destructors, most overloading and the STL? Wow.

According to the github analysis, the kernel repository is:

• C 98.3%
• Assembly 0.7%
• Shell 0.4%
• Makefile 0.2%
• Python 0.2%
• Perl 0.1%
• Other 0.1%

So yeah, its basically all C, plus a tiny bit of assembly for very low level bootstrapping and some helper scripts.

There is no C++ allowed in the Linux kernel and Linus has gone on several major rants about how terrible a language it is.

Man, now I’m nostalgic for my 3DS. I sold it when I got a Switch, which is a nice system but the 3DS had so many fun little things about it like Streetpass.

JPF vs the PFJ?

https://youtu.be/WboggjN_G-4?si=78-liE_B4zjkfppO

I feel like the fact that you can name all of those as different groups means that you’ve already fallen for the feldspar trap.

https://xkcd.com/2501/

You forgot about leftist infighting.

Yeah, and unfortunately I’m related to them. The maternal side of my family has pretty much split in two and aren’t talking to the other half nowadays because of shit like this.

I’ve been on the internet too long, because I assumed you meant it was a furry site.

“Spine is so shiny” I… I’m going to be thinking about that phrase all day now.