There is a lot to like here. It can be a nice stack when combined with async/falcon and viewcomponents, at least where you don't need a lot of client-side state and browser API usage (canvas/usermedia etc) where javascript-first is a better approach, or a lot of number crunching, for which Python is better.
A bit late to the comment party but just wanted to say that I just upgraded from 7.2 to 8 and it was a complete walk in the park. Easiest major dependency upgrade in a long time.
Also finally upgraded from Sprockets to Propshaft and Importmaps this afternoon and it was very straightforward as well. Truly amazing.
I think the only benefit is that it does less, so less code, less maintainance or things going wrong? But Sprockets is certainly battle tested and maybe better choice for many right now.
This is another brilliant writing example from dhh. What a master he is. Talk about the tech and the big sea changes, and talk about the people. This was clearly written with the help of many smart people. So good.
I'm very interested in kamal 2. I use dokku for almost everything and I like that I can do from the command line anything like deployment, use Dockerfiles, scale instances, switch proxies.
kamal 2 seems like it takes over an entire server. Is there any reason to consider kamal 2 if you want to buy a single server and run a bunch of tiny applications on it (the way I run dokku)? Maybe rails is heavy enough that you really need to run it on server by itself?
