Flask to Rails is an apples to oranges comparison in a few ways. Flask is a Python micro-framework, so there’s not much that comes out-of-the-box, while Rails is a large Ruby framework, with a large amount of abstraction and opinionated features. Each has a learning curve. Flask’s is around implementing more of your own libraries and solutions, and Rails’ is around learning the “Rails way” to do everything. First thing I would do is pick one language — Ruby or Python, and start learning fundamentals of that language before studying the domain-specific knowledge of any framework.
Principal software engineer at a fintech company, leading designs and architectures. Sharing personal insights on technology trends and their impact. My posts are based on my personal opinions.
Location
Chicago, IL, USA
Education
Bachelor's in Information Technology (Mackenzie) and Master in Financial Engineering (WorldQuant)
Work
Principal Platform Software Engineer at Enova International
Flask to Rails is an apples to oranges comparison in a few ways. Flask is a Python micro-framework, so there’s not much that comes out-of-the-box, while Rails is a large Ruby framework, with a large amount of abstraction and opinionated features. Each has a learning curve. Flask’s is around implementing more of your own libraries and solutions, and Rails’ is around learning the “Rails way” to do everything. First thing I would do is pick one language — Ruby or Python, and start learning fundamentals of that language before studying the domain-specific knowledge of any framework.
A more fair comparison would be Flask to Rack and Django to Rails, what you think?
Yeah more or less. In the Ruby world, Sinatra and Roda are most akin to Flask, providing slightly more out of the gate than request-wrapping.