1. all data flow through the rails app (no pre-signed s3 upload or download links for direct uploading).

2. no support for CDNs (I think newer rails versions added support)

3. blobs and attachments were unnecessary abstractions.

3a. Querying was annoying (extra joins) and easy to add n+1 queries.

3b. In my app, images are moderated and it was unclear where to put the moderation metadata (on blobs? attachments? create a new table? why so many tables?) or `deleted_at` type columns.

4. GraphQL gem didn't support it: https://github.com/rmosolgo/graphql-ruby/issues/1777

2. What do you mean? Point whatever CDN you want at your origin

3. Maybe

3a. Yes

3b. Metadata or a new table

4. GraphQL is the single worst technology that has ever been adopted. We adopted at my company...twice. Twice we made the same mistake now we're stuck with it for mobile clients. In fact we're stuck on the old Graqphl RB gem that used a DSL instead of classes, which also blocks our Rails upgrade. We've been able to revert everything back to good ole Rest for another part of the app. Be cautious adopting technologies of large companies.

2. CDN support is via monkey patch: https://github.com/rails/rails/issues/44136

3. yep

4. yep

It's not really governance, that's kinda the problem. To be fair, he never claimed that he was providing governance. Rails was extracted from basecamp. The impression I get is that he sees Rails as a gift to the community created from the profit-making Basecamp. Which is great; and I appreciate the fact that I've been able to build a career using Rails.

But there is no governance really. Rails goes in the direction that 37signals wants it to, which is largely pretty good. You and I don't get much of a say in it though; especially if DHH disagrees.