I was looking for Astral’s future plans to make money. Simonw already answered in another post [1] tldr - keep tooling open and free forever, build enterprise services (like a private package registry) on top.
I’ve hit similar problems with their Ruby gRPC library.
The counter example is the language Go. The team running Go has put considerable care and attention into making this project welcoming for developers to contribute, while still adhering to Google code contribution requirements. Building for source is straightforward and iirc it’s one of the easier cross compilers to setup.
I love a good pairing ladder. While there is no absolute good measure of productivity, a suite of thoughts observation can provide at least tripwires.
One major problem with tools that ask crafters to do data entry to show their value is that best people are most likely to refuse. You really need to focus on tooling to help capture what’s going on without toil.
For example, if your folks are remote and they use software to aid in pairing (eg Tuple), script the system to log the tuple sessions and perhaps even capture the pairing in the commits made together.
This can be used as an input to bring visible to be best leaders in your org.
If Firefox does release support, it shouldn’t be long before adoption is widespread:
> Since Mozilla throttles the rollout of a new version (incrementally upgrading the percentage of the population getting upgrades), it takes about four weeks for about 70% of clients to upgrade before stabilizing.
For personal projects, I’ve fallen for the simplicity of Kamal. Created to host Ruby in Rails apps from DHH and the team who run Hey and Basecamp, Kamal is web framework agnostic. The demo is hosting a go app. Works great on a Pi.