23K views · Mar 11, 2016 · 55:28 · 2 HN recommenders · 6 mentions · discussed 2016–2022
A joint Erlang Factory 2016 keynote by Phoenix creator Chris McCord and Elm creator Evan Czaplicki on using the two together, including Phoenix.Presence design and PubSub optimizations.
Why Hacker News points people here: Pointed to as the best source on Phoenix Presence internals and for combining Phoenix with Elm.
“My Erlang Factory keynote also goes into the design considerations and PubSub layer optimizations that sits underneath Phoenix.Presence”HN comment, 2016
“My Erlang Factory keynote also goes into the design considerations and PubSub layer optimizations that sits underneath Phoenix.Presence”
Keynote covering Phoenix.Presence design and PubSub optimizations.
My Erlang Factory keynote also goes into the design considerations and PubSub layer optimizations that sits underneath Phoenix.Presence: this video
“There is a nice talk from Erlang Factory 2016 called "Making the Web Functional with Phoenix and Elm”
Talk on using Phoenix and Elm together.
There is a nice talk from Erlang Factory 2016 called "Making the Web Functional with Phoenix and Elm" this video
“I liked this video from Erlang Factory about using Phoenix and Elm together.”
Half Phoenix, half Elm intro with nice debugging and error messages.
Speaking of Elm I liked this video from Erlang Factory about using Phoenix and Elm together. They both have a functional flavors so I think it might appeal to same people: this video The first half is about Phoenix, the second about Elm. I don't know much about front-end stuff but I did like the Elm bit as an intro, especially the debugging and nice error messages part.
“They used a combination of CRDTs with heartbeats to implement it.”
Explains Phoenix.Presence, CRDTs and heartbeats solving distributed presence.
The Phoenix Framework (web framework for Elixir) already solves this for you.[1] It's called Phoenix.Presence. They used a combination of CRDTs with heartbeats to implement it. You are right, it is a hard problem because of the distributed nature of Erlang/Elixir. That's why Chris provided a framework level solution for it. [1] this video (Erlang Factory SF 2016 Keynote Phoenix and Elm – Making the Web Functional)
“the keynote at 2016's Erlang Factory conference was a shared talk between Chris McCord (creator of Phoenix) and Evan Czaplicki (creator of Elm)”
Shared keynote by creators of Phoenix and Elm.
I wonder if the same might happen to Elm, should Phoenix adopt it as their browser language of choice. There's definitely a connection there -- for what it's worth, the keynote at 2016's Erlang Factory conference was a shared talk between Chris McCord (creator of Phoenix) and Evan Czaplicki (creator of Elm), "Making the Web Functional" [0] [0] this video
“Chris McCord had fun implementing a CRDT in Phoenix.Presence”
Chris McCord implements a CRDT in Phoenix.Presence.
Chris McCord had fun implementing a CRDT in Phoenix.Presence: this video (from about 17 mins by the looks of things).
