Choosing a Web Framework/Language Combo for the Next Decade

I was a little surprised to see Gorilla get kicked out. My understanding is that among Go developers, stdlib net/http + the Gorilla toolkit was the de facto standard approach.

People are experimenting with new frameworks, e.g., beego, revel, martini, etc, but I don't think any of them are stable enough to meet your stringent criteria in that regard.

It seems to me (as an outsider looking in) that the Go community is relatively "anti-framework", instead preferring libraries, like Gorilla, for special oomph in routing or sessions or what have you.

I also think it's worth determining what you think the next decade's high level architecture will be: JSON api backends with fancy JS frontends, or more along the lines of standard Rails, Yii, etc? That will drastically change the type of web framework to choose.

I'm interested lapis as well, I think this might finally be what I have been looking for...

I can't follow Jacques' reasoning when it comes to any of this. His first choice would have been a PHP framework (in 2014!), yet he goes on to criticize a bunch of languages which have sane == operators seemingly on the basis of his gut reaction to their very existence, while asserting things like "Python is like driving on the autobahn without guard rails" and "Lua is the sweet spot between Ruby and Python." That might be true if Python had shipped with exactly two data structures, and Ruby with zero, and neither of them had integers.

This is all before the frameworks are even discussed, which are included and dismissed for reasons just as arbitrary. Smaller frameworks like Sinatra are discarded because they can't handle the complex logic that flash cards demand, Django's out because of the whole auto safety thing, and we all know that ExpressJS didn't show up at Jaques' birthday party that one time. Play's out because Scala is unfamiliar, despite that not being a specific quality of Scala and just something that's true in general of programming languages one hasn't bothered to learn.

So the final list contains some more PHP horror shows and a few Java and Go frameworks to make things look democratic. Thankfully, Rails makes an appearance, but it feels like this is just because it was lucky enough not to get hit by a dart.

Let it be a lesson -- we all procrastinate, but when you get to the point where you're writing blog posts about dozens of languages and tools, none of which you have direct experience with, the best thing is just to pick something, do what you'd meant to do in the first place (although you will note that writing the flash card app was itself a way to procrastinate on learning Romainian), and discuss the pros and cons of the tools you chose once you actually know what they are.

MS Partner licensing gives you broader usage, through to production servers, Office etc. Pretty sure MSDN is dev or training only. Plus why pay twice, shit should just work without all the BS.