this post was submitted on 28 Mar 2025
221 points (98.7% liked)
Technology
68305 readers
4306 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Often, these include code that they don't have the rights to publish.
I feel like 99% of the time that's just a lazy or misleading excuse. I've worked in proprietary software development for 25 years and I've never worked for a company that didn't avoid restricted third-party code like the plague at all times. In the few, rare cases when we did have to use some proprietary third-party licensed library, it was usually kept very compartmentalized and easy to drop out of the code specifically because we were always afraid the other proprietary code vendor could fuck us and jack up their prices or find some nasty way to make our lives difficult.
The excuse that there is some secret but legitimate third-party code they're not allowed to share simply doesn't hold water in the vast majority of cases.
More likely answers are that some beancounter somewhere still imagines that the proprietary source code could possibly be valuable in some hypothetical future acquisition (nonsense of course) even though it has no real commercial value, or fears that it could expose the company to liability if some security flaw or licensing violation is found (more plausible).
Ironically, perhaps the most likely reality for this resistance is that the software actually includes code that dictates they were actually always obligated to publish the source but never did. ie, GPL-based code. GPL violations are all too common in proprietary software and very few organizations have codebase governance effective enough to keep the situation under control with developers copy-pasting from anything they can find on Google. Releasing their plagiarized GPL source code would reveal to the world that they were not in compliance all along. Let it quietly die, and nobody ever finds out and they get away with it. It's not simply that they're embarrassed by bad code, it's that their bad code will potentially incriminate them. Not worth the risk, and sometimes it's not just a risk it's a certainty.
The proprietary software industry relies on open source so much and rarely gives much of anything back. I'm fortunate that the company I'm working for now actually takes licensing seriously and does contribute to open source projects to some degree, although I keep insisting they need to do better.