3 ms·
> even with open-source, you're never going to sit and read the code (of the program AND its dependency tree) You don't have to. The fact that it's possible fo
by nkmskdmfodf 2y ago
> even with open-source, you're never going to sit and read the code (of the program AND its dependency tree)
You don't have to. The fact that it's possible for you to do so, and the fact that there are many other people in the open source community able to do so and share their findings, already makes it much more trust-worthy than any closed apple product.
- stephenr 2y agoJia Tan has entered the chat.
- tobias2014 2y agoI hope you bring that up as an example in favor on open-source, as an example that open-source works. In a closed-source situation it would either not be detected or reach the light of day.
- stephenr 2y agoIn a closed source situation people using a pseudonym don't just randomly approach a company and say "hey can I help out with that?" It was caught by sheer luck and chance, at the last minute - the project explicitly didn't have a bunch of eyeballs looking at it and providing a crowd-sourced verification of what it does. I am all for open source - everything I produce through my company to make client work easier is open, and I've contributed to dozens of third party packages. But let's not pretend that it's a magical wand which fixes all issues related to software development - open source means anyone could audit the code. Not that anyone necessarily does.
- ddingus 2y agoTHIS! Back when I was new to all of this, the idea of people evaluating their computing environment seemed crazy! Who does that? Almost nobody by percentage, but making sure any of us CAN is where the real value is.