The problem with Rails built in authentication generator

The rails authentication generator was added in Rails version 8 and it seemed like a cool new feature and lots of people were hyped to use this for new apps. I did use it quite a bit for my apps but there are some things that just make it more difficult than other proven solutions. For one it is very bare bones. It does not come with many fancy features like other well maintained projects it doesn't even come with a registration flow you have to do that manually. This forces you to be more hands on with your sign in/sign up flow from the beginning which is another reason why people use a gem to make that easier for new apps. Because when you have a great idea for an app and want to build your MVP you don't want to spend the first day just working on adding a simple user account login an registration flow. Back on the fact that it does not include a registration flow.

It only includes the views for logging in as a user and sending a password reset email it doesn't even include a remember me feature. This requires you to create your own registration flow just for allowing users to sign up before they can even log in to the account. I did create a gem called tailwind_registration which you can use to scaffold a basic registration flow with the same styling as the authentication generator which can solve that problem but another question is. Was adding this authentication generator really such a good idea? Its basically saying that we don't need to use gems and to use a built in solution which overall just puts the maintenance effort back on to you as a developer and moves us away from the fundamental concepts of the Ruby on Rails and Ruby programming language which is to work together as a community to share our code and package it up nicely for each other. We want to help others do things easier where we struggled before. One weird thing that you will notice is using the built in authentication adds a couple different model we have the standard user model is I am familiar with but also it adds a Session model and a Current model which is used somehow to manage the current user and all of the methods for logging in users are included in the authentication concern in the controller. Is this really easier than using a gem which is already built nicely, trusted my many successful companies and contributed to by thousands of developers whereas this authentication generator as at the most worked on by a small group of devs. I think I would not use the rails authentication generator again just because it is way to minimal and leaves you with all of the work without a friendly experience as a developer and many quirks in the code.

I am also writing this rant now because I decided to use this on a project I have been building over the past few months and now I got to the point where I needed another model instead of users that needs all of the same login/registration code and it left me with this huge pile of work to copy all of the things used for the main user model models ( Current, Session ) and concerns ( Authentication ) over to my other model and for what?. With devise it would all be taken care of with one command so I am strongly saying I do not like authentication generator ust use devise and lets not forget about the beauty of gems.