A Well-Designed JavaScript Module System is Your First Architecture Decision | CSS-Tricks
css-tricks.com
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.
  • CubitOomEnglish
    95·
    5 months ago

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

      • CubitOomEnglish
        3·
        5 months 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.

          • CubitOomEnglish
            1·
            5 months 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 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.

      • MadhuGururajan@programming.devEnglish
        2·
        5 months 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.