Why do I feel like this post is getting brigaded by Sashido?
Because it is. Makes me begin to regret my decision of migrating my parse server to them, but I will say that they did make it easy to migrate over and answered my questions promptly.
Parse is shutting down today
141–150 of 297 posts
Re: Parse is shutting down today
#142During this year-long shutdown/migration process, the open-source and community maintained Parse Server is what most people switched to. Parse is yours now. https://github.com/ParsePlatform/parse-server
Something I've been wondering is would you recommend using the open source Parse server for new code or is it more targeted towards projects that were already using the Parse API?
Erik, I recommend use Parse Open source to any kind of App project that needs a robust backend. It is awesome, simple to install and to maintain.
Re: Parse is shutting down today
#143Earlier quoted context omitted.
That would likely be overly onerous...what if they use licensed 3rd party components?
And in such a case, an Open Source mandate would directly conflict with the financial interests of the investors (the time required for the effort takes away from the liquidation amount of the remaining assets.
It would only if the software source or patents compromised the value they gained from the business. This would be the case for some startups. It wouldn't be for others where brand, talent, & existing users were what they were after.
It also wouldn't take any significant time given developers could just push the final source and docs into a Github repo with a license. Or just dump it as a zip on the web. That's nothing. Also a good chance that at least one ex-developer would like to do it just so their work wasn't totally wasted.
Re: Parse is shutting down today
#144I loved Parse from the time I first started using it in college. It started out as a really handy way to spin up small apps quickly so I could start beta testing my app quickly with real users. One of the main problems though was that it really felt like just a prototyping tool to me, and I never really used it for real apps in production. Thus, for my latest project that I've been working on for several months now,…
I was wondering if you have a public policy in place which outlines what would happen in the event of a Parse-like shutdown or other end-of-company-life event occurring? I ask in the hopes that it won't be taken as too negative a question but your company is VC-backed in the database space and we've lost a few too many of those this last year.
That's a very valid concern, and I appreciate you asking. One of the (many) benefits of using GraphQL is that it's an open standard.
And in the event of a Parse-like shutdown, migrating off of a hosted platform like Scaphold is much less painful since you could quickly spin up a GraphQL server on your own with the same GraphQL schema that you can easily export from Scaphold. Regarding the data you have stored in the system, we work hard to let you use as much of your own data as possible from various services across the web, so even if we shut down, your data still lives across those other service providers that you use. In addition, we'd be happy to give you a full export of your data in any format you wish. We use an underlying MySQL database behind the scenes, and migrating your data from one SQL database to another is much more structured than moving off of a Mongo database (Parse's data layer).
We're also pushing out more and more support for tying in your existing data hosted elsewhere on the web with advanced custom logic hooks that can tie into your other APIs and data layers as well.
Re: Parse is shutting down today
#145Earlier quoted context omitted.
Yeah, that's pretty impressive. YC should consider making it a requirement of funding that the components go open-source if they shutdown without acquisition, etc. Aside from collective benefit, a future, YC startup might get a head start from their docs or components. They seem to fund multiple startups in the same market segments at times.
That would likely be overly onerous...what if they use licensed 3rd party components?
They'd have to be left out. The rest could be open-sourced. If 3rd party stuff is hidden behind API, it could even be replaced with open-source stuff. That's not even necessary as my recommendation is to not overly burden the startups with this requirement. They just dump what's theirs somewhere under FOSS license. Others can do the necessary work of dealing with missing, 3rd-party components if they want to reuse the FOSS code.
Re: Parse is shutting down today
#146I've spent the last 15 minutes on parse.com, github.com trying to find out what the parse backend actually is. Can someone explain?
Same here, arguably this is one of the most important elements on the front page, open source or not.
Look at this open source project for example: http://activeadmin.info/
The front page doesn't leave you wondering why the fuck do you want to use ActiveAdmin for.
Re: Parse is shutting down today
#147Sashido is a solid alternative for a quick and easy implementation for those who need something similar to Parse.com style services
Is Sashido using the parse server for their army of HN spam accounts?
Re: Parse is shutting down today
#148Earlier quoted context omitted.
Shutting down is not the same as failure
But it is a reasonable enough definition of it that we should be able to apply the principle of charity to calling it a failure, no? It is not something anyone would mistake for "success" on its own terms, even if the people involved did OK for themselves.
It really depends on the goal. It's a success if the goal was to build something to be IPO'd or acquired for benefit of investors and founders. It was a big success in that regard. It's a failure if the goal was mainly to benefit developers. That wasn't the main goal. Incentives like this are why I don't use VC-funded stuff unless I have a fall-back option. Risks also apply to proprietary software in general but many suppliers are more interested than startups are in sucking money out of you for long-term. Market leaders stick around longer.
Re: Parse is shutting down today
#149Why do I feel like this post is getting brigaded by Sashido?
I was about to say the same thing. At this point I can't tell who is genuinely recommending me a service and who is shameless plugging.
Re: Parse is shutting down today
#150:DDDDDD all for the happy moments Parse geve i and my team.
We like focusing on building amazing apps so hosting our own Parse Server wasn't an option. After trying 2 service providers an patiently waiting for the easiest yet consistent with Parse Philosophy solution... Outta notting came Sashido.io :DDDDDD these now are for the happy moments Sashido is giving me. They are professional, nice support, easy to get along with. The technical aspects ill share in a proper blog post.
Thank you Parse, always