Does anyone have any favorite open-source Phoenix codebases?
Phoenix 1.3.0 Released
61–70 of 143 posts
Re: Phoenix 1.3.0 Released
#62Earlier quoted context omitted.
Pattern Matching makes it easy to write small, understandable code The Concurrency Model is simple to the point where creating a whole pubsub system to handle events, push out notifications, and handles backpressure can be done in Finally the pipe operator is like C#'s LINQ statements but with so much more power and flexibility, hard to explain but I highly recommend cracking open that book on your nightstand!
The Elixir pipe operator |> is the equivalent of the Clojure thread first macro ->, right?
Which is to say it's equivalent to function composition.
Re: Phoenix 1.3.0 Released
#63Phoenix is great! I only wish there was one recommended way for authentication and authorization - there are so many [1] different libraries that I got stuck in researching the options - I am confused, do not know which one to use. What is your preferred way? I would like to avoid to implement every little detail on my own - to get security done right was the main reason for me using open source libraries. It would b…
The closest clone of Devise I found for Phoenix is Coherence https://github.com/smpallen99/coherence
Re: Phoenix 1.3.0 Released
#64For anyone curious about Phoenix and Elixir, I can sincerely recommend the following resources to get you started: - Programming Phoenix by Chris McCord, Bruce Tate, and José Valim [1] - The Little Elixir & OTP Guidebook by Benjamin Tan Wei Hao [2] - Elixir in Action by Saša Jurić [3] Phoenix initially attracted me to Elixir, I've stuck around for that and the OTP platform: pattern matching, process based concurrency…
+1 on "The Little Elixir & OTP Guidebook". It's a generally good introduction to OTP, though the book has a lot more errors than I'm used to seeing (their github code differs without explanation from the code in the book at times, and sometimes one or the other won't run successfully).
Re: Phoenix 1.3.0 Released
#65For anyone curious about Phoenix and Elixir, I can sincerely recommend the following resources to get you started: - Programming Phoenix by Chris McCord, Bruce Tate, and José Valim [1] - The Little Elixir & OTP Guidebook by Benjamin Tan Wei Hao [2] - Elixir in Action by Saša Jurić [3] Phoenix initially attracted me to Elixir, I've stuck around for that and the OTP platform: pattern matching, process based concurrency…
Elixir in Action is a bit outdated, no?
Re: Phoenix 1.3.0 Released
#66Earlier quoted context omitted.
Could you give some examples of 'neat' things that needed to keep going no matter what on django (thus switching to Phoenix)
I should have said Python instead of Django. The problem is that I was/still am a rookie of a programmer. I could not wrap my head around async in Python. I just wasn't getting it. I had a nagging sense that it was going to fail in the middle of the night and there was nothing I could do about it. So, enter Elixir, which actually has a syntax that is kind of close to Python. It made immediate sense. If you want to do…
Very satisfying , thanks !
Re: Phoenix 1.3.0 Released
#67For anyone curious about Phoenix and Elixir, I can sincerely recommend the following resources to get you started: - Programming Phoenix by Chris McCord, Bruce Tate, and José Valim [1] - The Little Elixir & OTP Guidebook by Benjamin Tan Wei Hao [2] - Elixir in Action by Saša Jurić [3] Phoenix initially attracted me to Elixir, I've stuck around for that and the OTP platform: pattern matching, process based concurrency…
This is the best Elixir material I've used: https://pragmaticstudio.com/elixir You build you a simple HTTP server using Elixir and learn a lot of the core language and architecture choices when writing Elixir code. It doesn't pester you with this is an int, this is a string. You just start building this HTTP server out and learn about Elixir along the way.
Learned a lot from the pragmaticstudio resource as well and couldn't recommend it highly enough.
Re: Phoenix 1.3.0 Released
#68Earlier quoted context omitted.
The beautiful thing about Phoenix framework is that there is no "one-true way" to do things. Rails is omakase, Phoenix is not, and that's a good thing. You want the whole enchilada? Use Guardian. Need oauth? Use ueberauth. Just want email and password? Use comeonin to hash your password. It's liberating to know exactly how your system works and that it's not hidden behind some magical blackbox like Devise.
For me the sweet spot is somewhere in between. If it just shipped with a decent auth module that would work for 90% of people, but that could also be easily replaced or extended if needed, that would be the best of both worlds.
Even rails doesn't ship with an auth module though. Lots of people use Devise and there is an equivalent for Elixir (Coherence)...but shipping with auth built in is an exploit waiting to happen IMO.
Re: Phoenix 1.3.0 Released
#69Does anyone have any favorite open-source Phoenix codebases?
Re: Phoenix 1.3.0 Released
#70Earlier quoted context omitted.
Thanks for the link. One thing I hated about Rails when I tried it was the level of magic involved. Does Phoenix suffer from that at all?
Something isn't magical if you understand the underlying concept/convention.
I tend to think of "magic" as meaning fragile, indirect coupling; for example "magic numbers" at the start of files, which are only meaningful if the consuming application has a corresponding pattern in its database.
Or sets of things which only work if given in a particular order. Or unrelated functionalities which interfere with each other due to implementation details. And so on.
In other words, leaky abstractions where thinking in terms of the concept has so many edge cases that it's easier to think in terms of the implementation instead. Or conventions which can only be used via memorisation, trial and error, stack overflow and reading the source (often this is due to shoehorning things into language models which aren't amenable; e.g. all of the things aspect oriented programming tries to do)