You can stick with something for the wrong reasons just as well as you can shun something for the wrong reasons. Is Java hard to use? I don't think so. Is PHP

You can stick with something for the wrong reasons just as well as you can shun something for the wrong reasons. Is Java hard to use? I don't think so. Is PHP messy? Before the restructuring that happened from PHP 7, not so much. In fact, it's pretty good now. Are Ruby and RoR easy to use and well structured? They can be, if you are careful and stay on the well beaten path. As always, for small applications, RoR is a breeze to use. But once you leave toy land, the heavy amount of helpful magic comes around to kill you. Oh you thought you were calling this function with that name in that file over there? Nope, magic code loading decided to pass your call to that implementation instead. (a.k.a. monkey patching is evil) Let's not talk about dependency management and the constant shuffles due to abandoned gems. Let's not talk about nasty upgrades from one major release of Rails to another. But of course, I am being mean. The truth is that we, developers, make a mess of anything and when it becomes unbearable, we blame the tool and move on to another tool that grew from the ashes of other tools we abandoned previously. And hence, things like Laravel are born and grow out of the lessons learned with RoR (among others). As for Java, my Lord, the archeology of web frameworks based on it makes the archeology of life on earth seems simplistic. I survived servlets, JSPs, Spring, JSF, Struts, GWT, yada, yada, yada, generations of attempts at getting it right, growing on the putrefied corpses of failed attempts at not getting wrong. I think it's progress at work, but sometimes it looks like a pendulum.