A Well-Designed JavaScript Module System is Your First Architecture Decision (css-tricks.com)

submitted 1 month ago by codeinabox@programming.dev to c/javascript@programming.dev

6 comments fedilink hide all child comments

all 7 comments

sorted by: hot top new old

[-] CubitOom@infosec.pub 5 points 1 month ago

Actually, my first architectural decision was to not use JavaScript.

[-] AudaciousArmadillo@piefed.blahaj.zone -1 points 1 month ago* (last edited 1 month ago)

Hot take in a JavaScript community. By someone not working in web development.

[-] CubitOom@infosec.pub 3 points 1 month ago

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.

[-] NigelFrobisher@aussie.zone 3 points 1 month ago

The htmx won’t do anything then either.

[-] CubitOom@infosec.pub 1 points 1 month ago* (last edited 4 weeks ago)

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 rare goal that it's hard to find that implemented. Backbto the drawing board if I want this app to run kn a browser and not natively.

[-] MadhuGururajan@programming.dev 2 points 1 month ago

Exhibit A of why "web developers" get disrespected by the rest of the software developer community and mocked for not being real software developers.

Learn the fundamentals and you don't need to pretend that Javascript and the ecosystem surrounding it is not unnecessary suffering.

this post was submitted on 16 Apr 2026

8 points (83.3% liked)

JavaScript

2723 readers

1 users here now

founded 2 years ago

MODERATORS

erlingur@programming.dev

Ategon@programming.dev

nick@programming.dev