I think that kind of social endeavor isn't something a lot of maintainers can accomplish, not even those with the skills to work on such a project all by themselves.
I think that kind of social endeavor isn't something a lot of maintainers can accomplish, not even those with the skills to work on such a project all by themselves.
In reality engineering is straightforward, you just need someone to show you how to properly write data structures and algorithms and to break problems down.
Andreas showed these kids this, reinvigorating the web based hacker culture I grew up in. Anything is possible and even if a problem ends up being more than you can handle at least you learned a ton along the way.
Now days searching for how to code leads you to a ton of tutorials about gluing modules together. I feel sorry for young people with that thirst who won’t be satisfied thanks to the commoditization of learning to code.
“Wish we could go back to 2004. Modern web has become toxic af” which embodies the spirit of this community pretty well I think.
Andreas Kling is the messiah that is leading a group of people that are fed up with modernity.
It takes advantage of sharp hindsight and correct what was bad, and more importantly keep what worked.
Sorry but you get that wrong, that's just meant for file buffer and caches etc. NOT actually bloat.
Other OS projects I have seen either lack vision (same as x, but written in y), or they are just for the personal learning of the developer who started it.
While "Unix-like core with the look&feel of 1990s productivity software" sounds simple, it's more than what most new OS projects I have seen provide and it very clearly signals who it's for.
The "look&feel of 1990s productivity software", communicates that the UI will use consistent elements across applications, which is something you only find in Mac OSX these days.
The Super welcoming community is the other half keeping people engaged that you are looking for.
- write the whole stack yourself so you can fix any problem or make any improvement without external dependencies or coordination - the implementation is never written in stone and it is always possible to move to something better ( which is why you need to control the whole stack ) - no problem is too big to start solving - implement something basic that works and then improve it ( see all of the above ) - evolve everything in the open