3 ms·

> The Elixir community doesn't seem to aim for popularity (at least several important maintainers have said so on ElixirForum). Wow, then why does every Rails

> The Elixir community doesn't seem to aim for popularity (at least several important maintainers have said so on ElixirForum). Wow, then why does every Rails thread has an Elixir guy trying to tell us what an inferior software we're running? For the sake of humanity? > and will get more and more important as our CPUs can't get faster single-core performance and are just getting more cores. I don't think it will become more important in web dev world than it is now. We're here churning out back office CRUD apps like crazy, I don't know what you're doing. For a small team trying to get something up and running this really doesn't matter and that's what Rails is optimised for. If scale ever matters, if you scale that big, you probably already have the resources to deal with it. For the few startups that have huge scale + have very scarce resources and Elixir works well for them - great! I have no issues with that at all.

pdimitar 6y ago
> Wow, then why does every Rails thread has an Elixir guy trying to tell us what an inferior software we're running? For the sake of humanity? If you prefer that melodramatic phrase. I've been a Rails dev for 6 years and I know that many current Rails devs don't dare try something else -- call it a survivorship bias, fear to abandon what pays the bills now, habits, and most of the time you won't be wrong. Every now and then I speak with some of them and we exchange ideas. And you should stop stereotyping, it's juvenile and definitely has no place in HN.
- joelbluminator 6y ago
  > I know that many current Rails devs don't dare try something else OK, and I'm the one generalising yes? Clearly you have zero bias towards the Rails devs. How about simply becoming really good in a skill instead of jumping stacks every 5 years? To REALLY become good in Rails, to the point where you can write gems for activerecord for example that do something cool with arel, or follow the work Tenderlove is doing easily, this type of good takes effort. and time. Some people don't care at all and will happily switch and rebuild that expertise (or will never become experts in anything). That's totally fine. I value expertise, and won't make the switch for something that on the surface doesn't look like will benefit me at all (again, concurrency as it is in Rails is just fine for my career path and I think most Rails devs are on the same boat).

pdimitar 6y ago

> Wow, then why does every Rails thread has an Elixir guy trying to tell us what an inferior software we're running? For the sake of humanity? If you prefer that melodramatic phrase. I've been a Rails dev for 6 years and I know that many current Rails devs don't dare try something else -- call it a survivorship bias, fear to abandon what pays the bills now, habits, and most of the time you won't be wrong. Every now and then I speak with some of them and we exchange ideas. And you should stop stereotyping, it's juvenile and definitely has no place in HN.

joelbluminator 6y ago
> I know that many current Rails devs don't dare try something else OK, and I'm the one generalising yes? Clearly you have zero bias towards the Rails devs. How about simply becoming really good in a skill instead of jumping stacks every 5 years? To REALLY become good in Rails, to the point where you can write gems for activerecord for example that do something cool with arel, or follow the work Tenderlove is doing easily, this type of good takes effort. and time. Some people don't care at all and will happily switch and rebuild that expertise (or will never become experts in anything). That's totally fine. I value expertise, and won't make the switch for something that on the surface doesn't look like will benefit me at all (again, concurrency as it is in Rails is just fine for my career path and I think most Rails devs are on the same boat).