Can one skip a generation and say learn backbone instead of jquery, or meteor instead of django?
I wonder if knowing the older technology is still needed to appreciate the new one; The elders of 'server side rendering' frameworks are saying in talks that what they do is virtually obsolete, as more and more gets rendered on the client. But of course there's a large chunck of applications that still are better implemented with RoR/Django. Since we all have a limited time to learn... in 2013, is it still worth learning RoR/Django?
Instead of using RoR or Django (or something really "opinionated"), try looking into Sinatra or Flask (or other small "micro-frameworks" and libraries) where you can mix-and-match your own libraries from different places. This will get you in the habit of weighing the pros and cons of using different packages and tools for different tasks, and it will also force you to learn how to chose the <i>best tool for the job</i> yourself.<p>I think Rails and Django are great, but they offload a lot of design decisions to the community -- this is great when you want to write maintainable code with a diverse team, but not necessarily the optimal setup for gaining the most useful skills for the future. If you want to be ahead of the curve, try using smaller and more focused tools. Even though an individual piece of the puzzle may occasionally need to be replaced, you will at least know that you hand selected the best tool for your use case, and won't have to shoe-horn another approach on top of it.
This conversation seems to come up often. Server side templating is still really important and isn't going away too soon.<p>There's still so many problems to solve before server side templating can seriously be considered obsolete.<p>1. Search engines still can't scrape javascript created content. Hacks like #! don't count.<p>2. Grade A browsers still don't properly support pushState() and if they are supported in some cases it's a buggy experience.<p>3. There's still a decent amount of people with JS turned off.<p>4. Having the client do the heavy lifting of your web site is a bad idea because the experience cannot be controlled. Anyone without a decent computer is going to get a sluggish experience and mobile performance is still very questionable.<p>#3 is probably the least important thing but it will also depend on what your site is doing. If I'm selling a product that with global reach and I ignore #3 then I'm throwing away money basically because India and China are massive and they have pretty high %s of people without JS or very old browsers.
Backbone and jQuery do different jobs, they complement each other quite well.<p>For the next year you'd have a much better chance of getting a Django or RoR job than a Meteor job. Meteors still the new kid on the block so it's still in a process of picking up traction. Beyond the next year, who knows...anything could happen. As long as you understand the underlying principles of web development, picking up new technology should be trivial.
The idea of skipping Rails and learning Backbone instead makes no sense unless you just wanted to be a front-end guy all along. You still need a backend. Whether you like Rails' style of backend or prefer something like Sinatra is up to you, but you need something on the backend, and Rails is still a very strong contender.
It's not a zero sum game.<p>Also, there's a lot of hype about JS frameworks and client side rendering, but you still need an API and server side rendering (Twitter just figured this out after going back and forth). Both RoR/Django are good tools for writing REST APIs on, and for learning about web development in general.
IMO this is the composition vs inheritence debate.<p>In the Python world, WSGI was really a break-through idea (a decade ago!) - parse the request up front and pass the text down a chain of functions each of which can modify the request / response.<p>That way the chain you build is the chain used.<p>Every python web server uses it behind the scenes, and then
tries to make bits of it "easier" for you by hiding the underlying goodness.<p>Its usually a good trade off, but it kind of takes away the point.<p>So, I would say, (python) learn how to deploy your own WSGI app on gunicorn behind Nginx. And put security in using repoze.who.<p>Then you can choose to replace your app with Flask. Or django. Or ...<p>build up from the ground
<p><pre><code> > learn backbone instead of jquery
</code></pre>
Backbone relies on some sort of DOM library like jQuery to function. Regardless, for any library, it's important to learn the fundamentals before using them, such as DOM basics in JavaScript before even using jQuery.<p>To answer the original question, yes, it's important to learn server-side frameworks since there's still many things about them that client-side rendering can't do (better search engine optimization, progressive enhancement, accessibility).
If you want to remain an applications developer, then yes ROR/Djano is worth learning.<p>If you want to learn to build critical system components in the back-end, you can skip RoR or Backbone, and learn stuff like machine learning, NLP, or building distributed systems.
Can anyone enummerate the apps that are 'as of today' better suited to RoR/Django?<p>The funny thing is that the django tutorial uses a poll app. This is an app that is ten million times easier to do, and more effective, in say meteor. But I'm sure other apps are not.