31 ms·
+1 to learning Plug before Phoenix, too. Sometimes I feel like I have god mode activated when co-workers or friends are hung up on the connection life cycle or
by rubiquity 10y ago
+1 to learning Plug before Phoenix, too. Sometimes I feel like I have god mode activated when co-workers or friends are hung up on the connection life cycle or not sure how a piece of Phoenix works/scales. I'd add a basic understanding of OTP to that list as well.
Phoenix does do an excellent job of getting people to try Elixir, kind of like how Rails did for Ruby. Phoenix has also added a cool abstraction in Presence/CRDTs. Now that people don't have to implement that themselves I wonder if that will be as useful to people like how ORMs stormed onto the scenes in the early 2000s.
- carlesfe 10y agoAuthor here, I definitely agree. I tried to learn Phoenix just after Elixir, and I just couldn't do it. Now I've written a couple of simple web apps with Plug, and realized that I don't need Phoenix for most of my use cases.
- goldbrick 10y agoWould you say that Plug is the Rack of Elixir?
- rubiquity 10y agoYes that's exactly the domain that Plug sits in. It's an interface from web servers to applications. As someone who tinkered around with Rack and Ruby web servers a lot, Plug is much better designed (yay for learning from past implementations).
- alxndr 10y agoI'd even say that Phoenix is more akin to Sinatra than to Rails.