Half the time it's because it's FOSS with a proprietary skin over it.
this post was submitted on 30 Sep 2023
757 points (96.7% liked)
Programmer Humor
32410 readers
1 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
On the other side there's people that genuinely use that as an excuse and say "they'll open source after they cleaned up the code". Why they couldn't clean it up in the clear is beyond me, no one will shame you for your code, just sharing it under a free license is admirable in and of itself
Plenty of people will
Will what? I'm confused
They will shame you, for your messy code. People suck sometimes.
That's awful, I guess I should consider myself lucky that nobody looks at my repositories then. But still, if someone does they're the assholes, you shouldn't feel bad about it, you should actually tell them to fix it themselves if they're so good
Those are the kind of people who will always find something to ridicule or complain about, though, so you should never let their hypothetical bitching affect your decisions.
I open sourced my code so other people can clean it up *tap head*
Gigabrain, going for the afk grindset
I was watching a YouTuber going over a major revision update for a framework or something and he said "I skipped over the part where I was coding this" nah dude, I wanna see that as well. What did you try and how did it go.
So much weird ego in coding.
Asshole take: if you share your project online but not the source code I immediately think your code sucks.
Let's be real your clone project is not something a venture capitalist is going to invest in, there's literally no reason to hide it but shame. Shame of sinful and bad code.
This applies to any project, really. At my workplace, if someone refuses to let other teams look under the hood of a product, 95% of the time, it's because their code is absolute garbage, but their leaders didn't want to wait so they pushed it to prod and now it's up to some junior employee to fix all the shit that blows up in prod.
And just for closure, 5% of the time, it's because there actually is no product at all.
I have a project that I shared online, and the source code isn't shared BECAUSE it sucks lol
For certain projects I monetize, there are reasons I don't share the code.
Patents don't magically find people infringing your intellectual property. The owness is on you.
That being said, I have bills to pay, and mouths to feed. Giving my solutions away for free, doesn't help those issues.
I make all my sucky code public because I've never seen a codebase that doesn't suck in some way
High five!
My code might be garbage, but I've learned that no one will notice in this aisle of trash heaps.
I have a private repo on GitHub that is private for this reason. I made it in a weekend for fun, and it's honestly so bad. I have spent way longer fixing dumb mistakes that I spent developing the main features in the first place. But I learned a lot while doing it (and fixing it), and my current project that I'm working on is much, MUCH better. I do have it in a public repo.
Are you me?