Spring Boot (Java) is really simple and boring yet a lot of capabilities underneath
Also, ASP.NET (c#) - similar deal
Django or Flask (Python)
Backbone.js, jQuery, Bootstrap (JS front end)
Express (JS backend)
Sinatra (Ruby)
PHP 6
Maybe Angular or Ember or even basic React+Flux in the front end if you can contain your enthusiasm
For hosting, find a boring PaaS and avoid the container mud wrestling
For pity's sake use PostgreSQL or MySQL, MongoDB burns
I was pleasantly surprised at how much functionality I got for free once setup. I probably spent as much time on setting up Oracle and xml/config stuff as dev but it was still super fast to get a solid API built.
What would you suggest out of these for quick prototyping and just side projects?
https://realpython.com/blog/python/kickstarting-flask-on-ubu...
The latter is also when you might appreciate the fact that its markup language is really just embedded Python (PHP style) - you're trusted to not abuse the power, but you define what "abuse" is.
I'd be curious even to see it for the technologies you mention. But as others point out, there are plenty of things newer than PHP that have become pretty boring.
This is the case with any mature framework. Rails and Angular just happen to be my favorites, but Django, or Spring and Ember can probably work just as well.
I try to avoid having to put up Angular or anything big on the frontend and just scrape by with jQuery. However, when the interactions are supposed to be "rich" and have a lot of animations, drag/dropping, complex forms that validate on the fly, etc etc...things can get really complex. Then you're back to the old dilemma: you are either going to introduce a full-fledged framework, or write one yourself. In those situations, I pick Angular.
- Angular 2 also looks fine, but that defeats the question which asked about "boring", stable frameworks
Why? Well, some of it's solid code. That might be worth keeping. But some of it's technologies that fell out of fashion. And there's a bunch of stuff that people wrote in a frenzy, so there's a bunch of tech debt. And even if they stripped it down to the bones, there's a lot of upgrading to do just to get back to where they could do new work with modern libraries. From the business perspective it was easier just to glue together a bunch of outsourced services.
I'm sure those developers all meant well by picking cutting-edge tech. But as Dan McKinley says, we should generally choose boring technology [1]. As you describe, the costs of keeping up with interesting things is substantial. On rare occasions, it's really worth paying that cost. But, mostly, as with my acquaintance's company, the costs can accumulate while your attention is elsewhere, pushing code bases into a sort of technical bankruptcy.
[1] http://mcfunley.com/choose-boring-technology