Slashdot Mirror
Facebook Is Shuttering the Parse Developer Platform (cio.com)
itwbennett writes: In a blog post yesterday, Facebook announced it is shutting down the Parse developer platform as of Jan. 28, 2017, giving developers a year to move off its hosted services. This comes as a bit of a surprise, considering that just last month, Parse launched a set of new tools to help developers work with Apple's watchOS and tvOS last, and at the time, Parse Product Manager Supratik Lahiri promised more updates in the future. Developers who don't want to rewrite their applications to work with a new back-end service provider can follow a migration guide from Parse to make their applications work with an independent MongoDB instance and a new open-source Parse Server that's running on Salesforce-owned developer platform provider Heroku.
... another web API bites the bullet and all the kids will have to go learn yet another flash in the pan interface to connect to some moronic social site to scrape bullshit data to pass to an app they can sell to idiots.
you might care, if only we had https://www.google.com/search?...">ever heard of Parse. At this point it seems pointless to go
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
This is the technological equivalent of obsessing over some Kardashion boob job.
When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
over-reaction. They're giving a migration path that basically lets you run it self-hosted.
Price, Quality, Time. Pick none. What, you thought you had a choice?
Actually I think the plan is to migrate to another host provider. Until that one decides to drop it.
It ends when the hipsters are kicked out of the industry. They've ruined everything they've touched. They ruin UIs that were good. They create awful frameworks. They prefer to use the absolute worst programming languages, like JavaScript, for everything. They took git and centralized it on GitHub. They're too lazy and/or dumb to learn SQL, so they use persistent hashtables for storing data, and query it using imperative JavaScript code. It's nothing but idiocy and disaster when it comes to these people. It doesn't matter if it's an 18 year old hipster or a 30 year old hipster or a 55 year old hipster. They all need to find a different occupation.
So, whoever wins, we lose :)
What the fuck? Are you writing C++ code like it's 1987? You do know that the language has evolved, right? If you use RAII and modern C++ techniques, you can develop massive software systems without dealing with raw pointers even once, for example. You get the safety of Rust, but without the many downsides of Rust.
Rust is a lot like Ada. It's all hype, and much less substance. Whatever small amount of safety you might get over C++ is totally outweighed by the problems that Rust and Ada have that C++ just doesn't have. Those who might benefit from using Rust or Ada will just do what they've always done, and use a safe subset of C++ instead.
Everything you wrote about Ruby is wrong, too. The standard library is quite lacking. That's why you need to use so many goddamn Ruby gems in order to do anything remotely useful. And if you'd ever actually dealt with Ruby gems, you'd know how goddamn awful they are to work with, since the Ruby ecosystem is fragmented and total shit. Ruby on Rails alone changes so much between major releases that upgrades become a big disaster. Each major release of Ruby on Rails essentially is a new framework, they just all have the same name!
You should be careful about using insults like "fanboy", too. Name-calling like that could put you in violation of the Rust Community Code of Conduct! The Rust Moderation Team could then come after you.
Parse is/was a service that allowed people who knew next to nothing about server programming to cobble together a backend for a mobile app (or other app that can make http requests).
So in other words it was a tremendously useful or harmful service depending on your level of cynicism. It is of course hard to monetise a solution like this, since any app that becomes highly profitable will attract developers that know how to build a proper backend and then that app will migrate away and stop paying monthly fees.
And when it comes to Ruby having an anemic standard library, let's look at the libraries that are included with a vanilla install of Python versus a vanilla installation of Ruby:
Decimal arithmetic:
Python: decimal, Ruby: BigDecimal
Templating:
Python: string.Template, Ruby: ERB
Logging:
Python: logging, Ruby: Logger
Compression:
Python zipfile, Ruby: zlib
Argument parsing:
Python: argparse, Ruby: optparse
XML:
Python: xml, Ruby: REXML
Encryption:
Python: crypt, Ruby: openssl
Again, all these modules are included out of the box. No RubyGems required.