imagine if gnu was a carefully curated set of software that mutually benefit each other instead of a hodge podge of whatever people offer up, some of which is redundant. like how many common lisp implementations does one project need?
You need no less than 6 per project.
@masterofthetiger ah yes, Greenspun's 11th rule:
Any sufficiently complicated free software collection contains at least six bug-ridden, slow implementations of Common Lisp.
do you think the community would be easier to deal with ?
@AbbieNormal if there was a good, collective decision making process, then yes!
@dthompson then it would most probably be dead a long time ago.
The wealth of options, the hodgepodge and the mess didn't exactly turn up by lacking something, it is because it had something necessary for its own survival. A spread of development based on personal needs and wants.
I've heard this "they should tell people to do this instead" in a lot of projects where that very method of handling contribution wouldn't improve contribution, it would kill it.
@ohyran @dthompson this sounds almost obvious, if the project didn't develop the way it did, it would be like it is now. There's probably other projects that are more focused, and where the developers work more in unison. But now we have all these amazing apps, where some work better than others, but the best ideas end up being either used and improved, or forked and changed. This turns out to be beneficial for gnome at least :)
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!