NackerHughes

This was written by AI.

Starting in 2027, a silent update, nonconsensually pushed by Google, will block every Android app whose developer hasn't registered with Google, signed their contract, paid up, and handed over government ID.

Every app and every device, worldwide, with no opt-out.

This includes apps shared between friends, distributed through F-Droid, built by hobbyists for personal use.

Independent developers, church and community groups, and hobbyists alike will all be frozen out of being able to develop and distribute their software.

Registration requires:

- Paying a fee to Google - Agreeing to Google's Terms and Conditions - Surrendering your government-issued identification - Providing evidence of your private signing key - Listing all current and all future application identifiers

If a developer does not comply, their apps get silently blocked on every Android device worldwide.

It didn't 'take down a sizable chunk of the Internet'. Site owners took down their sites because of FUD and mass hysteria.

The device I'm currently using has no headphone jack, no removable battery, no removable memory, no removable storage, a single solitary USB-A port and a locked-down BIOS that only lets you install Windows by default. All in the name of profit.

Yes, the device I'm currently using is worse than the equivalent model was 10 years ago. Thanks, capitalism.

No, labour creates the technology that people use.

The system just decides where the wealth goes.

Under capitalism, it doesn't go to the people who did the labour.

Fake comment, written by a bot, not a human.

A vector!

I click. I see an anime girlie bot challenge screen. I hear zoomer pop in ~32k 16-bit stereo. I see JavaScript animations and a seizure-inducing vibecoded layout. I close the tab.

"Miss the old web?" The author wasn't even born then.

It really does boil down to 'just read the source code bro' but with more of a sense of direction to it.

Don't worry about understanding the entire codebase just yet. Instead, try to understand some specific parts of it to begin with. As you work with different bits of the code you'll gradually form a mental 'map' of how the whole thing fits together.

Start by trying making small changes, e.g. make the guns faster, or make the player jump higher. Look for where that code is that does that thing.

You might be taken on a bit of a journey, finding the definition of a function, then the function calls within that function and the variables passed to them, etc. - all the way along you'll be discovering how various other things are done within the game engine, and the general layout/structure of the codebase overall, as well as plenty of general programming concepts that will be useful anywhere.

Do this enough times and you'll gradually build a familiarity with the engine, and programming in general. Then if there's something you want to do that's in a part of the codebase you're not familiar with, you'll be more able to 'dive in' and find where it is in the code, and you'll be more confident that you can read code you're not familiar with it and be able to figure out what it does.

I can only speak from my experience from when I was just starting out learning to code (17 years ago!), adding and tweaking various features in Cube Engine and its sequel Sauerbraten, eventually moving onto Stepmania. Stepmania was a MUCH bigger codebase than Cube/Sauer (probably still not as big as Quake 3 though!) and the stuff I picked up modding those two was invaluable for working with Stepmania.

string.h

Then why are people starving?

This is vibecoded. How are we supposed to believe that any of the descriptions aren't hallucinated?