[joshvince]

Ruby on Rails has recently started actively marketing itself as the solo developer framework. I've worked with it for a long time now (among a bunch of other languages and frameworks) and I have to say the recent updates to the frontend 'story' are really compelling for a solo dev.

One of the compelling reasons to write JS on the server was to have the same language and ecosystem in the client and server, and things like Turbo for Rails really go a long way towards delivering on that for Ruby (although of course you still need to understand javascript and browsers.)

That said, if you're already familiar with something else, then pick the most mature batteries-included framework in that language. Languages are just a tool for the job, it's incredibly unlikely as a solo dev that you can pick a "wrong" one.

[arromatic]

It's not about picking the wrong one . What i am trying to know is which one can be most productive in short : doing most in less.

[Lio]

That's a very difficult question to answer without carrying out a proper study.

Languages, libraries and frameworks constantly evolving so it's a moving target too.

I think most people will just recommend the stack they know best unless you have more specific criteria.

Again, I don't think you can go wrong with Rails for web apps as a solo dev.

You get a lot of utility out of the box with Rails and you can also easily remove things you know you won't need.

e.g. Little utilities like Array#to_sentence[1] might not seem important at first but they're real time savers when you're working on your own to get something out the door.

1. https://api.rubyonrails.org/classes/Array.html#method-i-to_s...

[joshvince]

If you don't already know a language and its ecosystem, then I'd recommend Rails. It is simply the most mature and batteries-included framework. Ignore the claims that it is dead - if you're a solo developer the specific jobs market doesn't matter.