Like the parent commenter, I'm also a huge fan of Python. I've recently started my journey learning web dev using Scala. It's a pretty hot language right now, what with the rise of big data and ML (see Spark for example). It allows you to use existing Java libraries, yet there still is a considerable number of high-quality libraries written in Scala. The stack I've chosen is Scala + Play + Slick, but there are several popular options.

You should look at Elixir/Phoenix - I think it's the next rails and will be the new hotness in a year or so :)

I'm personally a fan of Clojure which is an excellent language with excellent tooling and a smart and friendly community

+1 You should look at Elixir/Phoenix

Sincere question: Don't you feel the lack of static typing?

We've begun to use Elixir and Phoenix at work, and it's far nicer to work with than Rails - there's far less magic going on, and being functional, there is much less mutable state to keep in your head. That said, I still miss a rich type system. Typespecs can get you some of the way, but they're unreliable, and there's no support for parametrically polymorphic functions so far as I can see, which limits the usefulness of protocols for typechecking purposes.

Static typing is not a single issue. It is several.

From a high-level-language standpoint, static typing is a crutch. It isn't necessary, but it forces you to do things "the right way"... according to some definitions of the right way. It is possible to make mistakes without static typing that you would not make with it... but if you're careful you can also do some good things without it that you can't do with it. It all depends on whether you feel more comfortable with taking control or you feel the need for some restrictions to keep you "in line".

From a purely performance standpoint, there is no question: static typing compiles/interprets to faster code.

> From a high-level-language standpoint, static typing is a crutch

I see types as a high-level design tool. They allow me to reason about a domain, and figure out how to structure things at a high level before delving into the implementation. Yes, performance is a great side-benefit, but it is not always the driving factor.

I've put it on my list of things to learn - it looks great. Looks like a pleasure to write.

As someone who used to do (still do a bit) C and Ruby for embedded stuff but now does RoR for an ecommerce site, webdev can be a soul-crushing mind-numbing bore, but there are jobs and it pays. Rails is decent, especially if you are working on a site where server costs are not a significant factor in site costs. It is worth learning.