Err I guess you sort of brought some points that I've learned through pain: * ) Hot code reloading is only done in scenarios where it must be. It's not somethi

Err I guess you sort of brought some points that I've learned through pain: * ) Hot code reloading is only done in scenarios where it must be. It's not something that's common or recommended in Erlang/BEAM. Most everyone actually just does rolling restarts. * ) EXRM is one the most frustrating pieces of software I've ever used. I don't mean offense to the folks working on it, but it's caused me days of lost time. I'm actually moving to just using RelX-- its vastly simpler without the "magic." EDeliver is mostly just one helluva shell script. You could accomplish the same with say, Capistrano, or by hand pretty easily. I know, cuz I done it. * ) Re: web frameworks, as I've found getting more exposure in the Erlang world-- most folks are already so productive in Erlang because of it/BEAM it seems silly to use monolithic frameworks. This was perhaps the most shocking revelation I had. I think as we Rubyists enter the community and "want to improve it," without learning why it's done this way-- we're just gonna push a community of bad solutions. Or solutions that probably aren't really needed after the first few weeks with the platform. Looks at exrm. ... Hopefully this came off as a discussion (on my part) and not hating on folks or the hardwork theyve shared with the community. My apologies if that's not how it came off... I've just been feeling more frustrated with Elixir (still love it) and they've have been solved by not using an "Elixir" solution but instead using the "old school Erlang" solution.