Authorative drive is what makes software more inclusive. It can focus the resources and attention where its needed, to create a superior product. Linus being a bulldog with the Kernel is proof enough with that.
Design by commitee does not make things more inclusive. It just leads to people not getting their way, having a huff, and screaming “I’M GOING TO FORK THIS AND GO MAKE MY OWN VERSION, WITH BLACKJACK, AND HOOKERS!”, and now you have two teams doing the same thing, and being lesser due to the split dev time and attention. and will probably lead to more forks, and more splits of teams.
Doesnt mean it has to be monolithic/monoculture. but a single product that serves 80% of everyones wants and desires is a better, superior product to one that tries to cater to and serve 100% to each, different individual.
and most people wont even notice the 20% difference in their everyday usage and life. They just get told something, or get a wrong idea, and are hard pressed to give it up cause humans can rarely admit their own wrong.
Authorative drive is what makes software more inclusive. It can focus the resources and attention where its needed,
Where a particular groups think it’s needed.
Let’s take some examples. In the linux world, there are multiple DEs, with different GUIs and approaches on how to interact with a computer. People used to the windows look might feel better and be more productive in KDE, while people who are more used to phones might prefer GNOME. There are DEs that are very lightweight with resources, so that people with older machines aren’t left out, and there are people who don’t even like DEs at all, who might prefer something like i3. In the end, everyone can have something to run on their machines, and which they will feel more comfortable with, instead of a particular group of people deciding how someone should interact with a computer, and people having to use it the way they want, whether they like it or not.
Doesnt mean it has to be monolithic/monoculture. but a single product that serves 80% of everyones wants and desires is a better, superior product to one that tries to cater to and serve 100% to each, different individual.
I agree with that, and maybe we’re talking about different things? The kind of diversity I mention is multiple projects aiming at 80% of different people, but coexisting.
But how much is too much? Diversity is a great thing for people, makes technology less authoritative and more inclusive.
Authorative drive is what makes software more inclusive. It can focus the resources and attention where its needed, to create a superior product. Linus being a bulldog with the Kernel is proof enough with that.
Design by commitee does not make things more inclusive. It just leads to people not getting their way, having a huff, and screaming “I’M GOING TO FORK THIS AND GO MAKE MY OWN VERSION, WITH BLACKJACK, AND HOOKERS!”, and now you have two teams doing the same thing, and being lesser due to the split dev time and attention. and will probably lead to more forks, and more splits of teams.
Doesnt mean it has to be monolithic/monoculture. but a single product that serves 80% of everyones wants and desires is a better, superior product to one that tries to cater to and serve 100% to each, different individual.
and most people wont even notice the 20% difference in their everyday usage and life. They just get told something, or get a wrong idea, and are hard pressed to give it up cause humans can rarely admit their own wrong.
Where a particular groups think it’s needed.
Let’s take some examples. In the linux world, there are multiple DEs, with different GUIs and approaches on how to interact with a computer. People used to the windows look might feel better and be more productive in KDE, while people who are more used to phones might prefer GNOME. There are DEs that are very lightweight with resources, so that people with older machines aren’t left out, and there are people who don’t even like DEs at all, who might prefer something like i3. In the end, everyone can have something to run on their machines, and which they will feel more comfortable with, instead of a particular group of people deciding how someone should interact with a computer, and people having to use it the way they want, whether they like it or not.
I agree with that, and maybe we’re talking about different things? The kind of diversity I mention is multiple projects aiming at 80% of different people, but coexisting.