They might rely on parts that have non open sourced drivers or firmware. Perhaps different parts of the code were authored by different people and they need everyone approval.
Fear of embarrassing code is often a factor too. Amazing how coding standards instantly improve across the board the moment you realize people outside of dev might be scrutinizing what you’ve been shipping to customers.
True programmers know that novice code is a rite of passage. Every programmer worth their salt looks at their own older code and cringes at it. Most people who do this for a living are more likely to give helpful pointers rather than tear you down, if anything.
If someone is being a jerk to you about your code, stop listening to them immediately and walk away or block them.
These guys are out of business anyway. They don’t have to care; they can just dump whatever they have somewhere and scuttle off into the night, never to be seen again, nothing more than an echoing “woop woop woop woop” fading off into the distance.
They’ve been handed a rare and highly valuable treasure. They get all the good will from the community for doing the one thing that everyone always wants these companies to do but never happens, and this is now someone else’s problem.
If you’re going to have a problem, someone else’s problem is the best kind to have.
OpenSourcing is a good move
What is “trying to” open source though? Make the GitHub repo public, include the database schema, and you’re done.
What ever could go wrong with that?
Oh, right. Winamp very recently showed us exactly what could go wrong with that.
Didn’t know about that. That’s kind of bullshit that they took it down.
They might rely on parts that have non open sourced drivers or firmware. Perhaps different parts of the code were authored by different people and they need everyone approval.
Likely they have proprietary or otherwise private information they want to clean out first, or they want to make it more presentable or documented.
I agree I’m not a fan of the “trying to” phrasing either.
Startups like this aren’t known for their robust infrastructure design.
It’s most likely running on some weird unicorn setups no-one has bothered to document.
With passwords in the code and such.
Fear of embarrassing code is often a factor too. Amazing how coding standards instantly improve across the board the moment you realize people outside of dev might be scrutinizing what you’ve been shipping to customers.
This is true even for my personal projects lol
I literally added pre commit checks to my personal repos today to lint and format
I’m not a programmer but dabble. I’m always so nervous when actual programmers look at my code.
True programmers know that novice code is a rite of passage. Every programmer worth their salt looks at their own older code and cringes at it. Most people who do this for a living are more likely to give helpful pointers rather than tear you down, if anything.
If someone is being a jerk to you about your code, stop listening to them immediately and walk away or block them.
yep, do this all the time with my own code… even for yesterdays code prior to second coffee time!
This guy codes.
These guys are out of business anyway. They don’t have to care; they can just dump whatever they have somewhere and scuttle off into the night, never to be seen again, nothing more than an echoing “woop woop woop woop” fading off into the distance.
They’ve been handed a rare and highly valuable treasure. They get all the good will from the community for doing the one thing that everyone always wants these companies to do but never happens, and this is now someone else’s problem.
If you’re going to have a problem, someone else’s problem is the best kind to have.
Probably a lot of stolen code
Definitely missing documentation to make it a proper repo
Yeah it’s so simple, no way they could be the good guys, can’t have that.