I wonder why Ruby users don’t flock to Crystal, and Python users to Julia. With all the whining about performance and types, they just stay put.
I've seen a lot of people (myself included) going from ruby to elixir
As an outsider, a non-Ruby-user, I find it strange that Ruby users seem to be migrating to languages that are similar only in syntax but vastly different in nearly every other imaginable way.
Do Ruby users care only about syntax?
Maybe I'm not so different? Maybe my preference for ALGOL syntax just gives me more language options?
I wonder why Ruby users don’t flock to Crystal, and Python users to Julia. With all the whining about performance and types, they just stay put.
Most of the people whining about performance and types probably don't actually use Ruby day to day.
I dunno. I used to use a lot of Ruby. The lack of types regularly made my life a real pain. I ended up building frameworks[0] tied really tightly to dry-struct to try to work around that, and it wasn't great.
I use TypeScript for everything I used to use Ruby for, save for the occasional file munging inside of `pry`.
I've seen a lot of people (myself included) going from ruby to elixir
As an outsider, a non-Ruby-user, I find it strange that Ruby users seem to be migrating to languages that are similar only in syntax but vastly different in nearly every other imaginable way. Do Ruby users care only about syntax? Maybe I'm not so different? Maybe my preference for ALGOL syntax just gives me more language options?
It's a "get hooked with the syntax, stay for the features" situation. Elixir leverages the incredible robustness of the erlang virtual machine. So much so, that for me, anyways, it's hard to imagine using anything else without losing sleep anymore.
I wonder why Ruby users don’t flock to Crystal, and Python users to Julia. With all the whining about performance and types, they just stay put.
Crystal does not have mature web frameworks like Rails.
It doesn't have battle-tested everything and the kitchen sink like Rails. It has plenty of frameworks though. They just happen to be far more like ExpressJS for node, or Sinatra for Ruby. In this day of microservice/thin JSON API-style apps, Rails might be overkill. I'm not saying it's bad, it just might be a little much.
I use Python and I just don't like 1-based indexed languages. I would say that a better replacement for Python(at least for backend) is Go.
Go removes so much of the expressive power that writing it after Python is a bit of a pain. OTOH I realize that many people don't use that expressive power and are happy with copy-pasting stuff.
I’m waiting for generics to land before I return to Go.
Most of the people whining about performance and types probably don't actually use Ruby day to day.
I dunno. I used to use a lot of Ruby. The lack of types regularly made my life a real pain. I ended up building frameworks[0] tied really tightly to dry-struct to try to work around that, and it wasn't great. I use TypeScript for everything I used to use Ruby for, save for the occasional file munging inside of `pry`. [0]: https://github.com/modern-project/modern-ruby
This is pretty much the route I’ve taken, except I used an internal framework at Airbnb for typings instead of “dry-...”.
These days I write Typescript. I’m excited for Deno, which looks like it’ll solve most of the Node bullshit.