111–120 of 142 posts
Earlier quoted context omitted.
I generally recommend using ASDF to install Erlang/Elixir, it has support for Fedora. https://asdf-vm.com/guide/getting-started.html https://github.com/asdf-vm/asdf-erlang https://github.com/asdf-vm/asdf-elixir Slightly more ceremony than curl | sh, but a good tool to have.
Mise also has support https://mise.jdx.dev/
Phoenix creator here – excited to finally have shipped this! Happy to answer any elixir/phoenix/liveview questions. In case folks missed it, buried in the blog post is a new installer that lets folks try out elixir/phoenix in seconds. It installs elixir and generates a new phoenix project from a single command: osx/linux: $ curl https://new.phoenixframework.org/yourappname | sh windows powershell: > curl.exe -fsSO ht…
(Is it possible to add RSS to the blog? The articles are great but there is no good way to stay up to date.)
You can thank Steffen from the Phoenix team :)
Phoenix creator here – excited to finally have shipped this! Happy to answer any elixir/phoenix/liveview questions. In case folks missed it, buried in the blog post is a new installer that lets folks try out elixir/phoenix in seconds. It installs elixir and generates a new phoenix project from a single command: osx/linux: $ curl https://new.phoenixframework.org/yourappname | sh windows powershell: > curl.exe -fsSO ht…
Hi Chris Many thanks for all the years of dedication to Phoenix and value you've given to developers around the world. OT: any thought about updating the 9-year old perf benchmark blog post? And is bandit now recommended over cowboy? https://www.phoenixframework.org/blog/the-road-to-2-million-...
Congrats! This stable release is huge. I built my (unfortunately) failed startup using LiveView for ~18 months. It was actually really good to work with and a great product experience. I ended up integrating React into it as well for some particularly complex / mature libraries (react-grid-layout, WYSIWYG editor). Pretty seamless connection to backend LiveViews, and I tried to keep everything in LV as possible. The b…
Congrats! This stable release is huge. I built my (unfortunately) failed startup using LiveView for ~18 months. It was actually really good to work with and a great product experience. I ended up integrating React into it as well for some particularly complex / mature libraries (react-grid-layout, WYSIWYG editor). Pretty seamless connection to backend LiveViews, and I tried to keep everything in LV as possible. The b…
What were the problems and how did you solve them?
I know there are paradigms to handle that now, although the details get complex in practice. For example, the idea of a "portal" in react is actually really important for layering modals and popups properly, but it can be difficult in LiveView.
The biggest single challenge I remember hitting was dynamic recursive forms (for example a logic builder). It took a lot of effort to get right.
Now there’s some good news! I’ve been using LiveView for years now and couldn’t be happier with it. It’s a joy to work with, and has reinvigorated my love of web development. I’m so blazingly productive in LV it’s unreal. I try not to be too self-promoey on HN but this feels like as good as time as any: if this v1.0.0 release makes you want to finally learn LiveView, I humbly recommend my own course at http://learnph…
Will you update the course for v1.0 of Liveview? Thanks
Has anyone tried both LiveView and say Vaadin Flow to compare them? I'm using Vaadin now on a project and it's pretty great so far with Quarkus. The app is also only using like 200mb of memory with production traffic, and I have a compiled language to work with. That's the main thing I'm waiting for with Phoenix...
The combination of Elixir, Phoenix & LiveView really is incredible: "What about supporting production hot code upgrades where browsers can auto re-render anytime CSS stylesheets, images, or templates change – without losing state or dropping connections? Sure!". No replacing servers to push code changes, no telling people to logout & back in to see the changes. Crazy.
In my htmx project, the best I could pull off was: 1) every server build has a unique version ID 2) the version ID is embedded in the page on the first page load 3) on every htmx request (it can be done with a bit of HTMX configuration) the embedded version ID is sent to the server as a special HTTP header 4) a middleware on the server always compares the version IDs, and if they don't match, sends back a special "re…
If the first one, if you don't do it already, your reload header could act like a "preload" header ("Htmx-Preload-Root: 1234abcd") and tell the client which assets to start pulling even before a logical navigation click, so that they're hot in the cache when they eventually do that navigation.
Phoenix creator here – excited to finally have shipped this! Happy to answer any elixir/phoenix/liveview questions. In case folks missed it, buried in the blog post is a new installer that lets folks try out elixir/phoenix in seconds. It installs elixir and generates a new phoenix project from a single command: osx/linux: $ curl https://new.phoenixframework.org/yourappname | sh windows powershell: > curl.exe -fsSO ht…
Congrats on the release Chris! What JS solution/approach would you recommend to use with LiveView for pure client-side stuff?
I'm attracted to JS+Cloudflare because hosting seems predictable and reasonably priced.
Do people have good recommendations / experiences with hosting?