3 ms·
On the one hand I certainly see why you could interpret it that way. On the other hand, Elixir seems to emphasize the easy use of existing Erlang libraries on a
by brightball 10y ago
On the one hand I certainly see why you could interpret it that way. On the other hand, Elixir seems to emphasize the easy use of existing Erlang libraries on a regular basis for everything from crypto to leveraging BEAM for hot deployment.
Regarding mature web frameworks - there are a lot of those for every language. What's attracting people to Phoenix isn't it's maturity, it's the lessons learned from other very mature frameworks that can't easily be fixed without a full rebuild. There's too much in that area to get into without a series of blog posts.
The other area where you're seeing some reinventing is usability. Drawing in people from the Ruby community around Elixir has a huge amount of value because there's no programming community that I've ever been around that puts developer workflow and efficiency at such a high premium.
There may be perfectly good libraries to use as the basis for functionality but the odds are good that if those libraries have too high of a barrier to entry, someone will try to improve that.
That's most of what I've seen at least. Elixir folks that I've observed so far have done very little other than singing the praises of what's already in Erlang/BEAM. I'm seeing emphasis placed on Observer, HiPE and Dialyzer. EXRM is abstracting a lot of what needs to happen to automate BEAM hot code deploys and now there's another library Edeliver that wraps EXRM to further streamline the process for developers.
Just my observation of the community so far, but it definitely seems to me like most of the reinvention is coming from the developer streamlining standpoint which is only going to make things more accessible to more people.
- rubyn00bie 10y agoErr 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.
- brightball 10y agoThat's the thing about Phoenix though, it's not a monolithic framework because of Elixir. There's actually some great talks about that at ElixirConf too such as "Phoenix is not your application" emphasizing that Phoenix is nothing more than an interface to get to the actual parts of your application. Admittedly, I'm only just getting into exrm so it's a bit hard for me to say just exactly how complicated it will end up being.