Elections for executive leadership doesn't sound all that crazy to me. With 30+ years in the business I have witnessed my fair share of executive whackos that wouldn't have passed a basic sniff test if they had convince workers that they should be the one leading them.
This is actually important to understand. What are the dependencies of your dependencies? I.e. if your goal is to be sovereign than knowing how far the turtles go, and who the turtles are, is quite important.
I remember playing this on my families Olivetti M24. It was very difficult. Maybe because the game was speed sensitive and the M24 was an 8086 running 8Mhz. Good times nonetheless.
> A 19k lines-of-code Pull Request was opened in January, 2026.
Such a PR should be rejected simply because of the shear size of it, regardless of AI use. Seriously, who submits a 19k line PR? Just make many small ones.
The PR touched a lot of internals, including module code and mirrors the fs APIs. So, yes it was big, but the commit history was largely clean and followed a development story, and it was tested. The code quality was decent too. I didn't review all of it because I don't have a personal stake in this though.
I suggest EVERYONE in this thread go read the the GitHub PR in question. There's some good arguments for and against AI, and what it means for FOSS... But good lord you will have to sift through the virtue signalling bullshit and have patience for the constant moving of goalposts
How would you go about breaking up this particular set of functionality into smaller PRs, exactly? It's meant to introduce a virtualized file system... the size is dictated by the feature itself.
Also, no mention at all regarding the test coverage, or impact if any on existing code paths specifically.
I added a Intel Core i7 10700K (with a nice low-profile Noctua cooler/fan) with 32GB of memory and a 512GB SSD and I'm using onboard graphics which is just fine for a daily driver "office" type machine running Linux. Very happy with it.
reply