Comment by charcircuit

14 hours ago

Until someone races to the bottom to do 12 months of availability.

Races to the bottom to … do work exclusively for free and not make any money out of the hopes that they become the most popular OSS toolkit, with an end goal of … what?

  • Validation, often. Stars and installs make self-worth integer go up, etc.

    Greed, sometimes. Gotta get those usercounts high to get acquihired / to sell out / to flip on the paid subs for formerly free features.

    I can’t remember the word for “prosocial through lowering cost to zero” is but sometimes that too.

  • > at they become the most popular OSS toolkit, with an end goal of … what?

    Look at how any "FOSS + VC + for-profit" company in the last 5-10 years worked out, and you'll see the playbook.

A race to the bottom of… unpaid work that eliminates the paid work? Can you elaborate?

  • We don’t need to speculate do we, there are tons of real non company run OSS projects

    Now I personally wish lawyers and plumbers also got into the free work thing but here we are

    • Plumbers are realistic and don’t live on ideals. They set their rates and set their hours. Lawyers; well if if only people behaved we could have nice things in life, but here we are with people trying to screw each other and misbehave…

      Digital assets or work are a bit different in that making a second copy is trivial. It’d be different if every computer in the world were bespoke and needed its own bespoke software. So that makes OSS a viable option for those who can but we also can’t expect everyone to default OSS. We can default to asking that the service and prices be reasonable though.

  • Coz just about everyone wants to be that one guy in Nebraska thanklessly maintaining this bit of digital infrastructure, apparently?

    Yeah me neither.

    I think the only thing that would convince people to move away from curl at this point would be if curl had a heartbleed level vulnerability and failed to fix it quickly.

    • Curl is so important that if it had a heartbleed and didn’t patch, someone would and people’d just apply it until it was fixed in tree.

    • Individuals don't but lots of companies do, so that they can threaten to rugpull it later if you don't pay them millions.

then it is up to community to fork the project if they find it valuable and can convince people migrating to their fork.

many engineers actually work that way, right? We are employed for 12 months and give our availability fully to the company and we get salary for it, why isn't it allowed to others?

  • A fork of a project that does security patches only is an interesting idea...

    Since then a diff of the two projects will be a perfect list of security issues and will make designing an attack rather easy...

    • Only until the next feature lands in upstream, likely accompanied by some refactoring.