From 3017646bbfe2dfd24ab9e4947a6e7daf464c429e Mon Sep 17 00:00:00 2001
From: Philip Sargent <philip.sargent@gmail.com>
Date: Tue, 4 Feb 2025 00:34:11 +0000
Subject: [PATCH] Turbo - online edit of handbook/troggle/trog2030.html

---
 handbook/troggle/trog2030.html | 1 +
 1 file changed, 1 insertion(+)

diff --git a/handbook/troggle/trog2030.html b/handbook/troggle/trog2030.html
index 3d291054f..f468025fd 100644
--- a/handbook/troggle/trog2030.html
+++ b/handbook/troggle/trog2030.html
@@ -194,6 +194,7 @@ A GIS db could make a lot of sense. Expo has GIS expertise and we have a lot of
   <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).
+      <p>Hotwire and <a href="https://turbo.hotwired.dev/">Turbo</a> now also look interesting as ways to gain responsiveness yet not tie us into a heavyweight JavaScript framework (Jan. 2025).
 
 <h3>Django and Flask</h3>
 <p>The idea that we should replace Django with Flask comes up from time to time: "No! This is a really <em>shit</em> idea":<br>