Ask HN: What web framework do you use? Why did you choose it?

nowdays you don't use xml to define your beans so most of the things are compile checked. granted some things are happening only at runtime which is a whole point of DI :-)

currently, i roll my own: golang net/http, gorilla/mux, eknkc/amber, and database/sql. i'm not entirely happy with amber as an html template language, prefer jade or haml, but it seems to work so far, i've had a few problems with it and the author fixed one of them in terms of nested data structures, but there's another issue pending for a long time so i don't think he has the interest to maintain this.

got into expressjs/jade, but didn't like the nested async callbacks, really annoying to read the code, but the tooling side was cool with npm, gulp, etc.

i used to use sinatra/haml/activerecord for a long time, really liked the simplicity of it, but ruby in general was just too slow in terms of performance, had to use a lot of physical resources to supplement for its slowness.

before sinatra i used ror, this was before i decided that rolling my own was more streamlined and efficient.

before ror i used python, tornado, and sqlalchemy. god, sqlalchemy was so clumsy back then, i even bought their ebook for my kindle, what a waste of money. ran ok, really liked the decorators used by tornado, but then fb went and bought friendfeed which doomed tornado to the depths of /dev/null.

before python, i used java servlets (as part of the j2ee standard) and java server pages. it was sort of nice to use html files and embed these java snippets, but still pretty primitive.

before j2ee, i used php, pear, god save me from those days. my personal blog was built on this, i saved all entries into xml documents and stored them in directories based on the date. that site was hacked and pwned so badly, thanks php security holes! this was a time before templates and orms.

and from the very beginning, there was pure html, wow, we have evolved so much since then.

golang is perfect for me, but i use it for a lot more than just a dynamic web server, it's also an api server and websocket service. i really like the ease of deployments with golang i.e. just copy a binary to my production servers. and the code is fast and scales. coming from sqlalchemy, activerecord, and sequel, i was a bit underwhelmed by gorp, but soon found out that going with sql was good enough.

I've mainly used Ruby/Rails from ~2008 to ~2015 both for work and side projects/prototypes, then I totally switched to Elixir/Phoenix for almost all my stuff. I still use Ruby/Rails for some works (where/when I can't use Elixir due to some constraint).

I've found that Elixir and Phoenix have an awesome community and a fast-growing ecosystem. The language is very clean and I can solve problems in a cleaner and faster way. It has all the tools I need and runs on a simple but powerful virtual machine with stunning performance and easy deployement. I can use websockets and async jobs without running external processes/daemons and thanks to brunch (or webpack, it depends) I have a powerful toolchain for frontend. Speaking about frontend, I've recently moved from React to VueJS, it's a very decent compromise between React and Angular: simple like React, with features and concepts similar to Angular.

All the dependency injection and spring setup is done at startup, so you won't have any of those errors during the life cycle of the app. Spring boot with spring data rest makes it so easy to create very strong REST APIs easily. Source: I've done a lot of demos, presentations and trainings on Spring Boot, including at SpringOne in Vegas last summer.

I don't agree: from my experience (~9years of full time Ruby/Rails, including teaching and coaching) Ruby is not easy to learn, at least if you want to know what you're really doing. And Rails, as is, promotes several anti-patterns that will mess your app after 6+ months. Fat models are a bad practice, models as form objects are a bad practice, developing uour business logic almost totally on top of models is wrong. That's why some experienced Ruby devs are moving away from those anti-patterns by promoting real object oriented approaches: for some good examples check hanami web framework, rom-rb and Trailblazer.

My 2cents reply.