I've had very good luck with Sashido.io as a replacement. I ported two of my apps over - migration was easy and very smooth + support and responsiveness were outstanding.
Parse is shutting down today
121–130 of 297 posts
Re: Parse is shutting down today
#122Re: Parse is shutting down today
#123Earlier quoted context omitted.
That's really awesome! I'm glad to see you've also solved a lot of the req/s issues that Parse had too. If prototyping tools are done right, I think they are valuable and awesome.
Thank you for the praise, however i really want to stress that Sub0 (and PostgREST) are not prototyping tools only :) It's true that you don't build api's with them the way you would with a more traditional stack but you can build real products with this a lot faster. This style of building APIs clicks faster with people that use (and trust) Postgres
Do you have any nontoy examples of this? I.e. nontrivial apps in heavy use.
Re: Parse is shutting down today
#124Earlier quoted context omitted.
I have created a few apps using Parse.com, one of them successful enough to take the additional time/cost hit to migrate and host myself using the Parse-Server project. The open source project is great and I appreciate the effort that went into making sure we didn't all get (totally) screwed. Would I use Parse-Server for a new project? Probably not. The state of the BaaS options out there has changed/improved signifi…
Which BaaS options are recommended now?
Scaphold (https://scaphold.io/) is a super neat BAAS built on GraphQL!
Re: Parse is shutting down today
#125A key takeaway from this; and one of the main reasons parse failed-- don't name a company or service after an extremely generic programming term. Parse failed for a lot of reasons but I hated it because the documentation was terrible at the beginning and used to get me stuck in a forever loop of links. So I searched for additonal info: "Parse javascript" "Parse website library" "Parse programming" Admittedly contrive…
That sure wasn't one of the main reasons Parse failed! It is annoying though. Perhaps we should have taken over some similar term, like "golang".
Re: Parse is shutting down today
#126I have seen a fair number of "abrupt" and poorly executed shutdowns on HN over the last few years, and although I don't use Parse, I feel as though the team did a good job sunsetting this over the last year. Thank you for the product, the open sourced version, and for not ditching your community! Best of luck to everyone who worked on the team
They did a great job with Parse server, but unfortunately for people who just wants their data they basically have been abandoned. Exporting data in JSON format is no longer supported. The featured has been left broken without any explanation, and they disabled the ability to contact them in regards to data export.
You could very easily have created a free mLab account, migrated the data, and exported it from there...
Re: Parse is shutting down today
#127Why do I feel like this post is getting brigaded by Sashido?
Re: Parse is shutting down today
#128I 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.
Re: Parse is shutting down today
#129I was never a huge fan of parse, having seen startups fail hard when using it, and I've been pretty vocal about that in the past [1]. It was a great idea in principal, but failed pretty hard when faced with the reality of non-toy development. I generally hate to see projects fail, but in this case I'm not terribly upset. I think that people were getting sucked into the ease of getting apps up and running quickly, the…
Did you vocalize any of these issues anywhere? I have never used Parse but have been looking at the open-source version. What are the many, many glaring bugs and problems you're referring to?
We would all go crazy trying to report all the bugs we found in every piece of software out there these days. When there are too many or something is too difficult to use, you move on. To a large extent, finding bugs is the responsibility of the developers. When users submit bug reports, good ones at least, they should be thanked. My point is, as a developer, you can't blame the users for not reporting bugs.
Re: Parse is shutting down today
#130We loved Parse! It all started out for them with this community. Sad to see them shut down. We moved away a week ago. Of course, last moment. We have a huge user base and managed to transition what we thought would be a nightmare process, to Sashido. I saw a few others mention them as well.
Their team helped us tons in doing the switch. Probably, we sent 50 emails back & forth on details. Don't know how these guys didn't hate us! Super responsive and caring team! Big kudos to them. They saved our butts.