Something I keep observing that seems to be passed over, coming from a Rails background, is that by using a known framework, the company is also accepting the "population" that comes with it, as well as the known problems.

I observed many Rails developers and many apps (purely anecdotal, I wish I could run a real study), but the problems are the usual, the ones on top of my mind right now:

    - database changes affect directly UI code, so a change in the DB requires changing code in a million places
    - Rails devs don't know SQL as much as they should (often just don't know it), for a framework that so SQL-centered, it's weird
    - hidden logic (callbacks)

These are very common problems with this framework and are well known to hinder company growth and ability to iterate.

Would a home-grown framework be better? I cannot tell, but surely if the list of downsides when choosing a framework was written in the splash page, I would be way more scared. "If you use this framework, your db will 100% be coupled with your frontend" is a terrifying statement.

Given that, framework should be evaluated for their downsides too, but there isn't even a list of known issues.