3 ms·
Better for building out services. Parallel processing. The supervised process abstractions are incredibly powerful. If you're building another Twitter I would
by colbyh 11y ago
Better for building out services. Parallel processing. The supervised process abstractions are incredibly powerful.
If you're building another Twitter I would still use Rails. You'll be much more productive.
On the other hand, if you need to run parallel tasks or have mission-critical (aka can't go down for anything) work to be done I think you'll find Elixir the perfect combination of Ruby's syntax and Erlang's power.
Just my $.02 - I'm having a blast with Elixir at the moment.
- aaron-lebo 11y agoNah, if you really are trying to build the next Twitter Rails is a poor choice for architectural and scaling reasons. No need to repeat Twitter's own mistakes. On the other hand, if you are just building another web app, Rails is the better choice...
- colbyh 11y agoI mean, if you're building an app for Twitter scale on day one you're already doing something wrong. But yeah.