I've been programming Rails since 2010, and still feel like it's far-and-away the most productive I've ever been for turning SQL into HTML and then user actions

I've been programming Rails since 2010, and still feel like it's far-and-away the most productive I've ever been for turning SQL into HTML and then user actions back into SQL. If your task is SQL into HTML and then user actions back into SQL, with a few "sprinkles" of Javascript on top of it, Rails will not steer you wrong. I have also recently been doing, for the first time in a long while, work which is not SQL into HTML and then user actions back into SQL. Rails was never seriously considered for that part of the project. This was the correct call, and the new stack (GoLang and React) are fun things to have in my toolbelt, but there have been a few points this year where I've said "I just spent two hours on something which would have been 4 lines in Rails and I'm not sure I'm done yet."