For saas as a solo dev, Rails would be faster for you to get up and running, rails also specifically caters to solo SaaS devs. but python is much more popular (you can look up the yearly stack overflow survey for more info) and you'll find developers much more easily. Consider Django, a similar MVC batteries included framework. I say this unbiased as a ruby and python hater lol
Why do you hate ruby and python?
Ask HN: Are startups still using Ruby on Rails to start new products/projects?
11–19 of 19 posts
Re: Ask HN: Are startups still using Ruby on Rails to start new products/projects?
#12Re: Ask HN: Are startups still using Ruby on Rails to start new products/projects?
#13Never seen ruby/rails at any company or startup. react seems to be the standard.
Re: Ask HN: Are startups still using Ruby on Rails to start new products/projects?
#14Re: Ask HN: Are startups still using Ruby on Rails to start new products/projects?
#151. Nonsense 2. Even if true what it has to do with your goals and circumstances? If you’re good at it - you use it, unless shipping actual product asap is not your main priority
Re: Ask HN: Are startups still using Ruby on Rails to start new products/projects?
#16Never seen ruby/rails at any company or startup. react seems to be the standard.
Re: Ask HN: Are startups still using Ruby on Rails to start new products/projects?
#17My two cents, although there are probably some more people qualified to answer this: Avo, Sidekiq, Gorails etc. can make a living. Why couldn’t you?
Re: Ask HN: Are startups still using Ruby on Rails to start new products/projects?
#18Re: Ask HN: Are startups still using Ruby on Rails to start new products/projects?
#19There is something about Rails' convention over configuration that plays really well with LLMs, and I love not having to fiddle with _too_ much javascript (it's still tbd whether hotwire and stimulus is actually better than react from my POV).
I've recently started also exploring Hotwire Native to get mobile apps launched and so far have been really impressed that it "mostly just works".
If I'm successful, I'm sure I will get to a scale where I'm wishing for static typing, but so far I've been able to accomplish way more with Rails in the same amount of time than I have in any other stack.
To answer your question, I'm very open to paying for features that I think will save me time (such as JumpStart). From what I've read, however, I think that's a hard road to go down to be frank.