6 ms·
"deprecation" kills Open Source projects, ecosystems, even private services. The people don't like to build their businesses, livelihoods on shaky ground that c
by unity1001 4y ago
"deprecation" kills Open Source projects, ecosystems, even private services. The people don't like to build their businesses, livelihoods on shaky ground that can collapse from under them at any point just by the decision of some maintainers who are doing something as a side-activity.
This seems to stem from the academic roots of Open Source. It grew from such projects in academic environments where deprecation of something would not cause anyone's business to collapse. Amplified by its adoption in large organizations in which deprecations don't cause major disruption and the organization would have ample time and funding to address these anyways.
This mentality even afflicts and hampers large private organizations - take Google:
A culture that has grown from its academic roots in MIT, where the funding mainly comes from the government or large military/private organizations. Carried over to the larger organization of Google as it matured, where there was ample funding and time for addressing such 'deprecations'. All good.
But they kept behaving towards their end-users in the same way. Constant 'deprecations', shutting down entire services on people's faces with little notice, literally giving a jolt to their small businesses, organizations, even livelihoods. Then they started noticing people earlier. But this didn't change a thing because the general public don't have the funding and resources that Google has for addressing such 'deprecations'.
So people started trusting Google. To such an extent that Google Cloud cannot get people on board even as their execs openly promise stability to the customers. Because nobody believes them anymore.
https://steve-yegge.medium.com/dear-google-cloud-your-deprecation-policy-is-killing-you-ee7525dc05dc https://steve-yegge.medium.com/dear-google-cloud-your-deprec...
Actually, turns out Google itself also doesn't have such resources. As evidenced by the recent 'inefficiency' talk that they gave to the company. So much engineering. But not enough product, in the face of a tech sector that is increasingly imperiled by rising inflation and dire economic times that do not permit floating organizations on overvalued stocks...
...
If even Google suffers from this kind of 'deprecation' behavior, imagine how much general Open Source suffers from this.
Obscure feature or security updates causing backwards-incompatible changes and breaking entire software setups, small businesses and individuals having to dedicate considerable time to maintaining their software as if they were software engineers who were doing it as a hobby.
That's what's hampering Open Source. Treating everyone as if they were software engineers using the Open Source software on the side, as a hobby.
They aren't.
They are people, a lot of them non-technical, with real lives, businesses and livelihoods that hang on that software.
And that is the major reason why Open Source keeps losing ground to proprietary, closed-ecosystem services that just give the users what they need to run their businesses and their daily lives without having to deal with Open Source maintenance problems.
So...
> The lifeblood of volunteer-run open source projects, which is most of them, is ultimately the motivation of the maintainers who work on them
No, the lifeblood of volunteer-run open source projects are their users. If there aren't users, there is absolutely no point to an Open Source software other than being a hobby for those who get involved in it. The users include corporate or intra-organization users too, by the way.
With such a mentality, Open Source can never change the world. Instead it would just keep losing ground or stagnating compared to closed-source private services and ecosystems that prioritize their users.
- mrtranscendence 4y ago> No, the lifeblood of volunteer-run open source projects are their users. If there aren't users, there is absolutely no point to an Open Source software other than being a hobby for those who get involved in it. This feels a bit screwy. Maybe it's arguable what the "lifeblood" of a volunteer-run open source project is, but surely it's not simply the users -- without sufficiently motivated volunteers there would be no project for the users to use. And how is working as an unpaid volunteer, alongside your day job, anything but a hobby anyway? > Instead it would just keep losing ground or stagnating compared to closed-source private services and ecosystems that prioritize their users. Let's assume you've identified a genuine problem with many open source projects: their unpaid volunteers aren't offering good enough support to their users. What happens to the project when their motivation is completely sapped because they haven't been able to work on interesting problems, due to having to pacify needy users who aren't giving anything back?
- unity1001 4y ago> This feels a bit screwy. Maybe it's arguable what the "lifeblood" of a volunteer-run open source project is, but surely it's not simply the users -- without sufficiently motivated volunteers there would be no project for the users to use. Without users, there would be no point to any software project. Less, Open Source... > And how is working as an unpaid volunteer, alongside your day job, anything but a hobby anyway? That's precisely why Open Source projects need to find a way to get funding. There is no way the general public would build their lives and future on Open Source that relies on hobbyists. Which is a reason why Open Source is not where it should have been today. > What happens to the project when their motivation is completely sapped because they haven't been able to work on interesting problems, due to having to pacify needy users who aren't giving anything back? Nothing. The project dies. Before that, the users will have already left, probably for private, closed ecosystems. Because it was a folly to expect people to build whatever they were going to do, less their businesses or organizations, on volunteers who may go away at any point in time. Sounds brisk and brutal, I know. But that's the reality of public usage of software - if people can't rely on it, they won't use it.
- OkayPhysicist 4y ago