You're lost orchestrating a dozen of libraries with conflicting dependcies and configuration that's in flux.
I'm done with webpack, typescript, loser react eco system where you drag 10 libraries through your code as soon you learn them only for them to become obsolete in 5 months, done with docker/image, done with Babel and its plugins, done with graph ql, redux... Just random bs stuck together aphazardly
I plan to leave js and thus front end development altogether. So my question is what is a good choice for backend language, ecosystem and all. Where things come , if not batteries included, then at minimum designed intelligently to work together.
I used to care about performance, but I'm open to compromise now. Car's speed doesn't matter if it breaks down every other mile.
I'm leaning towards python, Ruby, and go
Tried and true principles and architectures will outlive any libraries. Remember, React is only 6 years old, do you think new projects will use React in another 6 years? Remember Meteor framework that was all the rage 7 years ago? I don't know anyone using it for new projects. It's the natural cycle of development. Don't get emotional about frameworks.
If anything, build _your own framework_. I don't mean a competitor to React or whatnot, but your own set of tools that can be reused over time across projects. Back in the days before jQuery, people were doing DOM manipulation themselves and everyone built their own wrappers around the DOM. Nowadays, I notice too many people reach for a framework without thinking about what they even want to accomplish.
At the end of the day, "best" is always subjective, relative to your own experience and expectations. For what it's worth, I used to be a node.js developer in the pre-1.0 days and switched to Rails, Elixir, Go, but I'll probably use node for my next project since it's super easy to get stuff running in messy JavaScript compared to something statically typed like Go. In most cases, performance is moot for projects without users. Hell, a CGI script written in Bash could rival the performance of modern web frameworks.
Don't just "look" at it, don't try to "check it out". If you never done any Lisp, Clojure will not look extremely sexy at the first glance.
But give it a heartfelt try, I guarantee - you will find something truly incredible. Something that is still missing in many, perhaps most other language ecosystems.
Both have a wide variety of libraries and a reliable VM.
Plus, if you want more productivity, or to use other programming paradigms, you can use C# or F# for the CLR, and Groovy, Kotlin, Scala, or Clojure for the JVM. I believe all of them have full access to all C# or Java libraries.
It has its warts (Python's tragic history with packaging systems) and Django isn't quite in the sweet spot anymore now that we usually only serve Rest Apis instead of Html pages. Python isn't typed (though there is mypy now) and slow, sometimes that matters.
So I don't know about "best", but that's an endless discussion anyway. We still get lots of mileage out of it.
if you write lots of rest API you should use Go and thank me later.
Personally, I had the most fun with Erlang and what happened to become N2O: https://github.com/synrc/n2o It is designed for speed not compromising reliability so it kind of looks like what you want.
Python+Django probably has better ecosystem though.