3 ms·
It's not towards "less back end", and it's not "awkward". Since the dawn of time, everyone has been trying to do more stuff with less energy. Backend, frontend,
by StavrosK 10y ago
It's not towards "less back end", and it's not "awkward". Since the dawn of time, everyone has been trying to do more stuff with less energy. Backend, frontend, transportation, everything. That's why there are frameworks, and that's why, these days, we're fortunate enough to be able to glue a heap of libraries together and pretty much only need to write the functionality that's novel.
I think that the author is doing everyone a disservice by framing it like that. I don't even know where to begin to detail where he's wrong: Backend devs are the first people who want to write less backend (they're the ones writing all the libraries!), deepstream isn't a novel idea (it looks like it makes the 90% easy and the 10% horrible), pushing all the code to the client isn't a good idea (just imagine how long it would take to update every client when you discover a critical bug, rather than the three minutes you can update the server), etc etc.
It's a nice service that will allow people to prototype much faster and more easily, and I guess the controversial stance and title of the article worked very well for getting the clicks.