Comment by throwaw12
15 hours ago
I liked the idea as well, maybe OSS should adopt 6 months availability and 6 months for enterprise support schedule. This way both could benefit, OSS gets more funding, enterprise gets support (cheaper than hiring full-time employee for specific OSS)
nice idea to time vacation in the summar, right around major security conferences (blackhat, defcon, etc), when large bulk of CVEs get published, to put some fire under the enterprise butts
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?
End goal of complaining that no one pays for their efforts.
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.
5 replies →
> 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.
bait and switch
1 reply →
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
3 replies →
AI-slop PRs automerged in response to AI slop bug reports.
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.
2 replies →
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...
1 reply →
Isn't that what we have already?
That’s just the status quo.
Please go ahead and fork curl
Ah yes, people will just be clamoring to use hURL
Or the Rust re-write rURL
1 reply →