4 ms·
Exilir is exactly the better approach, sadly worse is better, so rubinius is the approach that will get the most adoption. (Unless exilir compatibility with ra
by fleitz 11y ago
Exilir is exactly the better approach, sadly worse is better, so rubinius is the approach that will get the most adoption.
(Unless exilir compatibility with rails approaches that of rubinius)
- sanderjd 11y agoPersonally, I don't find the library gap between ruby/rails and elixir/phoenix for simple web applications to be particularly onerous already, and it will only get better.
- mrinterweb 11y agoNot totally sure what you mean. Elixir will never run rails, but the phoenix framework has some similarities to rails.
- issaria 11y ago> has some similarities to rails. LOL
- dkarapetyan 11y agoI don't think worse is better applies here. There's also JRuby and rubinius is in a weird limbo state where it's not quite Ruby like JRuby and it's not quite another language like Elixir. Similar thing happened to Dart I think. It was stuck in limbo and never got adoption. So between JRuby and Rubinius I choose JRuby because I've used it in the past and it's great. The fact that JRuby folks try super hard to maintain compatibility is also really nice. I want to know who is actually using Rubinius and in what capacity and why.
- adamkittelson 11y agoWill it? My knee-jerk reaction to this was that Elixir already has more adoption than Rubinius, but then I stopped paying attention to Rubinius years ago. Do people use it for real stuff?
- matthewrudy 11y agoI agree. Elixir is already being pickup up for real projects but I feel like Rubinius has only ever been a play thing.