3 ms·
Often commercial software has tons of closed-source libraries that they don’t have the source code to. Even Doom had that when opensourced. It’s an annoying hea
by bombcar 4y ago
Often commercial software has tons of closed-source libraries that they don’t have the source code to. Even Doom had that when opensourced. It’s an annoying headache for a company to open source even for a project no longer in development.
- yjftsjthsd-h 4y agoThey could still release what they do have. Depending on the nature of the missing bits, the community sometimes can replace or shim out chunks of proprietary code and still have an easier time than replacing the whole thing. Or, depending on the licenses involved, it can be possible to at least release object files so people can edit the core code then link against closed libraries to build the final library. That's what happened with OpenSolaris - Sun released most of the OS as open source, but couldn't relicense some chunks, so they released a bunch of blobs that had to be injected into the build to create the final product; AFAIK some of these persist as annoying blobs to this day, but some were replaced piecemeal by illumos with FOSS versions. (Obviously, this is very dependent on how much lifting is done by what parts and how specialized they are; if you happen to use a closed zip library, that's easy for the community to work around, whereas if your app is a thin wrapper around another closed library then maybe opening it really is minimally useful)
- bombcar 4y agoYeah, and it does happen (rarely) - the best way to get it to happen that I've seen is to have a major customer ask for it. So instead of normal users asking, have Ford ask for a guarantee that X years after maintenance ends, the portions of the code that can be GPL will be, or something. Even then it's rare to work, but it sometimes can.
- bsder 4y agoIn this instance, though, the protocol is more valuable than the software. If they released documentation on the Firewire protocol, likely somebody could write the software to talk to it fairly quickly. Hardware protocols are almost always the simplest thing that could possibly work--and generally simpler than that. As one myself, I assure you that hardware people are LAZY. :) (In reality, the issue is that hardware is really difficult to change and expensive to develop. Consequently, you want your hardware to be simple and robust while pushing as much complexity as you can up to the software stack.) Or, even more importantly, if they released some schematics and documentation, that Firewire port could be replaced by an Ethernet port. The sticking point is likely the word "documentation". I suspect that "documentation" doesn't exist anymore--if it ever did.