From b04c32ecaaad147f45c2247a66da30e0166568d4 Mon Sep 17 00:00:00 2001 From: Henrik Nyh Date: Sat, 11 Jul 2020 20:40:29 +0100 Subject: [PATCH] =?UTF-8?q?Use=20a=20literal=20=C2=B9=20for=20footnote?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 'frameworks1' didn't look great in the Twitter link card. Though I suspect that one's now cached forever… This link is a tiny tap target. Should figure out something better some day. Perhaps a "pill" style – I feel like a previous iteration of this blog had that. --- ...0-07-11-optimising-data-over-the-wire-in-phoenix-liveview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/site/posts/2020-07-11-optimising-data-over-the-wire-in-phoenix-liveview.md b/src/site/posts/2020-07-11-optimising-data-over-the-wire-in-phoenix-liveview.md index 4070df3..e3ebc2f 100644 --- a/src/site/posts/2020-07-11-optimising-data-over-the-wire-in-phoenix-liveview.md +++ b/src/site/posts/2020-07-11-optimising-data-over-the-wire-in-phoenix-liveview.md @@ -5,7 +5,7 @@ tags: - Phoenix LiveView --- -[Phoenix LiveView](https://github.com/phoenixframework/phoenix_live_view) distinguishes itself from other "server-side reactive" frameworks[1](#footnote) by automatically sending minimal diffs over the wire. (That is to say, over a WebSocket.) +[Phoenix LiveView](https://github.com/phoenixframework/phoenix_live_view) distinguishes itself from other "server-side reactive" frameworks[¹](#footnote) by automatically sending minimal diffs over the wire. (That is to say, over a WebSocket.) Well, mostly automatically. The size of those diffs is affected by how you write your app.