@baldur@toot.cafe I see your point, though I feel the article leaves out an important counterpoint: When the goal isn't to sell software (aaS) but to have well working software for whatever a business does, it's simply the most efficient way (at least in the mid- to long term) to cooperate with others with similar interests. A client I'm working with right now on embedded system firmware isn't worried about someone else benefiting from Buildroot, kernel, etc. patches I'm writing, they're (rightly) concerned about the long term effort of maintaining a growing patch set and having to continually rebase it on new releases, so they explicitly want me to upstream as much as possible. Sharing reduces the local maintenance burden, and spreads the general one on more shoulders.

That's unlikely to save npm, but it's a much more positive outlook for those of us who work on solid infrastructure rather than flashy stuff and the latest hype. ​:neocat_floof:​