entwine

Honestly, there's probably a bigger market for a working printer than for their laptops.

To be fair, Microsoft's slap on the wrist came from Bush forcing the DOJ to settle. In this situation, it's a spineless judge refusing to enforce the law in the first place.

Another reason to use Linux is to spare yourself the Windows CMD prompt syntax

Rug pulling a blog service? Seriously? Any first year student can make something like this. The name/brand is probably the only part that's remotely valuable, and a rug pull is a good way to fuck that up.

With old hardware, beggars can't be choosers. I get the appeal of the nouveau driver, but if your goal is to save a machine from the landfill, it's probably the better compromise to use the proprietary driver and keep it actually competitive for as long as possible. Those 900/1000 series cards are still plenty powerful today, even if they can't quite do AAA gaming anymore.

Bazzite. Every other recommendation is wrong.

Bazzite is "immutable". What that basically means is that you won't be able to break it even if you try. And if it does break somehow (for example, because of a bad update), you can fix it by doing a rollback, which is literally a one-line command: sudo rpm-ostree rollback

Sure, there are other immutable distros out there, but Bazzite is probably the most popular right now, and it ships with Nvidia drivers so it's ready to go for 99% of people with no changes necessary.

I think you're conflating regular auto use with using it as a return type/argument. The latter is syntactic sugar for declaring a template. It isn't any less "documented" than doing a template<class ReturnType>....

Once the bubble pops, Claude, OpenAI, etc will need to raise prices and/or tighten rate limits. I wouldn't want to be a "vibe coder" in that situation.

being inserted automatically.

Aka the entire point of RAII

This non-sarcastically. The operating system is better at cleaning up memory than you, and it's completely pointless to free all your allocations if you're about to exit the program. For certain workloads, it can lead to cleaner, less buggy code to not free anything.

It's important to know the difference between a "memory leak" and unfreed memory. A leak refers to memory that cannot be freed because you lost track of the address to it. Leaks are only really a problem if the amount of leaked memory is unbounded or huge. Every scenario is different.

Of course, that's not an excuse to be sloppy with memory management. You should only ever fail to free memory intentionally.

Software. It's a phone that can't make phone calls, with a camera that can't take pictures. It doesn't matter if some coding genius manages to port Crysis to it, if the phone can't phone, it's DOA.

I haven't used it that much (never even done a jam with it). The weird licensing of the editor rubs me the wrong way, and IIRC it even has some telemetry enabled by default. That's kind of a red flag when you consider the engine came from King, a mobile game developer. I don't think I want to trust them, but other people might not care.

But I do like the design of the engine. Message passing is actually a great pattern in general, and it's used by other engines like O3DE to great effect. It does take some getting used to though, and I personally never was a fan of Lua. If you've ever done any Objective C or Swift, it'll be familiar. It provides a way to build decoupled systems effortlessly, and long-term keeps your codebase flexible and maintainable, which is exactly what you want for a game that needs to constantly evolve its design throughout development.