Our live_link’s and live_redirect’s will also be much faster because it happens over the established websocket connection, so if you are doing things like pagination within a running live view, you don’t have to refetch current user/org/etc and do all the setup/teardown of the request 
chrismccord
Creator of Phoenix
10
cnck1387
So for clarity, in the semi-short term are your plans to fully replicate Turbolinks inside of LiveView? In other words, being able to just load new content in (with push state) behind the scenes and now only the body of your page will be swapped out between page views with no extra work at all?
This makes a tremendous difference for the better in page loads because the browser doesn’t need to parse all of your CSS and JS on every request.
Although Turbolinks does quite a bit more than that too, which is nice. I’m currently using it in a Phoenix app today but it would be nice to drop it for LiveView eventually.
tomekowal
Hey, @chrismccord Can you post the elisp config to enable mmm-mode like that?
I thought it would be only:
(require 'mmm-auto)
(setq mmm-global-mode 'maybe)
(mmm-add-mode-ext-class 'elixir-mode "\\.ex\\'" 'web-mode)
but I get Invalid or undefined submode class: web-mode error.