Really? Do you think that users will stop wanting interactive web apps because of some minor technical complaints you have about the stack?
Once you start building an app with a lot of interactivity, sending certain states as prerendered pages becomes a huge distraction.
Re:Ask HN: Where are all the Rails jobs?
by crdoconnor on Saturday November 22, 2014 @10:28PM
(#8647709)
>Really? Do you think that users will stop wanting interactive web apps because of some minor technical complaints you have about the stack?
No. I think customers will stop wanting extremely javascript heavy interactive apps when they start to realize that 95% of the time they can have something that is cheaper and more reliable that isn't so javascript heavy.
Are you dying for hacker news to become a one page ember app?
Didn't think so.
Users don't really care about this stuff unless all that javascript brings huge gains (e.g. for a mapping app).
I don't think node/ember will ever go away, but I'm sure that they'll lose their fashionability after a year or two much like rails has, and for that reason I'm pretty loath to chase them. I'd prefer to invest in the other type of technology instead of chasing faddish stuff.
These days the benefits of this model of development (one page js app) is also hyped enough to drown out the fairly significant drawbacks - javascript behaves unpredictably under different browsers, is weakly typed, and the whole model breaks certain abstractions. I'm betting that the hype will die down but the drawbacks aren't going away.
I also don't think that switching ecosystems is quite as easy as you make out. Each ecosystem has enormous tool chains and you quite often need years of experience to know what the best of 500 libraries/tools to use in any situation is.