This is quite different form the Python frameworks ecosystem: here most "beginners" already know Python, or at least they already know how to program having exp

This is quite different form the Python frameworks ecosystem: here most "beginners" already know Python, or at least they already know how to program having experience in something like Java, C# or C++. And because they already have this knowledge, they usually ending up doing things "their own way", or they already know what each piece is supposed to do before starting to play with a framework that has all the pieces in it. And "being explicit" rather than "convention over configuration" really helps people make their own choices. When people bump into the limits of Django's ORM, for example they quickly replace it with SQL Alchemy, when they do something in Flask, they already know what the pieces they are putting together do. Rails culture seems very "top down", i.e. people start learning and doing things by learning the stack as a whole and then about the options for individual components. This leads to "elegant solutions", but tons of pains for beginners that need to "swallow it whole". I don't know which way is better, but I've always been attracted to the Python ecosystem because I like learning things "bottom up", e.g. playing with all the different pieces and then assemble them into a whole once I'm confident I understand them.