Phoenix LiveView 1.2 Released

6/14/2026 at 9:29:04 AM

I've been using Phoenix for super basic things for a very long time since I first discovered it at the Elixir meetup in ATX.

I haven't touched it in a while, Since writing code these days, as most of us know, it's basically steering an LLM.

So I wonder how good are LLMs at writing Phoenix or Elixir so to speak? Time for me to create another side project... and figure it out.

by orliesaurus

6/14/2026 at 7:06:49 AM

LiveView is such a breath of fresh air, especially over the vibe coded NextJS rats nests that have become the norm (that need specialized hosting, are dog slow and require a ton of proprietary paid services bolted on like caching, background workers and even auth which Elixir and Phoenix provide out of the box).

https://elixirisallyouneed.dev

by cpursley

6/14/2026 at 9:06:51 AM

I've been loving LiveView. Been using it for a project for a client recently and it's so... chill. I like it a lot.

by AdamConwayIE

6/14/2026 at 8:25:54 AM

What caching is provided out of the box for Phoenix framework?

by Tinkeringz

6/14/2026 at 8:48:17 AM

Doesn't seem to be mentioned in the page but if you're talking about request caching there's libraries like PlugHTTPCache or RequestCache.

Otherwise I usually use Nebulex (annotations are nice for Ecto queries) with ETS as it's faster than with Redis (if you don't care about losing the cache on deployment).

by conradfr

6/14/2026 at 7:33:20 AM

What are the pros and cons compared to ASP.Net/Blazor?

by candl

6/14/2026 at 7:46:01 AM

The BEAM virtual machine. Its has lightweight isolated processes, message passing, supervisors, hot-ish runtime introspection, and fault containment are not libraries bolted on later. They are the substrate. not an after thought.

if you are build an app that needs the following: + many concurrent users + real-time UI + background jobs + workflows + stateful sessions + distributed events + failure isolation + “this thing should keep running for months”

You're going to want the thing built on the BEAM.

by weatherlight

6/14/2026 at 7:48:02 AM

But it doesn't have neither AOT nor JIT.

by zerr

6/14/2026 at 7:54:40 AM

I believe BEAM bytecode is now JIT-ed.

EDIT: It is, since OTP 24 was released in 2021:

https://www.erlang.org/downloads/24

> The BeamAsm JIT-compiler has been added to Erlang/OTP and will give a significant performance boost for many applications. The JIT-compiler is enabled by default on most x86 64-bit platforms that have a C++ compiler that can compile C++17.

by arcanemachiner

6/14/2026 at 7:54:15 AM

What about https://www.erlang.org/doc/apps/erts/beamasm.html

by conradfr

6/14/2026 at 7:53:14 AM

elixir/erlang gets compiled into beam byte code. It's a vm. why does this matter..

by foxes

6/14/2026 at 9:19:59 AM

It's an interpreted byte code run (interpreted) by BEAM. Not a native binary run by CPU.

But apparently BeamAsm JIT solves the issue? As mentioned in the sibling comment.

by zerr

6/14/2026 at 7:57:25 AM

TLDR; LiveView is web only.

There have been efforts to make LiveView native, but it’s extremely difficult to do so, and thus far (to my knowledge) all have failed.

I was thinking about this the other day because carsandbids (Doug DeMuro’s car auction site) uses Blazor (at least as far as I can tell). And I think that’s one of its biggest advantages of Blazor—- is that it is capable of producing native apps and web apps while LiveView is resolutely not. And that’s because Microsoft can pay for it (or at least sponsor huge amounts of supporting infrastructure).

And FWIW— that’s an extremely difficult problem to solve. It requires an enormous amount of funding, both a huge team capable of both understanding Android and iOS SDKs and capital to employ folks on pure engineering challenges (hence why MS or Meta can). End users don’t care if it’s made with LiveView, Blazor, React, Java, SwiftUI, et. al. And, the list of companies that can facilitate that long term is extremely small.

There’s also the issue of OTP being non-trivial to implement or meaningfully transpile into another language/runtime. Erlang, BEAM, and OTP were made together for each other in a very peculiar and specific way, for a specific set of problems, and if it wasn’t a necessity that they were developed together it would be a dead language, runtime, and platform (and for the record it’s absolutely not).

by rubyn00bie

6/14/2026 at 9:04:30 AM

I am a fan of the idea, but the websocket is also quite a big attack surface; you can do a lot more by sending messages over this socket to your phoenix app than you would likely expect to have exposed via some api on another framework.

It’s difficult to secure, in my opinion. Perhaps not impossible but the cost of doing so pretty much eclipses the benefits of using liveview imo.

by cyberpunk

6/14/2026 at 9:29:24 AM

Why? It's the client that initiates the connection.

by kitd

6/14/2026 at 9:18:18 AM

I haven’t used it for anything in production so I haven’t seen these issues, could you give a bit more detail? I’m mostly wondering why you’d have any more websocket messages that you respond to than you would APIs if you were using any other approach. Does LiveView itself respond to certain messages bypassing your app?

by mcintyre1994

6/14/2026 at 8:10:03 AM

Why not just build mobile apps in their native language (Swift etc)? Anyways, end users absolutely notice and care - cross platform mobile apps are all hot garbage without exception.

by cpursley

6/14/2026 at 8:52:44 AM

Especially now that you can likely throw the mobile conversion to an LLM and judge the feasibility of it's maintenance once it's done.

by epolanski

6/14/2026 at 8:18:35 AM

That’s what I would do that personally. I hate wrappers around native SDKs. But I also learned them.

A lot of folks assume mobile apps are “difficult” because of the underlying language. But it’s not the language that’s an issue, it’s the SDKs. They’re so wildly different from each other, and the way things work on the web, that it’s (IMHO) a losing proposition to do so.

That’s not to say things like Blazor or React Native don’t have a place but that place is one that’s inherently difficult to maintain without huge amounts of ongoing effort and capital invested in non user facing features.

by rubyn00bie

6/14/2026 at 8:10:04 AM

I’m not sure how I feel about the CSS integration. Nor the collocated JS that was somewhat recently released.

On one hand, yes it is convenient, but on the other it could become a huge mess. It reminds me of Rails 2.x where it became almost impossible to debug, or fix front end code that used rjs or whatever it was called. Because disparate snippets of JS were littered throughout your code base in files that were hard to find.

I’m sure the Phoenix team has put a lot of effort into it, and I truly hope it slaps. I myself am just really hesitant to use it, when CSS files and non colocated JS work just fine. I’ll probably be waiting a couple years before giving it a try

by rubyn00bie

6/14/2026 at 8:55:17 AM

To be honest that's copied from the JS frameworks. I tend to agree with you but sometimes scoped CSS is nice to have.

by conradfr