Updated RailsCasts Status

I think this speaks of a larger trend with the Rails platform. What I mean is that it&#x27;s now a mature platform and Railscasts have covered a lot of ground. My guess is part of the burnout Ryan is experiencing is due to a dwindling amount of material to cover without venturing outside of the platform, which he has been doing (and is welcome).<p>While I love Rails and Ruby (and learned a ton from Railscasts), the future of the web is building a separate RESTful API + separate static JavaScript browser app + any other devices like mobile, Glass, etc (opposed to nesting client-side JS apps under assets).<p>Edit: In response to the downvotes, let me clarify: I think Ryan is running out of topics in the context of Rails. He&#x27;s a great teacher and I&#x27;m a paid pro subscriber.

I feel like I owe such a huge debt to Ryan and don&#x27;t even want him to feel the pressure of &#x27;coming back&#x27;... as he already gave so much. Burnout is a serious issue for those that make a living behind a keyboard.<p>That being said - how would you reenergize in his shoes?<p>He&#x27;s been chasing the edge of Rails development for so long - is that where the subscribers come from?<p>It seems like he gets OVER THE TOP response every time he does a more &#x27;newbie&#x27; Railscast - so maybe here are some options to maybe reenergize and keep the subscriber base - what would you like to see?<p>- More Rails newbie stuff - Exactly like before, after a break - More Multi-session &#x27;building a complete app&#x27; - Guest speaker sessions - Evolve to more of a &#x27;how to tackle programmer challenges&#x27; - Evolve to more of a &#x27;building web apps&#x27; vs. &#x27;only Rails&#x27; (ember, meteor, Go)<p>What else?

Railscasts was really useful when I was learning Rails, so there&#x27;s no begrudging Ryan.<p>But still, part of me has to wonder, how much of this is TextMate Syndrome[1]? By which I mean, how much did Railscasts end up earning?<p>I was signed up for about a year -- $108. Ignoring those who would pay their personal money, and just considering those who could expense it (a whopping $9 per month!), I have always just <i>assumed</i> (but don&#x27;t know) than many thousands of others must have subscribed.<p>Making hundreds of thousands of dollars more than you expected does really make it harder to keep working on some nerd shit, instead of... not doing that.<p>[1]: <a href="http://blog.macromates.com/2006/year-in-review/" rel="nofollow">http:&#x2F;&#x2F;blog.macromates.com&#x2F;2006&#x2F;year-in-review&#x2F;</a>

This is the best way to handle it, just a quick note saying &quot;Sorry, maybe soon!&quot; rather than out and out abandoning ship. Kudos to him, I hope he finds his desire for it again, he makes some excellent resources.

Nicely handled. Good for you, take your time Ryan. You&#x27;ve given so much quality free content over the years, the least the Rails community can do is hang back and let you figure this out on your own good time.

I would pay 90$&#x2F;mo, if he makes golang screencasts. He has covered almost everything you would need to know about ruby on rails. It is time to explore new worlds.

I wish there were a way to opt-out of the extension. I am a subscriber and plan to continue to be a subscriber as long as I can afford the $9&#x2F;mo.<p>Ryan&#x27;s resources were invaluable to me when I made the transition to rails. While I would be sad if Ryan decided to not come back, I would happily continue to pay. It truly is the least I can do.<p>Thank you for everything, Ryan. Come back soon!

I&#x27;m sad to see this happen as Ryan not only produces great screencasts but shows the trends and popular gems along the way. I respect his decision, though - I know what burnout feels like and it&#x27;s the biggest mental burden one can have. Good luck, Ryan!

Take your time Ryan! Not sure what exactly that you are going&#x2F;went through. But your style and topics you covered were&#x2F;are still unparalleled and sorely missed in the Rails world.<p>Ryan, if you are reading these: You have been doing Rails stuff for quite a while now. If you think, its getting repetitive and not challenging enough, it might not be a bad idea to diversify the screen casts away from Rails. Node, golang or anything that ignites the keen learner in you. I am sure you will do a great job making those technologies accessible to the uninitiated. Of course Ryan knows best :)

I&#x27;m happy about how open Ryan has been about this whole thing. We all suffer from burnout from time to time.

I hope he recovers completely and soon regardless of whether he continues Railscasts. And, I appreciate that he extends subscriptions and I know many people need that, but I almost wish he wouldn&#x27;t as I subscribe more to thank him and look up revised episodes than to get the new content.

As a developer who has only been using RoR for about a year and a half, Railscasts are an incredible resource. Ryan saves you hours of research that you&#x27;d have to do yourself. In fact, I&#x27;d still happily pay the subscription right now even without new content.

I think he&#x27;s a great at explaining stuff and a terrific teacher. Maybe his next venture should be an online school teaching general computer science or more languages&#x2F;frameworks. Hopefully his burnout is with Rails alone and not teaching in general.

Recovering from a burn out myself too. Took it easy for a couple of months, went on some holidays, and now helping a startup out at the lisbon challenge.<p>Good luck ryan!

Take your time Ryan. We will wait patiently.

I&#x27;m surprised no one else has really stepped into his space and made much impact.