Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Parse is shutting down today

status.parse.com

Post reply on HN
Print view View original

181–190 of 297 posts

Re: Parse is shutting down today

#181

Post by 010a »

primitivesuave wrote: post #60
jeyoor wrote: post #44

Earlier quoted context omitted.

Which BaaS options are recommended now?

I second the Firebase recommendation. Facebook killed off their BaaS acquisition while Google doubled down on theirs. If you prefer open-source, Horizon ( http://horizon.io/ ) is a great alternative to Firebase but does not have many of the key features like file storage and iOS/Android SDKs.

Horizon is a scary recommendation right now given the recent shuttering of RethinkDB (the company). It might still be a great choice, but I would give the community some time to coalesce and see where things end up before recommending it for new projects.

Re: Parse is shutting down today

#183

Post by flovilmart »

alysson_b4a wrote: post #161

I would like to make an appeal. Let's use this post as a great recognition for the Parse team hard work and share also our lessons learned using Parse/Parse Server as a Backend. Thank you, Thank you guys. @csmajorfive, @gfosco, @laker, @HectorRamos,@jamesjyu, @flovilmart ... and everyone else

Thanks for the shoutout, but I'm not part of the parse team :)

Re: Parse is shutting down today

#184

Post by realPubkey »

ahelwer wrote: post #180
realPubkey wrote: post #131

So the alternative options are: - pouchDB - https://github.com/pouchdb/pouchdb - RxDB - https://github.com/pubkey/rxdb - gunDB - https://github.com/amark/gun - horzion - https://github.com/rethinkdb/horizon - firebase - https://firebase.google.com/

Kind of strange that you just threw in RxDB (your own creation?) and GunDB (which is easily torn apart as snakeoil whenever it appears on HN) along with the rest of them.

Yes RxDB is my creation. Didnt know that GunDB is not liked here, do you have a link for me?

I just wanted to have a next-to-complete list.

Re: Parse is shutting down today

#185

Post by BinaryIdiot »

eriknstr wrote: post #25
gfosco wrote: post #2

During 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?

It's geared towards legacy. I have used parse in 3 different projects (none of that was my choice, these were existing projects I had to take over) and I would NEVER recommend it for new projects.

The way everyone seems to use it, in my experience, is giving the client credentials to manipulate the full database which is absolutely insane. Obviously this is not good practice but every single parse project I've gotten thrown into already did this and it was a significant amount of work to move it to be more secure and NOT do that. I think the way it's created makes it very, very easy to make bad security choices.

It's also basically a RESTful CRUD. That's mostly it minus some, mostly minor, bells and whistles. You can already do this with about 20 different open source stacks very easily and you're not stuck using this parse technology.

I can't articulate just how much trouble parse has given me. I even took an app and re-wrote its entire backend away from parse significantly faster than doing a handful of updates.

Re: Parse is shutting down today

#186

Post by beachstartup »

djm_ wrote: post #159
beachstartup wrote: post #140

Earlier quoted context omitted.

if you run a company or product, it's on you to make sure your data is recoverable and your product is fixable in the event of an outage. expecting a vendor to tell you exactly how they're going to fold is something they can surely dream up and send to you so you feel better about the nature of the universe, but something you shouldn't really rely on. in other words, assume the worst will happen, despite assurances o…

Fully agreed, I still find it helpful to judge the response and general attitude of the company in question though. In this instance, it was exactly what I was hoping for.

the problem is in many circumstances the entire management or operations teams can be forcibly removed by investors etc. many of these companies are all volatile, high growth venture-backed companies with financial and corporate shenanigans being pulled left and right.

i wouldn't say the risk is attitude, or intentions. you know what they say about good intentions...

Re: Parse is shutting down today

#187

Post by alysson_b4a »

flovilmart wrote: post #183
alysson_b4a wrote: post #161

I would like to make an appeal. Let's use this post as a great recognition for the Parse team hard work and share also our lessons learned using Parse/Parse Server as a Backend. Thank you, Thank you guys. @csmajorfive, @gfosco, @laker, @HectorRamos,@jamesjyu, @flovilmart ... and everyone else

Thanks for the shoutout, but I'm not part of the parse team :)

Yes, you are! Parse Server Team :)

Re: Parse is shutting down today

#188

Post by tommorris »

beachy wrote: post #61
geofft wrote: post #56

Earlier quoted context omitted.

When a marriage ends in divorce, it is fair to call the marriage a failure even if you get a profitable settlement from the divorce and even if you both go on to better marriages. Same reason.

Nice analogy, but we generally don't select development tools on the basis that we want to grow old with them.

Speak for yourself, but the longer the tool has been around, the more I trust it. One of the chief selling points of learning something like Vim or Emacs is precisely that it isn't going to disappear next week and become abandonware (TextMate) or just lose interest from people because something else came along (Sublime Text → Atom/VS Code).

Same with a lot of developer tools. (This is sometimes bad. It is still taking a long time for people to migrate to Python 3.x, and the transition from CVS/SVN to Git and other DVCS was pretty slow.)

Re: Parse is shutting down today

#189

Post by emresancaktar »

Parse.com is the best BaaS option I have ever used. Now Sashido took the best BaaS options flag from Parse.com. I am very happy to be in SashiDo.io and I really recommend for every developer. Because its same with Parse.com and they improve.

Re: Parse is shutting down today

#190

Post by jsmeaton »

nickpsecurity wrote: post #143
hkmurakami wrote: post #115

Earlier quoted context omitted.

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 nothi…

How many production systems have you come across that could be dumped onto the public without any cleaning? Credentials, build systems, personal information, patent use, are a couple of examples that I've seen in prod code that couldn't or shouldn't be included.

Assuming the cost of open sourcing something is zero, even if it's just a zip dump, is usually not correct.

Post reply on HN