Behind every technology, there should be a guide for its use. While JavaScript modules make it easier to write “big” programs, if there are no principles or systems for using them, things could easily become difficult to maintain.
I’m making a htmx/go-lang app right now. And as someone who browses the web with NoScript enabled, my first architectural decision was indeed to not use JavaScript and process everything sever-side.
You don’t know me.
I’m making a htmx/go-lang app right now. And as someone who browses the web with NoScript enabled, my first architectural decision was indeed to not use JavaScript and process everything sever-side.
The htmx won’t do anything then either.