Serving ~54 RPS for less than $10 per year: https://www.troyhunt.com/serverless-to-the-max-doing-big-things-for-small-dollars-with-cloudflare-workers-and-azure-functions/
How would folks feel about: patenting a thing, writing the only implementation as GPLv3+, and giving full rights to the patent for any GPLv3+ licensed implementation. Then using the patent to block non-free implementations and selling individual dual-licenses for non-GPL use as a way of supporting the project.
How would folks feel about a variation of the GPL that didn't include the right to run the software? The source code would be available, you could study/modify/share the source code, and could run the software to _validate_ your changes only. Using the software for any real work would require a paid license. Folks sharing modifications would do so under the same license. They could chose to either distribute their patches for free, or also charge for the right to run the patch.
I feel that focusing only on the right to run actually _discourages_ open source contributions by placing the maintenance burden at the feet of the project maintainers. Without a community that values the other rights, there is a high cost to a project owner when open sourcing. It's often easier to keep software closed source than to deal with the maintenance burden of giving everyone the right to run without anyone else having the desire to study and change.
Freedom respecting software is about the right to run, study, change, and redistribute software. I feel that the Open Source community is focused on the first point, the right to run, but the others are IMO more important. The right to study gives humanity the ability to learn and grow together. The right to change allows users to customize software to their needs. The right to redistribute allows you to share the cool new stuff you build with your friends.
The more I build, the more I see real dev-time and operational value in breaking problem domains apart into separate process spaces (and code bases!) and coordinating w/ IPC. Going back to monolithic development for end user applications is painful. I feel like bash is the only mainstream language designed for shipping to end users that does a pretty good job of breaking problems up across process boundaries and coordinating IPC.
dockeri.co is moving to arc.codes!
Photo is of the _entire_ app after migration (other than the svg template in badge.js).
See it live at: https://staging.dockeri.co/image/node
Fighting back against the entropy of the universe by building highly structured systems that power the hive mind of humanity.
Fosstodon is a Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.