If you have an issue with an open source software, you need to register on a website that is made for developers, that will try to sell you a git hosting service, write a bug following a technical format, and you are expected to given information in a reproducible way.
If you have an issue with a closed source freeware, you just use a contact form on their website or leave a comment on their blog or whatever.
The amount of friction to report a bug that FLOSS puts on users is absolutely insane. It's almost like it's trying to deny anyone who isn't a technical person from reporting problems they are having.
GitHub is meant for developers. Plenty of OSS has forums or Zulip/Discord chats for ordinary users to get support in a more casual way. Sometimes not, but there's just as much closed source software with poor support too.
I don't think that means anything. It's just some random words to add pretense to an arbitrary change.
I mean, just stop to think about it. You have a Youtube account, you post videos. Analytics shows traffic from Google but can't show you the keywords.
At one point, Google merged Youtube with Google+. Just did it outright without asking anybody.
Youtubers link their Youtube accounts with Google AdSense.
You can link your Youtube account with your Google Ads account if you want to advertise.
One of the latest features added to the Search Console was... an AI chatbot.
So Google showed us they can link anything with Youtube when it wants, and they can add new features to GSC if it's AI, but for some reason showing Google search terms for Youtube channels took 20 years.
I wish I knew a word like enshittification but for when something improves but at a rate so slow you don't even feel like celebrating it anymore. I think I'd use such word a lot...
The term you're looking for might be "maintenance mode". This sounds like what we do with software we don't care to develop further, even if it's the big cash cow
>We became increasingly horrified at the programming practices we saw in Bun's codebase. Hacks on top of hacks. Abuse of assertions. Most of all, recklessly speeding past feature after feature with very little time taken for reflection and elimination of bugs and technical debt.
I'd like to know what the poor code quality in Bun looks like. Does anybody have concrete examples?
If you have an issue with an open source software, you need to register on a website that is made for developers, that will try to sell you a git hosting service, write a bug following a technical format, and you are expected to given information in a reproducible way.
If you have an issue with a closed source freeware, you just use a contact form on their website or leave a comment on their blog or whatever.
The amount of friction to report a bug that FLOSS puts on users is absolutely insane. It's almost like it's trying to deny anyone who isn't a technical person from reporting problems they are having.