From b293cb91cf6c4de45fef947b772ff86294b7941e Mon Sep 17 00:00:00 2001
From: Expo on server <expo@expo.survex.com>
Date: Sat, 6 Jan 2024 16:18:28 +0000
Subject: [PATCH] add id link and Expo 2030 mention - online edit of
 handbook/troggle/trogspeculate.html

---
 handbook/troggle/trogspeculate.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/handbook/troggle/trogspeculate.html b/handbook/troggle/trogspeculate.html
index a73a50bd7..af5db1569 100644
--- a/handbook/troggle/trogspeculate.html
+++ b/handbook/troggle/trogspeculate.html
@@ -31,7 +31,7 @@ effort. [ See <a href="https://en.wikipedia.org/wiki/Comparison_of_JavaScript_fr
 Wikipedia list of javascript frameworks</a>.] With our deep historical perspective ("cough"),
 we can expect <a href="https://www.circleid.com/posts/20201031-the-javascript-ecosystem/">this 
 menagerie to sort itself</a> out into a stable, standardised foundation 
-within the next couple of decades but probably not within the next 10 years.
+within the next couple of decades but probably not within the next 10 years [i.e. by April 2029, in time for Expo 2030].
 (ECMAscript 12 is definitely on the way to making these frameworks redundant.)
 <p>
 A web API to expose the troggle database (read-only) would allow some keen
@@ -69,7 +69,7 @@ this addresses <strong>our biggest problem: devising  something that can be
 maintained by fewer, less-expert people who can only devote short snippets
 of time and not long-duration immersion</strong>.
 
-<h4>Front-ends update</h4>
+<h4 id="frontends">Front-ends update</h4>
 <p>Three years later (re above) and there is still no sign of stability in front-end 
 frameworks. There are now some Python frameworks, so maybe one of these will give us 
 the stability we want that Javascript is failing to provide, such as <a href=