> I think what is actually dreaded is Rails, and the terrible, awful, no-good things PM's forced it to do in the 2010's. That's basically it, for me, yeah. Lon

> I think what is actually dreaded is Rails, and the terrible, awful, no-good things PM's forced it to do in the 2010's. That's basically it, for me, yeah. Long-lived (or hell, pretty much any of them that aren't just getting started) Rails codebases, even when they're not particularly complex, without heroic levels of good processes & individual discipline to keep things reasonable and clear, become fucking nightmares to onboard to. I'm more wary of Rails than a bespoke PHP codebase, at this point, and "we're a Rails shop" is damn near an instant "well thanks for the interest, but no" from me. I don't need that stress for the dozenth time. Just done with it. It sure is impressive how fast one developer can knock together a prototype with Rails. Meanwhile I've had so many extremely-bad experiences with ongoing Rails projects that I hope never to touch one again. But I actually like using Ruby itself a lot better than, say, Python. Ruby's fine. Rails... no. Never again. Maybe if they embrace static typing and it becomes nigh-universal in the Rails library ecosystem, they can make it tolerable. Too much magic, too little help from my tools to help me understand WTF the magic is doing, where it comes from, et c.