So apparently a bunch of people woke up this morning and decided Rails sucks.
Let me translate some of this for you.
I’m becoming more and more certain that this means that Rails-style MVC frameworks on the server-side are going to end up being phased out in favour of leaner and meaner frameworks that better address the new needs of thick-client architecture.
What that means is:
Part of the reason we have these monstrous frameworks is because at some point all software is just one giant if/switch around the seemingly endless list of bugs stemming from one of (client OS, client hardware, client browser, client plugins, deranged and clearly pants-on-head-stupid client workflows, and the vagaries of quantum physics.
But, because programmers think code rusts, and we love to rewrite the HELL out of it, we come up with new and exciting ways to do just that.
So! It’s the trifecta of awesome rewrite-your-app time:
“Everyone’s settled on non-blocking IO as the only way to scale.” “Client-side tempting is where it’s at these days.” “We’ll less trouble since it’s all the same language and platform everywhere!”
Time to rewrite those apps!
Fast-forward 2 years when “I’m becoming more and more certain that this means that Node.js-style single-threaded engines with client-side logic are going to end up being phased out in favor of leaner and meaner megathreading frameworks that better address the new needs of the quantum-core architecture”.