From 8feb7f5389c80e1576398f9331784d8a3241a79f Mon Sep 17 00:00:00 2001 From: Expo on server Date: Thu, 29 Feb 2024 12:26:59 +0000 Subject: [PATCH] url - online edit of handbook/troggle/trog2030.html --- handbook/troggle/trog2030.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/troggle/trog2030.html b/handbook/troggle/trog2030.html index 861318a78..d18be2cc3 100644 --- a/handbook/troggle/trog2030.html +++ b/handbook/troggle/trog2030.html @@ -163,7 +163,7 @@ A GIS db could make a lot of sense. Expo has GIS expertise and we have a lot of

WebAssembly Front-Ends

[January 2024]
-

We have been waiting for more than a decade and a half for the JavaScript Framework mess 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 "Things that could be a bit sticky 2 - front-end code"). +

We have been waiting for more than a decade and a half for the JavaScript Framework mess 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 "Things that could be a bit sticky 2 - front-end code").

In 2024 it now looks as if we may be able to stretch the current architecture into a post-Javascript era entirely because Webassembly continues to develop rapidly.