Until someone races to the bottom to do 12 months of availability.
replyA race to the bottom of… unpaid work that eliminates the paid work? Can you elaborate?
replyCoz just about everyone wants to be that one guy in Nebraska thanklessly maintaining this bit of digital infrastructure, apparently?
replyYeah 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.
AI-slop PRs automerged in response to AI slop bug reports.
replyRaces 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?
reply> at they become the most popular OSS toolkit, with an end goal of … what?
replyLook at how any "FOSS + VC + for-profit" company in the last 5-10 years worked out, and you'll see the playbook.
bait and switch
replythen it is up to community to fork the project if they find it valuable and can convince people migrating to their fork.
replymany 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...
replySince then a diff of the two projects will be a perfect list of security issues and will make designing an attack rather easy...
That’s just the status quo.
replyPlease go ahead and fork curl
replyAh yes, people will just be clamoring to use hURL
replyOr the Rust re-write rURL
reply