Slashdot Mirror


Why Facebook Really Shut Down Parse (medium.com)

New submitter isisilik writes: For those working in the 'aaS' business the Parse shutdown was the main topic of conversation this weekend. So why did Facebook decide to shut down their developer platform? The author claims that Facebook never wanted to host apps to begin with, they just wanted developers to use Facebook login. And he builds up a good case.

1 of 39 comments (clear)

  1. Re:The one lesson developers should learn by tylersoze · · Score: 1, Offtopic

    Really dude? It's more of the fact it was an easy to use service that wrapped a nice API around a solved problem. I'm a mobile app developer I just want an easy to use standard REST/CRED database backend I can connect my app to save my data. I don't want to program a back end for a solved problem. The only issue with Parse was it was developed, hosted and run by another party. Obviously the best approach would be to host the service on your own servers, Facebook is thankfully making the code available to do that. As long as you're not writing even single bit of code yourself you're always going to be depending on some else, whether it be for the language, the server, the database, the OS, etc and have to hope they keep supporting whatever stack you decided on it. It's just a matter of where you draw the line.