111
Why 'free' proprietary software will always end in tears
(davelane.nz)
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
This is also true for open source software though, a lot of open source devs are mini dictators ruling over their own fiefdoms with an iron fist and they don't care what the users, many of which have no coding ability, need or want.
Even those that do have some coding ability will be ignored if they try to change things upstream that the main devs don't agree with, even if most users would welcome such a change.
When I ran my open source project, I was discerning as to what code I'd accept from people.
Does that make me a little dictator if I don't want to then maintain shit code from someone who doesn't know what a comma splice is, like above?
Sorry if you do code better than you write.
No, that isn't really what I'm talking about.
Sure, code quality matters.
I'm talking about things like mastodon trying to push a certain outlook upon its users just because the main dev thinks they should be using it a certain way, and hating how people actually use it.
It's funny how you resort to personal insults to me even though I have not really to you. It's true there are a lot of punctuation rules I do not understand. However, I would point out that this is not an english test, so it doesn't matter.