3 ms·
I really like Elixir and Erlang, but haven't found he time to play with Phoenix. But... > You're right basically, but the migration wave from > rails to ph
by steveklabnik 10y ago
I really like Elixir and Erlang, but haven't found he time to play with Phoenix. But...
> You're right basically, but the migration wave from
> rails to phoenix has noticeably started, and
> it shows.
People have previously said this about:
* Clojure
* Node
* Go
And lots of things before that.
- rdtsc 10y agoThere is a difference this time. Phoenix and Elixir was created specifically with an eye towards Ruby developers. Jose is working for a Ruby shop from what I understand. Go was C++ ++ or Java++ or Python++, Node was front-end brought to the backend kinds deal (or "you only need to know only language" deal). Clojure is an interesting one, but I haven't gotten much to play with it, so don't have much to say about it.
- sotojuan 10y agoClojure will never take off as a "Rails killer" because well, it's a Lisp. Sounds superficial but it's the truth. Also, from what I see it doesn't have an opinionated framework like Phoenix or Rails. That said, neither does Node.
- KurtMueller 10y agoThere's Luminus: http://www.luminusweb.net/ http://www.luminusweb.net/ And then there's its competitor, Arachne: http://arachne-framework.org/ http://arachne-framework.org/
- anonyfox 10y agoSure! But this time (tm) it's different. Phoenix is a direct drop-in replacement for rails, with a bunch of strong benefits on top. Getting productive for a rails developer should be 1-2 weeks max, since one already knows how the framework works conceptually. The truly cool stuff happens when one learns how stuff works beneath the surface. While you're around: Elixir/Erlang in itself is a rather slow language when it comes to number crunching performance. The canonical way currently is to write NIFs in C for these parts. But if this native code crashes, the reliability promise of BEAM goes out the window. For me it would make much more sense to write native extensions in Rust. Have you ever considered to include a plugin to "mix", Elixir's build tool, that allows one to ship Rust source files alongside the Elixir application, which then at compile time fetch a Rust compiler, compiles the code on the current platform and generates a NIF? This would be so huge.
- davidw 10y ago> direct drop-in replacement Uh... "Drop-in replacement is a term used in computer science and other fields. It refers to the ability to replace one hardware (or software) component with another one without any other code or configuration changes being required and resulting in no negative impacts." That's not the case at all with Phoenix, nice as it may be.
- anonyfox 10y agoPoint to you. I should have looked up the actual definition.
- rozap 10y agoYou might be interested in this project: https://github.com/hansihe/Rustler https://github.com/hansihe/Rustler
- anonyfox 10y agothis looks like it could really fit. Can I use this in a phoenix app and then deploy to Heroku without problems?
- steveklabnik 10y ago> But this time (tm) it's different. Everyone always says that :) That said, your sibling comment makes good points here. > While you're around: I think this idea is _really_ cool, but I'm not equipped to build such a thing, since I haven't had enough experience with them yet. I agree that that would be super cool.
- out_of_protocol 10y ago> Everyone always says that :) Truth to be said: there were some good languages but never good frameworks. After rails it's really hard to touch these semi-baked flawed "rails copies". And Phoenix is the first framework that not only replicates good rails sides (other web frameworks failing even that) but also fixes most (actually important) rails issues.
- dogweather 10y agoAnd therefore, what? :-) You imply a conclusion, but i'd like to know what you believe this implies.