I really like ruby and rails, but my big concern isn't really about performance, its about how to deal with the rise of heavy JavaScript spa apps. I'm still wo

I really like ruby and rails, but my big concern isn't really about performance, its about how to deal with the rise of heavy JavaScript spa apps. I'm still working out how to deal with this. One approach is to wait it out. Stay with the trade rails view, add JavaScript as needed, see what I can get out of turbolinks and sockets in rails 5. Another possibility is to go rails-api and write the front end in react or ember. This of course requires going in heavily on JavaScript and (at least for now) duplicating a lot of effort in client and server code (models data routes ...) Another is to say bye to ruby and go all in with node. I don't hate JavaScript but it felt great to go from java to ruby. Doesn't feel great going from ruby to JavaScript but that may change over time. Another is to go rails api and try to carve out a role as a pure back end dev. I enjoy back end work more anyway, and maybe specialization is inevitable. It has certainly happened in other fields. Lastly maybe the trend toward isomorphic development will continue and devs will have as wide a range of choices on the client as they have on the server. I do see signs of this - volt is one good example. The last time I remember this kind of uncertainty was around 2004 when MVC and DI and ORM frameworks were proliferating wildly in javaland. I studied a lot and finally picked... Ruby ;). so let's also not rule out the possibility that something very new sweeps everything off the table with a loud crash to usher in a very new way of thinking.