> and it feels like we have this huge unfair advantage over our competitors.

As one man company I feel you on this. May is subjective, but starting from watching people that spend literally weeks to combine some buggy wordpress plugins to build out a functionality that is essentially just CRUD to folks who build multi server, multi service apps for just a few hundred monthly users. Where we just run a few generators, add a few major gems and can start focus on the fun stuff.

Although rails alone is enough to carry ruby. I think there is likely just not enough reason to use ruby over python in most non web use cases.

Is there particular reason to use it over Python even in web use cases? I'd say it's pretty arbitrary, choose what you know, or on the basis of the main library or two you'll need to use.

I've worked in a Ruby/Rails team within a mostly Django company.

Sure it's not fair to compare mostly Django to mostly Rails.

However our team was tasked most things that had a higher complexity but should be done rather fast. I think Django slightly limited their flexibility for business logik that doesn't follow their standard pattern. This is all anectotal however. The reason I prefer ruby is simply because I like it more.

I would consider this kind of the disadvantage of Ruby. If everything is obvious nothing is.

This is why we have things like Rails. I can instantly tell if a project was done by someone who loves rails or someone who just does it. If someone understood what it wants, everyone after them will be able to instantly find and understand the code.

Pure Ruby on the other hand... I've read some scripts that are as hard to parse as perl for me, some others that could be a copy of the official tutorial.

What does that mean?

There is a continuum between a language that's very restrictive and forces you to do things one way (I'd think of Go as one pole here), and a language that provides countless redundant ways to do things without clear advantages over another, and in my opinion Ruby goes too far in the direction of giving you too many ways to do things. The disadvantage of that is that it works against uniformity in a project and makes each file its own little puzzle.

> too many ways to do things

If there are many ways, then there is no obvious way, but then the "if" part of what you said does not apply.

I think your thought is much better captured by "if everything is possible, nothing is obvious".

You’re probably right. I was just thinking it is not “obvious” what code does after the fact.

What languages do you think your competitors are using that are slowing them down?

What kind of advantages?