edisonywh
There are other services out there like Stoop Inbox, Feedly & Feedbin that also does the same thing, but point being that I think newsletters are fundamentally different from an "email" and thus deserve a special treatment (similar to how Podcasts are just RSS feed underneath, but it's fundamentally a different product)
If the process dies, the Supervisor invokes the `terminate/2` callback so you're still able to process events.
Here are the relevant lines: https://github.com/plausible/analytics/blob/b724def948d51a0f...
Keep in mind you need to trap exit signal to tell the supervisor to invoke the callback, as done so here: https://github.com/plausible/analytics/blob/b724def948d51a0f...
The erlang docs also mentions this: https://erlang.org/doc/design_principles/gen_server_concepts...
It's a Rails-like framework written in Elixir (piggyback-ing off 30 years of BEAM), and LiveView changes the game by allowing you to build rich front-end application from your backend.
The way it works is that it serves you static HTML on initial load (yay SEO), and then it establishes a websocket connection to the server (very efficient thanks for BEAM), and every subsequent user interaction sends a event_name which you handle on the backend, and the backend respond with only the changed data (Phoenix can intelligently track your changes so it only sends what has actually changed), and then morphdom on the browser side patches things onto front-end.
You get the full power of interactivity but you barely have to touch any front end at all (and if you really do, it plays super well with AlpineJS, so you still get that escape hatch).
All in all, LiveView is amazing (and the surrounding technology), I just wish more people know about it!