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.
The go-lang handler is the replacement server side
Edit, upon further investigation I think you are right. I thought I could use htmx for some things without JavaScript but it doesn’t seem like that, or it’s just such a rare goal that it’s hard to find that implemented. Back to the drawing board if I want this app to run in a browser without JavaScript and not natively. Or I can just accept that I need JavaScript enabled for the server with no other dependencies.
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.
The go-lang handler is the replacement server side
Edit, upon further investigation I think you are right. I thought I could use htmx for some things without JavaScript but it doesn’t seem like that, or it’s just such a rare goal that it’s hard to find that implemented. Back to the drawing board if I want this app to run in a browser without JavaScript and not natively. Or I can just accept that I need JavaScript enabled for the server with no other dependencies.