3 ms·
Agreed. There is a good amount of boilerplate needed to get a basic app setup. I hope it becomes a bit more "Railsy" with some Omakase-style conventions chosen.
by the_gastropod 4y ago
Agreed. There is a good amount of boilerplate needed to get a basic app setup. I hope it becomes a bit more "Railsy" with some Omakase-style conventions chosen. Right now, it's left up to you to implement multiple sessions, even though 95% of apps will want this. Auth feels like another area where there's a happy path that'd cover the 95% case, but it's currently left up to you to choose / implement using cookies vs tokens vs ???.
That said, there is a decent amount of documentation around these things, and even as a relatively ignorant Swift programmer, I was able to copy/paste from the docs, and get an application working reasonably well.
- joemasilotti 4y agoThat's awesome to hear you were able to get something working. And yes, 100% with you on this one. It's a very non-Rails like experience going to Turbo Native. You have to configure everything pretty much on your own and are left to figure it out by yourself for new things. One of my goals is to fix this in the near future!
- heartbreak 4y agoAlthough in the case of authentication, Rails has dropped the ball for over a decade on providing an out-of-the-box solution. Practically everyone uses Devise.
- joemasilotti 4y agoEven though the maintainers have pretty much said to use anything else! I'm guilty myself. I know how Devise works, including all of its quirks, so I refuse to learn something new. I don't think Rails will ever have a built-in authentication solution. But I would love to see more official support for something a bit "lighter" than Devise. And that works out of the box with Turbo.
- airblade 4y agoI believe the maintainers regard authentication, rightly or wrongly, as a business-level feature. Not so much the mechanics of checking a user's credentials but how you want to steer the different authentication flows.