My time with Rails is up
Great article, and only 391 posts.  Clearly I need to show up 24 hours after the fact and put in my two cents ;)<p>From what I&#x27;ve read here, it really doesn&#x27;t sound like his time with rails is quite &quot;up&quot;.  It sounds like he has read the writing on the wall about rails, after a very long time with the framework (certainly longer and more involved than I&#x27;ve been, though I have used Rails quite a bit).  This is different from realizing that a technology won&#x27;t last &quot;forever&quot;, it&#x27;s a more distinct understanding that you see where things are going and how your current tools don&#x27;t quite match up anymore.<p>But when my time with Rails is &quot;up&quot;, that will mean that I have largely stopped using it.  I&#x27;m mot counting maintenance, or perhaps the occasional one-off, I mean that if my time with a technology is &quot;up&quot;, that means I don&#x27;t use it anymore for day to day work.<p>I&#x27;d be interested in reading more from Piotr Solnica on this topic, because I&#x27;m in a similar spot.  I don&#x27;t see Rails as the ideal match for much of what I&#x27;m doing on the web, but I&#x27;m not anywhere near ready to give it up.  I increasingly need much more interaction between the client and server than I get from the MVC approach, but I&#x27;m not sold on javascript front ends with a web service backend, at least not the way it&#x27;s been presented now.  For starters, I personally (yes, this is very much a personal trait) don&#x27;t relish the idea of giving up Ruby to write most of my app in Javascript.<p>It&#x27;s not just that I like ruby, I don&#x27;t really like the idea of giving up the very rich set of languages I can choose from on the server side, or minimizing their role, in order to allow javascript to take over most of my programming work.  I also feel that javascript front end frameworks are still a moving target, and I have a suspicion (like I said, I&#x27;m trying to sort this out) that when the dust settles, elaborate javascript front ends communicating with a web service written in something else won&#x27;t be where I go next.  I&#x27;ve read about some exciting new possible directions in this blog post, and I&#x27;ve read interesting things elsewhere (Volt, specifically, non-js languages transpiled to isomorphic javascript, more generally).  It is all very exciting and promising, but is this the moment to give up on Rails, which works though I find myself increasingly shoehorning things into it?  For me (again, just for me, everyone has a different set of interests and tasks), no, not yet.<p>Drawing on my past experience - the last time I felt this way was when web programming in java moved from the jdbc&#x2F;servlets&#x2F;html with libraries to struts, struts2, spring mvc, pico, spring di, jpa, hibernate, ibatis, wicket, tapestry and so forth.  Looking back, I wish I&#x27;d had the conviction to stick with the old way of doing things even though I knew its days were numbered.  Keep an eye on things, keep learning.<p>It sounds to me, from the end of this article, that this is what Piotr is doing.  There are some good suggestions of where to go next, but I guess my question for the author is this: where are you going <i>now</i>?  Is your time with rails &quot;up&quot; in the sense that you no longer have a substantial day to day use for it, that there is a new technology that you&#x27;ll be working with now the way you worked with rails for 9+ years?  Or is this more a situation where you see that your time with rails is ending - if not today, then certainly before long?