521 karma · joined April 19, 2008
No more of that. Today, buy a router OpenWrt supports and just install the official images and get on with your life.
But with GitRoyalty, you can't even install the software to see if you want to use it or take a dependency on it.. without at minimum ponying up a credit card and signing up for a free trial.
My take is that this roadblock will turn away new users in sufficient numbers that it'll hurt projects with this paywall in place. Users will leave in droves for competing projects with less install friction. Not because they don't believe in paying, but because they don't know if they want to pay yet.
The projects that can afford to turn away users like this are the well-known ones with big-name maintainers, corporate sponsors, and thousands of GitHub stars. But these also happen to be the projects least in need of funding.
As difficult as it is to implement, a better place for a paywall would be after the user has installed the software, evaluated it, and decided to roll it out in production. That would bring the payment closer to the point of value, and also keep the on-boarding friction nice and low.
For all I know, it could exist for haircuts too.
[1] https://nutritionfacts.org/video/oxalates-in-spinach-and-kid...
Not necessarily a good idea in every case, but if it's "just data" in the Python config file, you could make the Python config instead slurp in an actual data file of your desired format (YAML, TOML, whatever), and then transform it into Python data structures as needed.