So I'd guess the code would end up looking similar on a lot of teams
So I'd guess the code would end up looking similar on a lot of teams
It's not object oriented, it's a functional language. It is polymorphic and all data is immutable. (Edit: actually realised its very much not like ruby, when I re-read this)
What I've seen in most projects is that the awesomeness that is threading (tasks and processes) is not really used. Supervisors aren't built as first class citizens.
I see teams eat the cost of NIH, but not get the benefits of crash fast, crash often.
So yes it does end up looking/smelling like ruby/rails but it really really shouldn't.
“A language that doesn't affect the way you think about programming, is not worth knowing.”
You can know enough to get going quickly, but there's a healthy layer of power that will only come with time.
I should mention there is no problem not going there. I respect my teammates. Ruby/Rails is a great way to get things done. I would 100% use it as my MVP lang.