I'm actually starting to think there's something to be said for letting each generation of programmers grow up simultaneously with a hot new framework. It encou

I'm actually starting to think there's something to be said for letting each generation of programmers grow up simultaneously with a hot new framework. It encourages learning through experimentation, lets them make the mistakes we all have to make, helps spread new ideas unbounded by the received wisdom (many of which will be stupid, some will have important influence for decades to come). In the end, you get a bunch of developers that are both comfortable with a modern framework, have some understanding of the growing pains of new, complicated systems, and are ready to bring fresh ideas to more mature parts of the industry. The contrasting mentality of sticking to what we already know is "good enough" leaves developers dull and uninspired, less equipped to think outside the "rules" inherited from previous generations that came from solving problems that look a lot different when you examine them 10 years later. All of which is to say, Rails probably isn't for beginners anymore, and it shouldn't be, but I don't think trying to substitute a simple framework that explicitly avoids becoming complicated is necessarily what the doctor ordered...