4 ms·
Why limit it to open source? You wouldn't let an engineer build a bridge with car-sized holes just because the blueprint is not open.
by mkl95 4y ago
Why limit it to open source? You wouldn't let an engineer build a bridge with car-sized holes just because the blueprint is not open.
- deleted 4y ago[deleted]
- kube-system 4y agoThere are different questions that should be asked when choosing open source software vs proprietary software. If you're using proprietary software, you might ask things like, "what's your SLA?", "can we review the source code?", or "how much is a license?" If you're using open source software you might ask things like "is the project maintained?", "who developed it?", or "do we have anyone on payroll who knows how thing works?" So yeah, it makes sense to treat them differently, at least in some respects.
- PaulDavisThe1st 4y agoFor the sorts of purposes described in bill-blurb, the questions would be essentially identical.
- kube-system 4y agoNot really. The managerial process for fixing a vulnerability or mitigating supply chain attacks in an open source project is functionally different than for a proprietary product. So much so that it’s often the subject of memes (and frustration) in the FOSS community when people don’t understand the difference. Stuff like this: https://daniel.haxx.se/blog/2020/12/17/curl-supports-nasa/ https://daniel.haxx.se/blog/2020/12/17/curl-supports-nasa/ Or this: https://daniel.haxx.se/blog/2022/01/24/logj4-security-inquiry-response-required/ https://daniel.haxx.se/blog/2022/01/24/logj4-security-inquir... … is exactly why you can’t treat them the same in these types of situations.