chrismccord

13 ms·

91.
by chrismccord 5y ago
That's really the goal, and for a large class of applications we are already there. Higher-fidelity UIs is pretty vague and there is absolutely a limit to where you necessarily need a bunch of code running on the client. Google maps &a
92.
by chrismccord 5y ago
Just a small nit-pick here. If we're talking REST/graphql stateless APIs, sure the scalability gains may be a harder sell vs throwing hardware at the problem, but the value-add depends on what's being built. I built Phoenix f
93.
by chrismccord 5y ago
We're already there. We have huge companies using elixir and phoenix, with phoenix powering the web platform for the majority of them. Several great case studies exist on elixir-lang.org if you're interested, ie: Pepsi: https:&#x
94.
by chrismccord 5y ago
These are great suggestions. The getting started guides on Elixir and Phoenix get you moving with the basics. Beyond that, Programming Elixir, Elixir in Action, and Programming Phoenix are great book options.
95.
by chrismccord 5y ago
Phoenix creator here – I'm happy to answer any questions about elixir, phoenix, or this release!
96.
by chrismccord 5y ago
Not with LV 0.16, but slots is one of our top priorities after Phoenix 1.6 / LV 0.16 is out
97.
by chrismccord 5y ago
It's neat to see channels getting some love here! They were the main reason I started Phoenix seven or so years ago, and they were the first major feature to land in the framework. I'm happy to answer any questions here about chan
98.
by chrismccord 5y ago
It will scale just as well as any other stateful application built with Phoenix, such as one using Phoenix Channels, which we've shown can scale to millions of simultaneous connections. LiveView allows you to mark which data you want t
99.
by chrismccord 5y ago
Phoenix creator here. Stimulus Reflex and most LiveView-like solutions do not perform diffing that LiveView does, so you are receiving the entire page/template for every change which adds to the overhead. You are correct that purely cl
100.
by chrismccord 5y ago
For a frame of reference, an Erlang VM running all of Phoenix will consume 16MB memory on startup, so we need more details on what exactly you've heard and for what usecases. For the Phoenix channels 2M connection benchmark, some folks
101.
by chrismccord 6y ago
There’s already a PR for it with a video of autocomplete in action :) https://github.com/elixir-nx/livebook/pull/208
102.
by chrismccord 6y ago
Since LiveView is built on phoenix channels, it's the same story. Simply pass the `transport: LongPoll` option to the LiveSocket constructor and you're now using long polling with LV :)
103.
by chrismccord 6y ago
This has been a long time coming for us on the phoenix-core team. I'm really excited about what this unlocks for use cases that would have previously been too complex to implement for many devs, such as post-processing, cloud uploads,
104.
Real time communication at scale with Elixir at Discord(elixir-lang.org)
19 points by chrismccord 6y ago|0 comments
105.
by chrismccord 6y ago
To be fair, Pi Zero's are $5, which will happily run nerves. Outfitting with relevant hardware for the task at hand will of course increase the price (as would any hardware product), but the "$35 pi" is a little misleading. Y
106.
by chrismccord 6y ago
We are actually working on a `mix phx.gen.auth` generator. Check Dashbit's blog about it: https://dashbit.co/blog/a-new-authentication-solution-for-ph...
107.
by chrismccord 6y ago
As always, I can make no guarantees before 1.0, but we have really focused on refining the programming model and APIs for the last several months, so we're in a good state currently.
108.
by chrismccord 6y ago
"offline support" is strictly on the side of needing to run a lot of code on the client, so this is where we draw a line and say you need a js framework, of which there are number of great options. We have javascript interop via p
109.
by chrismccord 6y ago
Confirm. LiveView will apply css loading state classes, which are user defined, but we generated css by default in new apps to lock the UI with loading cursor, and show a top loading bar. On reconnect, which happens automatically, we rematc
110.
by chrismccord 6y ago
I also forgot to mention we provide optimistic UI features with our loading states and annotations. For example, in the screencast, the "Save" button has phx-disable-with="Saving...", which applies on client instantly an
111.
by chrismccord 6y ago
you are correct, you can't escape the laws of physics latency wise, but most web things we are all building, including 100% JavaScript apps require a round trip to the server. For example I can't post tweet without a round trip to
112.
by chrismccord 6y ago
Absolutely. We have extremely varied usage in the wild. From sports/content websites with tens of millions of users (bleacher report, cars.com), to folks running social/chat services with millions of persistent connections, to fol
113.
by chrismccord 6y ago
We are really excited about this release! I also wanted the screencast to be a single take, so I'm happy to answer questions if there are gaps to fill in for things I could have explained more clearly.
114.
Build a real-time Twitter clone with LiveView and Phoenix 1.5(phoenixframework.org)
548 points by chrismccord 6y ago|244 comments
115.
by chrismccord 7y ago
Check out our "temporary assign" documentation – you only hold on to the state you need. That said, you are right that a LV application will necessarily use more memory than a stateless JSON API, but there is more nuance to the st
116.
by chrismccord 7y ago
Yes, in the above gist the connect are params used, so connect params are a general purpose mechanism for state recovery. In the above example a form is used, but on mount you can do whatever you'd like with the data. Thanks!
117.
by chrismccord 7y ago
In my ElixirConf keynote, I highlighted how automatic form recovery is on the roadmap, provided we can determine that such a recovery is possible on reconnect. More advanced dynamic forms will require manual recovery, and as you said it can
118.
by chrismccord 8y ago
Neat project! We indeed support nesting in LiveView :)
119.
by chrismccord 8y ago
Also to be clear, if you are already in the Elixir web ecosystem, EEx (Embedded Elixir) templates are what you currently write for regular server HTML rendering. LiveEEx allows you to take those same templates and support the diffing opti
120.
by chrismccord 8y ago
Cowboy maintainership has not been an issue, but there are other options in the Erlang and Elixir ecosystem for webservers, ie elli, chatterbox, and Ace. And to be fair, chatterbox is an Erlang http2 server that has been around for 3 years

More ›