4 ms·
I'm really excited about Exilir because it makes creating DSL like the Phoenix Web Framework, trivial. However, I am concerned though that developing in Erlang
by tiffanyh 12y ago
I'm really excited about Exilir because it makes creating DSL like the Phoenix Web Framework, trivial.
However, I am concerned though that developing in Erlang is a paradigm shift for most developers (eg letting apps crash when unexpected behavior occurs, concurrency model, etc) and Exilir makes it too easy to think you're developing in a procedural language when you're not.
I wonder if I'm alone with this concern. One thing simply the Erlang syntax does well is re-enforce the idea of how to fundamentally change how to develop applications to fit its model yet Exilir hides all of that
Edit: typo
- tomp 12y agoAre you by any chance familiar with Flask/Sinatra? Is Phoenix in any qualitative way better (more flexible/costumizable/simpler) than those two?
- chrismccord 12y agoPhoenix sits somewhere in b/w Sinatra and Rails custom/simplicity wise, while offering features that neither address, i.e. (realtime communication with browsers, native iOS, & soon android clients). "Qualitatively better" is a loaded question, but by virtue of Erlang VM, Phoenix apps can be distributed across a cluster without extra fanfare. You could run 20 Phoenix routers, load-balanced on a cluster, and everything like Webscokets/pubsub would "just work". i.e., no extra layer in b/w like redis or rabbit, no code changes, and no issues with things like sticky sessions.
- ad_hominem 12y agoFYI it's called Elixir, not Exilir.
- jdeisenberg 12y ago100% agreement here. Erlang doesn't look like an procedural language, so I'm not tempted to think in procedural terms. Also, Erlang's single-binding variables tends to keep me honest.(edit: add next sentence) That being said, Elixir does have some very nice features and is quite well designed; José Valim and other contributors are very open to input.