diff --git a/handbook/troggle/trog2030.html b/handbook/troggle/trog2030.html index 90f07203c..3d291054f 100644 --- a/handbook/troggle/trog2030.html +++ b/handbook/troggle/trog2030.html @@ -205,17 +205,14 @@ A GIS db could make a lot of sense. Expo has GIS expertise and we have a lot of

Postscript

-

Andy Waddington, who wrote the first expo website in 1996, mentioned that he could never get the hang of Django at all, and workinhttps://github.com/Chaoyingz/flect - - -

- g with SQL databases would require some serious book-revision: +

Andy Waddington, who wrote the first expo website in 1996, mentioned that he could never get the hang of Django at all, and working with SQL databases would require some serious book-revision:

-So a useful goal, I think, is to make 'troggle2' accessible to a generic python programmer with no specialist skills in any databases or frameworks. Pugainst that is the argument that that might double the volume of code to be maintained, which would be worse. Nevertheless, an aim to keep in mind.https://github.com/Chaoyingz/flectno +So a useful goal, I think, is to make 'troggle2' accessible to a generic python programmer with no specialist skills in any databases or frameworks. Put against that is the argument that that might double the volume of code to be maintained, which would be worse. Nevertheless, an aim to keep in mind. But even 'just Python' is not that easy. Python is a much bigger language now than it used to be, with some increasingly esoteric corners, such as the new asyncio framework.. - +

Postscript2 - end of 2024

+

The AI wave is just starting and Option 3 could be just to stick with Django indefinitely and use AI programmer aids to help new coders understand and edit existing troggle. An AI can grok the whole thing.


Return to: Troggle design and future implementations