I tend to agree. I was setting up a new Rails 5 app recently in a very specific way and felt like it took a while just to turn off all the stuff I didn't want in there. While I dug CoffeeScript a few years ago, I'm more inclined to do ES7 nowdays, and I don't want to use minitest, and I don't want to dev on Sqllite, and don't even get me started on Webpack... Maybe because I don't necc. build projects in "The Rails Way", which could be my own flaw.
Wasn't that the whole point of Rails "templates"? Wouldn't it make more sense to just point people toward a "kitchen-sink" template and have it do all the things - versus having a bunch of things you don't need in there by default? Or, add a slim version to rails new. I was happy to see --api, maybe there should now be a --slim without all the extras?
I'd also question whether this is a "good thing" for a new rails user. In the beginning, it was very simple, things made sense, and it was fairly compact (compared to, say, a default .NET web project). Now even as a long time rails user, it seems WAY more complex than it needs to be.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.