Relevant xkcd: #2347
I really do love Open Source. I love being able to build software that I know people will be able to make greate use of if it fits their use case. I love that we can extend already existing open source software & I love that we're able to put licenses on our code and explain where and how you can use it.
But open source is a tuly double-edged sword. Forever are there stories on Twitter with people explaining how they were taken advantage of, or don't have the resource to keep maintaining a project.
Recently, a library called
faker.js was nuked by the author in an attempt to make a "political" point. Wildy unsuccesful and in my opinion, extremely immature. However, the community responded really quickly and quickly forked the project into
@faker-js/faker. This meant developers could easily switch their project over to use a 100% API compatible, up to date and community managed version of the project. The original author, Marak Squires, ended up deleting the original repo. As well as that, Squires also placed malicious code in another project of his,
colors.js, that would infinite loop the victim's computer.
But there was a reason for this. Thanks to the wonderful archive.org, we're able to see old and deleted posts explaining why this had had happened — and it's a common frustration within the community. Famously, Marak mentions he will do No more free work and he's also written a good few hundred words on the topic, too.
Okay, so he's frustrated with people taking Open Source for granted. What's the solution here? Well, fantastic companies like OpenCollective and GitHub are taking the initiative to provide a direct, low fee method of sponsoring open source projects. Big companies like Discord, Stripe and Microsoft have all sponsored small and large projects and sometimes they get their name on the Readme in return. At the moment, we're not quite there completely but we're definitely heading in the right direction.
motion (motion.dev) which caused a bit of a stir in the community for shaking things up a little bit with regards to their monetization strategy. The library itself exists on npm and can be installed as you would any other node module, except there is no GitHub url for the package..? Taking a look at the README on npm says the following:
Become a sponsor and get access to the private Motion One repo. File issues, read the changelog and source code, and join discussions that help shape the future of the API.
Okay interesting, so you can use the module and read the documentation for free, but accessing the source code requires somewhat of a paid subscription. There is valid incentive for companies to do this as it allows them to not only audit the codebase (under security concerns), but also it allows for reading the source code to see how everything works and learn a lot.
So what's the downside to this? Well one of the reasons traditional open source is brilliant is because it allows anybody to freely see how something works — so assuming that is true, could we even call
motion an open source project? What's more, a lot of individual developers are students or kids learning and as such, they're not financially able to support projects. On top of that, they are the generation we want to be educating the MOST about programming and so immediately cutting them off is definitely not a win.
One final example of open source being painful has got to be Fastify. Fastify's creator is active on Twitter very often and there have been a few Tweets describing some headaches they have had to go through as a team to get Fastify to be successful. Keeping it short, but one thing they have done extensively has been advertising Fastify which has kept it mainstream and allowed for more users and therefore sponsorships. Matteo Collina, Fastify's creator, has explained that had there not been the advertising done, Fastify would not be as maintained, if at all, as it is today. Right now, Fastify has two core maintainers and 16 on the core team overall.
There is plenty of room for innovation in this space, I'm excited to see where places GitHub sponsors and OpenCollective go and if we can see some large tech companies spreading the word about open source
By the way, I do accept sponsorships via GitHub, so if you enjoy my work or writing then please consider any spare VC funding you have just raised 😊 github.com/sponsors/alii
Thanks for reading!