Isn't it more of a blue shift / red shift situation, rather than scattering?

I'm not sure, at least the unrepairable mess made by Microsoft is software rather than hardware - you can reinstall a janky OS but you can't unexplode a phone that disassembled itself when you sneezed in its general direction.

There's no fine line between the two companies.

Edit: they continuously fucked up Halo in unexcusable ways, fuck them, they're worse than Apple. Forgot about that.

Microsoft is definitely the corpoest of them all.

Probably not the worst corpo, likely even, but out of the corpos, they are the most corpo corpo of any corpo.

1. They own LinkedIn, and I could just stop this list here.
2. They're the founding fathers of Embrace, Extend and Extinguish.
3. They are the vanguard of videogame studio consolidation, after buying Activision and Bethesda.
4. AI
5. Everything they do is soggy bread: you can eat it, it's probably mostly healthy, I think, but if a product is not the minimum viable product then it will be; take the Halo franchise as a reference for blandness, Windows for end user tolerance - both are controversial yet functional and popular software that people complain (and do nothing) about. Halo took quite a hit in popularity, but still...
6. Remember when a software company got in trouble for monopolistic practices? That was a thing that happened at some point, and it was Microsoft. Not that it will ever happen again, nowadays all the cool kids have some slice of the tech landscape on a chokehold.

I don't know how this would be useful to someone reading the cheat sheet, but here's something interesting I just indirectly found out while skimming it through:

Ctrl+D does the same thing as ENTER, except the latter additionally sends the end-of-line character to the reader while the former sends nothing;
as is the case for shells or interactive programs like the Python REPL, Ctrl+D causes them to terminate only because it sends a string that is 0 characters long, and 0-size reads are universally interpreted as files reaching the end.

To test this: enter cat, type "hello" without pressing enter, then Ctrl+D: you should see "hellohello".
An extremely rare case of this being useful would be using netcat to send a string somewhere, without sending the end-of-line byte at the end.

I played many games that didn't fit onto either of my SSDs, on an HDD, including Destiny 2 and for a while Baldur's Gate 3 - they had ~70% longer loading times, but they didn't freeze outside of loading screens.

As for recording, you'd be amazed at how filesystem caches are good at what they do

This is what infinite exponential growth does to a mf

... and all the other mfs in the near vicinity

I swear they did in the preview

deleted by creator

As far as I know, C's threads.h implementation (or std::thread for C++) is based on POSIX threads.

If you're using CMake or a similar build system that can define macros when building from Windows, then one option you have is to simply create an interface of sorts.
Something like:

// angle brackes work for this codeblock? idk

#ifdef PLATFORM_WIN32
   // The syntax MSVC wants (which I'm not familiar with)
   #include "fuckmissingbracketsidontrememberwhatiwrotehere"
   thread_t win32_create_thread( /* ... */ ) {
      /* ... */
   }
#else
   // The syntax sensible compilers want (which I'm also unfamiliar with because I forgor U+1F480)
   #include "fuckmissingbracketsidontrememberwhatiwrotehere"
   int thrd_create( /* ... */ ) {
      /* ... */
   }
#endif

It may be a bit tedious, but I don't know if there is some widely known C equivalent to the Boost library, at least for threads.

You don't have to switch, you can dualboot if you have some disk space to spare.

Unfortunately the only rolling-release distro I've ever used for more than 10 minutes is Arch Linux, which is not "easy to use"; it's not hard, but you have to tinker with it every now and then (especially in the beginning, since you have to set everything up) - if you run pacman updates without looking at the archlinux.org frontpage beforehand you might find yourself with a malfunctioning bootloader or something on that nature.

AL updates are known for breaking things a few times, but in my opinion it offers a good compromise between DIY and ... y'know, Ubuntu.

Eh, at this point it happens every 3 commits, you get used to abusing gdb (since valgrind just dies).

I hope the police doesn't find my unregistered breakpoint minigun...

The in-house engines I know are being used are also really old - hell, 343i even decided to ditch the fossil that once was Halo: CE's engine because of technical debt and outsourcing blood sacrifices

Do people even make their own engines anymore? If this wasn't a pet project I would have dropped the entire thing as soon as I started dealing with 3D models, and visited Godot's homepage.

...

Perhaps I should get my hands on Godot at some point.

Not the fastest

This is my 4th Vulkan related "project" and 2nd attempt at making something other than a glorified tutorial workspace in 6 years, and it took me 4 weeks to draw this stuff with minimal technical debt.

I could just use an existing game engine, but what's the fun in not manually sorting all draw commands by mesh>pipeline>material and hunting synchronization hazards by just looking at funny glyphs for extended periods of time?

Promises of infinite exponential capital growth => Feature creep

"An error occurred while enabling Mobile Code, whoopsie"

*removed externally hosted image*

"You don't pass Google SafetyNet, fuck you, this ain't supposed to be your device"

*removed externally hosted image*

C, fight fire with fire