2 ms·
> In Rails, a process is short-lived by design (the lifecycle of a request) Yes and no. Rails processes are so huge that they are loaded up and kept around be
by davidw 13y ago
> In Rails, a process is short-lived by design (the lifecycle of a request)
Yes and no. Rails processes are so huge that they are loaded up and kept around between requests. Erlang processes (which are not unix processes!) are much smaller and lighter. One Erlang program can handle tons of concurrent, always open requests, whereas Rails just isn't cut out for that.
As to what Erlang is good for, I think its sweet spot with web stuff is where you need a lot of always open connections, such as with web sockets.
I'm a fan of Erlang, but for most SaaS kinds of startuppy things, am not sure it's a good fit: you get so many more tools packaged up and easy to use for you with Rails that unless you know Rails does not work for you, I would almost always choose Rails.