Listening to DHH here clarifies to me why I didn't enjoy working in a Rails shop. Rails is opinionated, but opinionated around ways that DHH likes to work and thinks about apps, and seems I just disagree with and/or don't think that way. E.g. his dislike of components and componentizing such as ViewComponents, the suggestion to build your own auth, etc.
Not a knock against Rails, just an observation as to why I couldn't get into Rails even when surrounded by folks who really liked it.
As a longtime product designer in the process of refreshing my development skills, one of the things I appreciate about Rails is how transparent and evident it’s point of view is. Without too much trouble I’m able to understand both the jobs the tool is suited for and whether I’ll enjoy the experience of learning / working with it. Many other frameworks / languages I’ve experienced require a more significant investment of time before I’ve been able make a similar assessment. The feeling of investing a few months into a dead-end is unpleasant.
I’m sure an experienced engineer is much more able to make these assessments; however as a perpetual dilettante in this space clear signaling is such a time-saver.
Not a knock against Rails, just an observation as to why I couldn't get into Rails even when surrounded by folks who really liked it.