The browser expects JS, since JS was made for the browser, so you make a front in JS. But now you need a back, and hey, you already have all models and repos in JS, might as well make the back with JS.

It's a vicious cycle. Honestly, JS is fine for either if you are component enough (ie. not using stuff like "is-number"), don't get the hate on It.

[–] rimjob_rainer@discuss.tchncs.de 3 points 3 months ago (1 children)

No, JS is for scripts, it should have never been a whole framework for a frontend. But we can't get away from it now, because it's the only thing we have for browsers.

[–] JaddedFauceet@lemmy.world 5 points 3 months ago (2 children)

What do you want to use for frontend framework then?

python, ruby, java, C? Invent a new language?

you will see me screaming "X is for Y, it should have never been a whole framework for a frontend"

[–] rimjob_rainer@discuss.tchncs.de 5 points 3 months ago (1 children)

Anything, as long as it's not a bunch of scripts which form a framework after you downloaded a terabyte of shady dependencies.

[–] JaddedFauceet@lemmy.world 2 points 3 months ago

React it is then 😄. It only has 2 dependencies:

- react
    - loose-envify
        - js-tokens

https://www.npmjs.com/package/react?activeTab=dependencies

[–] fruitycoder@sh.itjust.works 4 points 3 months ago

Static? I mean for most of the web it honestly seems like the move. HTMX?