3 ms·
I feel like we just need new terminology. Visible source, for example. As the author says, "There's absolutely no problem with proprietary software". To me, the
by noduerme 3y ago
I feel like we just need new terminology. Visible source, for example. As the author says, "There's absolutely no problem with proprietary software". To me, there is a problem with it under some circumstances if I can't inspect the source. A lot of times you aren't including it in your own code, you're just using it in your toolchain and you want to make sure it isn't poisoned. "Open source" as a phrase has become a stand-in for being able to check the source, but obviously as the author points out it's a misnomer, and can be used for misdirection. Why can't we just call it "visible source" when this is the case, to avoid confusion or false marketing?
- commoner 3y agoWouldn't "visible source" be exactly the same thing as "source-available"? https://en.wikipedia.org/wiki/Source-available_software https://en.wikipedia.org/wiki/Source-available_software