4 ms·
JavaScript is used for a lot of different things. * Real-time, graphics-intensive applications (d3, three.JS, etc.) * Chrome extensions/PWAs * Server-sid
by ironmagma 4y ago
JavaScript is used for a lot of different things.
* Real-time, graphics-intensive applications (d3, three.JS, etc.)
* Chrome extensions/PWAs
* Server-side code (NestJS, Express, etc.)
* Server-client-side-hybrid code (SSR)
* Single page apps (React, Svelte)
* Documentation or static site generation (Gatsby, etc.)
* Query language (Mongo)
Further you have a lot of personalities you're supporting:
* Frontend devs
* Backend devs
* The complexity-embracing folks (React)
* The complexity-hiding folks (Svelte)
* Marketing teams who don't really want to be coding (Squarespace, jQuery, Alpine)
Even with all that, some tooling is going to be better at doing what it needs to than others. The tooling is all still very young, because we never settled on one right way to do it, probably because the package system in JS is so bananas. The bundlers/minifiers/packagers/transpilers all need to compete and come together still, it hasn't happened yet.