I can relate to your experience, James. I tried moving to other frameworks, even to better option you mentioned.
But rails has one big upside, which is hard to ignore -- maturity of libraries (gems). With a big probability I can find a library that satisfies my picky requirements.
With Phoenix and Elixir I still find myself spending too much time on very trivial things. Since I'm an indie dev -- this is a luxury I can't afford.
But I can afford rewriting some components in languages that performs better, if there is a bottleneck in Ruby itself. But in a lot of cases, I just know how to make Ruby performant :)
Yep, as a one-man-show, it's tough to argue there are a lot of better options that allow for more productivity/hour than RoR.
If I find myself in a situation working on something that has 1mm connections simultaneously, sure, I'll use Elixir. But to spin up a CRUD app, which honestly, are still to this day, most online web apps, Rails and Ruby are tough to beat.
I agree that Rubygems is one of the main reasons that people stick with Ruby and it is an amazing resource. I've written my fair share of gems over the years and I hope that they helped people in some way. Working with Phoenix can be pretty annoying when you can just get a hex package that just handles user authentication the way that devise does - you have to wire up a lot of code to get it to work. I think this is mostly about maturity but I think it will get there. I once joked that Elixir is powered by thousands of angry Rubyists and like all jokes I think there's more than a grain of truth in it.
I can write whatever I need just fine, if I need it.
I wrote my own "package" manager in ruby and have been using that for ~13 years to manage my *nix systems.
I once joked that Elixir is powered by thousands of angry Rubyists
Elixir has great ideas; erlang is awesome, but the syntax of erlang is UTTER SHIT.
But even then, too few people use elixir; and even fewer use crystal.
Say what you want about ruby but ruby IS used by LOTS of people.
I think this is mostly about maturity but I think it will get there.
This depends on how many people use a language. Crystal struggles a lot because of this - too few people go into crystal. Which is a shame. But I myself also am not using crystal, primarily due to lack of time; but also because the type-madness leads to syntactic monsters that I don't want to deal with.
Note that ruby 3.0 will get additional type information, so some of your fake-complaints above may be answered.
I still think your article is horrible though. Please try to make your points more objective in general.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I can relate to your experience, James. I tried moving to other frameworks, even to better option you mentioned.
But rails has one big upside, which is hard to ignore -- maturity of libraries (gems). With a big probability I can find a library that satisfies my picky requirements.
With Phoenix and Elixir I still find myself spending too much time on very trivial things. Since I'm an indie dev -- this is a luxury I can't afford.
But I can afford rewriting some components in languages that performs better, if there is a bottleneck in Ruby itself. But in a lot of cases, I just know how to make Ruby performant :)
Yep, as a one-man-show, it's tough to argue there are a lot of better options that allow for more productivity/hour than RoR.
If I find myself in a situation working on something that has 1mm connections simultaneously, sure, I'll use Elixir. But to spin up a CRUD app, which honestly, are still to this day, most online web apps, Rails and Ruby are tough to beat.
I use my own fake-webframework (created before rails came out).
Granted, it is way below feature parity with rails. But it also does not want to be feature equal.
I also use sinatra so I more belong into this world of simplicity.
And I am mega-productive related to the www there too, without needing RoR (but I value simplicity at all times; I hate the complexity of rails).
I just wonder why people think the www in ruby belongs to rails. I don't see it that way at all.
what is your framework?
I agree that Rubygems is one of the main reasons that people stick with Ruby and it is an amazing resource. I've written my fair share of gems over the years and I hope that they helped people in some way. Working with Phoenix can be pretty annoying when you can just get a hex package that just handles user authentication the way that devise does - you have to wire up a lot of code to get it to work. I think this is mostly about maturity but I think it will get there. I once joked that Elixir is powered by thousands of angry Rubyists and like all jokes I think there's more than a grain of truth in it.
Rubygems is great but I do not rely on it.
I can write whatever I need just fine, if I need it.
I wrote my own "package" manager in ruby and have been using that for ~13 years to manage my *nix systems.
Elixir has great ideas; erlang is awesome, but the syntax of erlang is UTTER SHIT.
But even then, too few people use elixir; and even fewer use crystal.
Say what you want about ruby but ruby IS used by LOTS of people.
This depends on how many people use a language. Crystal struggles a lot because of this - too few people go into crystal. Which is a shame. But I myself also am not using crystal, primarily due to lack of time; but also because the type-madness leads to syntactic monsters that I don't want to deal with.
Note that ruby 3.0 will get additional type information, so some of your fake-complaints above may be answered.
I still think your article is horrible though. Please try to make your points more objective in general.