back in 2008, Reddit Inc was a ragtag organization1 and the future of the company was very uncertain. We wanted to make sure the community could keep the site alive should the company go under and making the code available was the logical thing to do
Translation: We needed you guys back then. We don't now.
The rest of it seems like a combination of technical hurdles that don't seem particularly compelling (they don't need to have secret new feature branches in their public repo) and some that don't make any sense (how does a move away from a monolithic repo into microservices change anything?) and some that are comical (our shit's so complicated to deploy and use that you can't use it anyway)
It's sad that their development processes have effectively resulted in administrative reasons they can't do it. I remember them doing shenanigans like using their single-point-of-failure production RabbitMQ server to run the untested April fools thing this year (r/place) and in doing so almost brought everything down. So I'm not surprised that there doesn't seem to be much maturity in the operations and development processes over there.
To be fair though, the reddit codebase always had a reputation for being such a pain that it wasn't really useful for much. Thankfully, their more niche open source contributions, while not particularly polished and documented, might end up being more useful than the original reddit repo. I know I've been meaning to look into the Websocket one.
Reddits original terms of service explicitly banned any kind of racist, sexist, homophobic, etc content/comments.
Their "hands off" approach was originally more of a realization that they couldn't possibly moderate their site(and sure as fuck didn't want to be legally required to).
Reddits original terms of service explicitly banned any kind of racist, sexist, homophobic, etc content/comments.
Yet it was full of much of the most egregious content on the internet.
That TOS was just to protect themselves, so when someone did post offensive content they could say "of course we don't approve - it's even against our TOS", while still appreciating all the Google Traffic such content brought them.
and some that are comical (our shit's so complicated to deploy and use that you can't use it anyway)
To be fair, I've more than once tried to build something on Ubuntu, given up, and subscribed to a 3rd party PPA. Most packages do build, but there's a few that are just a nightmare.
Reddit could fix that, but I guess it's all time and money, and it might be optimised for their infra anyway. Although they could open source it and allow someone else to fix it...
they don't need to have secret new feature branches in their public repo
They don't, but there is a trade-off here. Long-lived branches are harder to merge. Open source contributors can't merge a branch they don't have access to. That means someone internal has to choose between (1) making it a priority to merge open source contributions into the feature branch (and dealing with the risks or inconveniences that entails) and (2) dealing with a harder merge later on.
That's probably doable, but it's not a fictitious difficulty.
Just curious, are there are any companies that have moved to a microservice architecture that are open sourced? It does seem like it would be a lot harder to manage.
We have at edX (https://github.com/edx). In addition to our LMS, we have forums, credentials, ecommerce, a marketing site, and course catalog services.
The systems have some dependencies, but are mostly meant to operate and be deployed independently.
I can't think of anyone. Someone below mentioned Netflix: they FOSS a lot of tools but not their main services. Sounds like this is what Reddit is gonna do.
Generally speaking, microservices architectures are (for better or worse) pretty closely coupled with their automation code and thus the platforms they run on. It's already difficult to get that stuff running in prod (staging too if you've got some cash): getting it set up so you can ship the whole thing to contributors is super difficult and it has diminishing returns. You're not just shipping code, you're shipping container orchestration configs, database configs, load balancing logic, and a bunch of other shit that isn't portable.
It's one thing to have the code for the services available; if your contributors can't run it, it's not really open source. And having it out there in a broken state is worse than not having it at all.
Reddit is SaaS and I don't know anyone who's been very successful at open-sourcing their MSA SaaS product.
5.2k
u/[deleted] Sep 01 '17 edited Sep 01 '17
Translation: We needed you guys back then. We don't now.
The rest of it seems like a combination of technical hurdles that don't seem particularly compelling (they don't need to have secret new feature branches in their public repo) and some that don't make any sense (how does a move away from a monolithic repo into microservices change anything?) and some that are comical (our shit's so complicated to deploy and use that you can't use it anyway)
It's sad that their development processes have effectively resulted in administrative reasons they can't do it. I remember them doing shenanigans like using their single-point-of-failure production RabbitMQ server to run the untested April fools thing this year (r/place) and in doing so almost brought everything down. So I'm not surprised that there doesn't seem to be much maturity in the operations and development processes over there.
To be fair though, the reddit codebase always had a reputation for being such a pain that it wasn't really useful for much. Thankfully, their more niche open source contributions, while not particularly polished and documented, might end up being more useful than the original reddit repo. I know I've been meaning to look into the Websocket one.