Plain old Ruby on Rails is significantly more Lindy than this. And how about…

- LAMP (Linux, Apache, MySQL, PHP)

- CGI programming (/cgi-bin/)

- HTML, CSS, JS (with XMLHttpRequest to avoid full page reloads)

- AOLServer with Tcl (still developed as NaviServer)

- FTPing your HTML and CSS directly to the server

HTMX in particular is decidedly non-Lindy.

I was not familiar with Lindy as a concept but even the author seems to contradict themselves, in one passage claiming to be taking an approach which relies on mature technology and then in the next passage talking about how great htmx is.

I think even by the authors stated definition, Go would not be considered Lindy.

The approach shown is clever and interesting though!

The man who pushes the Lindy concept contradicts himself constantly. The theory does not stand up to rigorous analysis.

Doesn't fetch replace XMLHttpRequest? Or is that not Lindy enough...

I don’t mind the HTMX abstraction of JS and XHR but blindly exposing DB schema seems lazy. Clients generally don’t need or want this exposure but the “API” certainly can be replaced by notional views in a lot of cases.

PHP would be the Lindy backend tech, right?

Django is nice too.