programming-phoenix-liveview
purerl
programming-phoenix-liveview | purerl | |
---|---|---|
6 | 6 | |
13 | 314 | |
- | 1.3% | |
10.0 | 5.9 | |
almost 3 years ago | 4 months ago | |
Elixir | Haskell | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
programming-phoenix-liveview
-
Elixir as first programming language
Read and watch tutorials: Thinking Elixir - a podcast that explores different aspects of the Elixir programming language: https://thinkingelixir.com/ Learn Elixir - a free interactive tutorial that teaches Elixir from scratch: https://www.learnelixir.tv/ Programming Phoenix LiveView - a book that teaches how to build web applications in Elixir using the Phoenix framework https://pragprog.com/titles/liveview/programming-phoenix-liveview/
-
Phoenix 1.7.0 Released: Built-In Tailwind, Verified Routes, LiveView Streams
A good project based book that goes pretty in depth is: https://pragprog.com/titles/liveview/programming-phoenix-liv...
- Projects with best practices
-
Phoenix 1.7 is View-less
LiveView is evolving into a great piece of tech, but as others have noted elsewhere in the comments one of the challenging parts with LiveView right now (and to an extent Phoenix) is the outdated books & tutorials.
Bruce Tate and Sophie DeBenedetto have been authoring the book “Programming Phoenix LiveView” (https://pragprog.com/titles/liveview/programming-phoenix-liv...) which has the potential to be a great source for people that want to really dive into LiveView. The challenge though is they have not updated it to support the changes introduced in 0.18.0 which makes it really hard to start using the book when a new Phoenix application “mix phx.new dev_app” looks different than what’s in their book and some of their code breaks with the default installed versions of included plugs.
While I wish the book would receive an update sooner that brings it back to a compatible state (meaning there are no issues following along with the book), the good news is they have committed to having the book be updated when LiveView hits 1.0.
-
How to get started with LiveView?
I suggest cloning down an actual LiveView project (maybe this one?) and making changes to it. That will help you get a grip on things more easily than trying to build something from scratch right away.
purerl
-
Erlang: The coding language that finance forgot
I will put in a good word for PureScript for the beam with `purerl`. It's my go-to for writing BEAM code nowadays. Notably PureScript tooling including LSP, package management, etc., just works, so you are able to just get to work in internalizing the way OTP and other Erlangy things are expressed in a statically typed, pure language.
https://github.com/purerl/purerl & https://purerl-cookbook.readthedocs.io/ for more information. Join the PureScript discord and the #purerl channel if you want help.
-
purerl - Integrating PureScript into Elixir projects
purerl is a compiler for turning PureScript code into Erlang code, so that you're able to write BEAM (the Erlang virtual machine) applications using it.
-
Phoenix 1.7 is View-less
You've been able to write PureScript that compiles to Erlang and has perfect interop for years, via `purerl`[0]. Using it with Elixir is as simple as adding `purerlex` as a compiler and having your PureScript code automatically compile when `mix` compiles things, and off you go.
In terms of the typing itself, it's exactly what you get in all of PureScript, strict static typing with no `any` or the like. Using `Pinto`, the de facto OTP layer in PureScript your processes are typed, i.e. their `info` messages & state are typed, which means that they are all much more like strongly typed state machines than anything else.
You can see an example of a basic `gen_server` here:
https://pastebin.com/UTEfz7Wg
The differences aren't very big in terms of what you'd expect to be doing. One small thing to note is that the `GenServer.call` expects a closure to be passed instead of having the split between `gen_server:call` & `handle_call`, removing the need for synchronizing two places for your messages being sent and handled.
0 - https://github.com/purerl/purerl
- Angular without SSR is faster than Next.js with SSR. I have the data
- Beam VM Wisdoms
- V0.14 of Gleam, a type safe language for the Erlang VM, has been released
What are some alternatives?
unsplit - Resolves conflicts in Mnesia after network splits
hamler - Haskell-style functional programming language running on Erlang VM.
FunkyABX - Audio blind tests
Gradualizer - A Gradual type system for Erlang
elixir-ls - A frontend-independent IDE "smartness" server for Elixir. Implements the "Language Server Protocol" standard and provides debugger support via the "Debug Adapter Protocol"
lumen - An alternative BEAM implementation, designed for WebAssembly
elixir_koans - Elixir learning exercises
gleam - ⭐️ A friendly language for building type-safe, scalable systems!
livebook - Automate code & data workflows with interactive Elixir notebooks
erllambda - AWS Lambda in Erlang
bandit - Bandit is a pure Elixir HTTP server for Plug & WebSock applications
js-framework-benchmark - A comparison of the performance of a few popular javascript frameworks