From 96af546bed08e2cac5bb5c320318d8d501607fdb Mon Sep 17 00:00:00 2001
From: Expo on server <expo@expo.survex.com>
Date: Wed, 28 Feb 2024 15:54:56 +0000
Subject: [PATCH] HTMX - online edit of handbook/troggle/trog2030.html

---
 handbook/troggle/trog2030.html | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/handbook/troggle/trog2030.html b/handbook/troggle/trog2030.html
index 5b30409c0..861318a78 100644
--- a/handbook/troggle/trog2030.html
+++ b/handbook/troggle/trog2030.html
@@ -11,7 +11,7 @@
 <h1>Troggle in 2025-2030</h1>
 
 <h2>5-Year Plan</h2>
-<p>[Philip Sargent, 1 June 2020. Async updates 21 April 2021]
+<p>[Philip Sargent, 1 June 2020. Async updates 21 April 2021, HTMX updates 28 Feb.2024]
 <ul>
 <li>I reckon django has at least another 4-5 years left as a very active project (~2025) and at least a decade or so as a well-maintained project.
 <li>I reckon python has another 10-20 years at least.
@@ -166,6 +166,8 @@ A GIS db could make a lot of sense. Expo has GIS expertise and we have a lot of
 <p>We have been waiting for more than a decade and a half for <a href="trogspeculate.html">the JavaScript Framework mess</a> to sort itself out. We want to see where we could sensibly move to a front-end+back-end architecture, instead of redrawing every screen of data on the server (see above "<a href="frontends">Things that could be a bit sticky 2 - front-end code</a>").
   
   <p>In 2024 it now looks as if we may be able to stretch the current architecture into a <a href="trogspeculate.html#frontends">post-Javascript</a> era entirely because Webassembly <a href="https://thenewstack.io/webassembly-4-predictions-for-2024/">continues to develop rapidly</a>.
+    
+    <p>HTMX now looks like it may evolve into replacing large chunks of what is now done with JavaScript packages (Angular, React, Vue.. and jQuery before them). See <a href="https://testdriven.io/blog/drf-vue-vs-django-htmx/">Django/HTMX</a>  article (5 Feb.2024).
 
 <h3>Postscript</h3>