21–28 of 28 posts
I'd love to see someone who knows Exilir/Phoenix to submit it to the Web Framework Performance Shootout [1]. [1] http://www.techempower.com/benchmarks/ Edit: typo
I'd love to see Phoenix represented there. I'll see what's required to get it added.
Info below on how to submit your test suite.
http://www.techempower.com/benchmarks/#section=code&hw=peak&...
I'll start by saying that Phoenix seems specifically built for Elixir, while Chicago Boss appears to be an Erlang framework which works fine with Elixir after a minimal amount of initial configuration upfront.
Let's hope that can be resisted. As long as we can avoid the disease of Ruby Gems creeping over, it may just be ok.
Nice writeup. I hadn't looked at Phoenix yet. It seems that many Elixir people come from Ruby. One thing we should be wary of is making shallow ports of Ruby concepts into Elixir, when there's much more elegant approaches available. We, software engineers, have a tendency of doing this: for example, there's a whole bucketload of C# libraries that have Java roots (NHibernate, Spring.NET), and every single one of them…
> We should avoid making Elixir a Ruby-on-Erlang when it has the potential to be so much more. Elixir is fool-proof from turning it into a "Ruby on Erlang" simply because it embraces and improves on Erlang's programming model. Some libraries are ported over from Ruby. But there are also libraries ported from other languages and libraries that have been written for Elixir specifically. Just a heads up: please don't ma…
I've seen it improves on some tools and a fair deal of libraries, but I don't exactly see how it improves on the programming model itself?
Nice writeup. I hadn't looked at Phoenix yet. It seems that many Elixir people come from Ruby. One thing we should be wary of is making shallow ports of Ruby concepts into Elixir, when there's much more elegant approaches available. We, software engineers, have a tendency of doing this: for example, there's a whole bucketload of C# libraries that have Java roots (NHibernate, Spring.NET), and every single one of them…
Not to be That Guy, but why don't Elixir-ists just use Cowboy?
Earlier quoted context omitted.
> We should avoid making Elixir a Ruby-on-Erlang when it has the potential to be so much more. Elixir is fool-proof from turning it into a "Ruby on Erlang" simply because it embraces and improves on Erlang's programming model. Some libraries are ported over from Ruby. But there are also libraries ported from other languages and libraries that have been written for Elixir specifically. Just a heads up: please don't ma…
What do you mean by 'improves on Erlang's programming model '? I've seen it improves on some tools and a fair deal of libraries, but I don't exactly see how it improves on the programming model itself?
Elixir semantics is very close to Erlang's, but it also has things beyond what Erlang can offer as easily: macros, protocols, comprehensions with any kind of enumerable as a generator.
Of course, the core facilities provided by the runtime system are left unchanged: concurrency primitives, functional semantics, distribution, error handling (Elixir has slightly different conventions, but the idea of "letting it crash" remains). And in OTP land there are quite a few additions that simply make OTP more "elixirish" (like getting a lazy stream of events from GenEvent).
Nice writeup. I hadn't looked at Phoenix yet. It seems that many Elixir people come from Ruby. One thing we should be wary of is making shallow ports of Ruby concepts into Elixir, when there's much more elegant approaches available. We, software engineers, have a tendency of doing this: for example, there's a whole bucketload of C# libraries that have Java roots (NHibernate, Spring.NET), and every single one of them…
Cowboy [1] uses a router, I don't think its a rails-ism. Not to be That Guy, but why don't Elixir-ists just use Cowboy? [1] https://github.com/ninenines/cowboy
For those curious about the realtime layer in Phoenix, I have a screencast where we live code a Phoenix chat app. We've added a View layer since the recording, so ignore the rendering hack: http://chrismccord.com/blog/2014/05/06/how-to-build-an-elixi...
[1] - http://async-io.org/