3 ms·
Freaking awesome! So much to learn from the code from these guys... plus easier to use, more trustworthy... and you don't have to wait for the vendor to fix cri
by andrewljohnson 11y ago
Freaking awesome! So much to learn from the code from these guys... plus easier to use, more trustworthy... and you don't have to wait for the vendor to fix critical bugs when needed.
I'd really like to see all infrastructure SDKs open sourced (obviously a tough sell, but maybe Parse paves the way). In building our core stack, we don't tolerate closed source. But we end up allowing it for things like Crashlytics, MixPanel, Segment, etc - and it's not a free lunch.
- jamesjyu 11y agoThanks Andrew! Transparency and community involvement is our top priority here. Also, we're doing a series of blog posts that will cover each part of the SDK stack. Lots of learnings to share from our kick ass SDK team. Here's the first: http://blog.parse.com/learn/the-parse-sdk-whats-inside/ http://blog.parse.com/learn/the-parse-sdk-whats-inside/
- franklinho 11y agoYES! It's so important to be able to look under the hood with these things. When I was working at MoPub, our open source SDK was one of our major selling points.
- andrewljohnson 11y agoCorrection, MixPanel and Segment SDKs are open source. I don't know why I thought otherwise: https://github.com/mixpanel https://github.com/mixpanel https://github.com/segmentio https://github.com/segmentio