3 ms·
Out of curiosity, I thought there were a few blog posts about how Parse is written in Go. But based on this blog post, it looks like you are re-implementing ht
by didip 11y ago
Out of curiosity, I thought there were a few blog posts about how Parse is written in Go.
But based on this blog post, it looks like you are re-implementing https://github.com/ParsePlatform/parse-server https://github.com/ParsePlatform/parse-server as a node app. Why not open source the original code?
- zitterbewegung 11y agoIt could be because Parse was engineered not to be easily deployed but heavily dependent on Facebook infrastructure or the code that is there isn't fit for release.
- ec109685 11y agoIt didn't use Facebook's infrastructure: https://aws.amazon.com/solutions/case-studies/parse/ https://aws.amazon.com/solutions/case-studies/parse/
- aikah 11y agoIt was originally written in Ruby , then they rewrote the API in Go. I guess they can't opensource the Go code for legal reasons. Maybe the parse-server written in Node JS was an experiment they did before when they were still choosing a new technology for the rewrite.
- supster 11y agoThe Parse infrastructure itself was written in Ruby then in Go. But the customer facing CloudCode feature was in a Node.js environment. Thus it makes sense that Parse Server which needs to run this cloud code would be in Node.
- gedrap 11y agoI think there are plenty of reason for this, and the question should be 'why open source the original code rather than having a clean start without all the dependencies and ugly things that accumulated over the years?'. Once it's open, people will scrutinize everything, especially something as high profile as parse. They don't need publicity about commit message "Joe is so fucking stupid" that slipped away or something equivalent.