It’s never going to happen.

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.

A compiler. I mean, yeah, I guess I could go back to writing asm, but I really don’t want to.

Exactly, the same way I handle all my credentials.

If you mean emissions wise, that’s really going to depend on the bike. Old two-strokes rocking carbs? Yeah, they’re terrible. Modern fuel injected four strokes with cats? Pretty good, actually. And they get better mileage than most hybrids. I get 60mpg on my 900cc Triumph, which is a mid-sized bike by American standards and a big bike by world standards. Smaller bikes and scooters can get over 100mpg.

Take a look at motorcycles. They tend to be far behind the curve technology wise, and only Zerocycles have a telemetry system afaik.

Fun fact: Leaded solder is still required in aircraft because it doesn’t grow whiskers like this, while pure tin solder does.

I’ve been really enjoying my current Pathfinder:Kingmaker run going for the true ending.

Even if you don’t have anything material to leave behind, there are still a few questions that it’s good to have the answers written down for, mostly advanced directives. You can find free AD forms if you live in the US at https://www.aarp.org/caregiving/financial-legal/free-printable-advance-directives/ and most other countries have a similar system.

Nope. They do require some form of 2FA, but that can be any of: phone number, security key, authentication app, or a secure device. They also support one time use backup codes that you print out and keep secure. Personally, I use security keys for day to day and keep the printed out backup codes with my will.

I know that’s supposed to be a jokey edgy comment but advanced planning is really important for those you leave behind. They will absolutely appreciate it if you have done the basics of estate planning (will, advance directives, digital account planning) so that it’s not one more burden during one of their most difficult time in life.

In my filing cabinet that contains my will and other emergency documents I have a printout of the emergency backup codes for my password manager and my google account. That should be enough for my heirs to get whatever they need and want.

My development PC running linux (I don’t use Arch, BTW) + Steam has by far the most games I’m interested in playing. Games that I have played my entire life run great, through DOSBox, Proton, native, or console emulators.

That being said, I still have a huge soft spot from my old 3DS and wish I still had it. Sure the Switch is great, but the 3DS had so many fun little quirky features that it was just fun to use as well as play games on.

System Shock (2023) just had a big new patch and is just about to tick over the one year mark. Seems like a great time to play it again for the first time.

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.

It has nothing to do with actual distances and everything to do with optical illusions and atmospheric effects.