Live data from Hacker News

Parse is shutting down today

status.parse.com

41–50 of 297 posts

Re: Parse is shutting down today

#41
post #36
post #33

Ah yes, the day that so many unsupported apps stop working.

As for iOS apps, I imagine Apple's new attempt to remove unsupported apps from the app store will result in many of these apps getting the boot soon. I've already seen the notification when opening an app that it might perform slowly since it is not supported (or something along those lines).

I've seen a notification like that, but it had to do with an App not being compiled for 64 bit architecture.

Re: Parse is shutting down today

#42
post #39
post #16

Earlier quoted context omitted.

It's a shame so many people think of the Data Access Object design pattern as something only Java developers should be using. Using DAOs to provide database-agnostic access to your data takes a few moments more at first, but then when you need to move data from $DB_X to $DB_Y, there's a lot less wailing and gnashing of teeth. Mediocre link on the topic: https://en.wikipedia.org/wiki/Data_access_object

I'm not sure what your point is. Do you mean that if only people used DAOs then Parse shutting down wouldn't be a problem? It only encapsulates the problem. You still need to go through a process to switch from Parse to MariaDB or whatever else you switch to. You just don't have to rewrite your whole application. I'm in favor of DAOs and use them myself but they don't have anything to do with what I was talking about…

You made the point that the tradeoff can bite you. I mentioned DAOs as a way to make that bite less painful. Not a hard connection to make.

Re: Parse is shutting down today

#43
post #42
post #39

Earlier quoted context omitted.

I'm not sure what your point is. Do you mean that if only people used DAOs then Parse shutting down wouldn't be a problem? It only encapsulates the problem. You still need to go through a process to switch from Parse to MariaDB or whatever else you switch to. You just don't have to rewrite your whole application. I'm in favor of DAOs and use them myself but they don't have anything to do with what I was talking about…

You made the point that the tradeoff can bite you. I mentioned DAOs as a way to make that bite less painful. Not a hard connection to make.

That's what I assumed, but it wasn't totally clear that was your intention.

Like I said it does help but it's not a panacea.

Re: Parse is shutting down today

#44

Earlier quoted context omitted.

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?

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?

Re: Parse is shutting down today

#45

The export data feature has been broken for months — it’s stuck in the “waiting to begin…” phase. Is there plans to allow people to export their data? I’d like to get my data out, but both options for exporting data via the dashboard are broken. They also disabled the ability to contact them in regards to the export data functionality.

uhhh...sorry to say but I don't think you're getting that data out anymore. >When your app is disabled, you will not be able to access the data browser or export any data, and your applications will no longer be able to access the Parse API.

The apps were not disabled. The export feature hasn't been working because of a bug on their end. It seams like the claim that Parse "firmly believes in data portability" is complete BS.

Re: Parse is shutting down today

#47

I 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

Thanks mcescalante, we appreciate the kind words!

Re: Parse is shutting down today

#48

The export data feature has been broken for months — it’s stuck in the “waiting to begin…” phase. Is there plans to allow people to export their data? I’d like to get my data out, but both options for exporting data via the dashboard are broken. They also disabled the ability to contact them in regards to the export data functionality.

Email migration@parse.com for generic last-moment migration assistance.

Re: Parse is shutting down today

#49

Parse was an amazing discovery when I was just starting out my dev career and I've used it in all of my major projects, but it had some serious shortcomings. I wrote about why I think Parse failed from a developer's perspective. https://news.ycombinator.com/item?id=13522602

Why do you think Parse was a failure in the first place? Surely, Parse founders got a nice little cash out of the acquisition and Facebook got developers onboard and Facebook Login integrated onto many apps.

> Why do you think Parse was a failure in the first place?

Because the title of this post is "Parse.com is shutting down today".

Re: Parse is shutting down today

#50
post #37

The open source Parse Server offers more benefits than hosted parse.com. Many of the benefits are outlined in this blog post: http://blog.parse.com/announcements/what-is-parse-server/ Whatever you are building with Parse Server, Nodechef can help you get there faster. https://www.nodechef.com/parse-server

Are you a nodechef cofounder by any chance? I host with nodechef and am happy with them so far.
Post reply on HN