Comment

Comment on Which side are you? Javascript or Typescript

I’d agree with you if you were saying this about 8 years ago, but IMO the post-jQuery-front-end dust has settled and the “best” (in terms of what most organisations end up choosing) hasn’t really changed in a while.

Typescript unless you’ve got a really good reason not to.
React if you have anything remotely complex.
Webpack (or one of the wrappers) to bundle it up.

Sure, someone may like a React alternative, and that’s completely fine. But at the end of the day, most companies are using React because it’s basically industry standard at this point, and it’s got too much momentum behind it for that to change any time soon.

source

Sort:hotnew top

zebbedi@lemmy.world ⁨9⁩ ⁨months⁩ ago
Webpack… Aren’t you on the vite train?

source
- railsdev@programming.dev ⁨9⁩ ⁨months⁩ ago
  Ha! Webpack. I ripped that shit out as soon as import maps were added to Rails; I cut my Docker image size by 50% and kissed Node goodbye.
  
  source
Strawberry@lemmy.blahaj.zone ⁨9⁩ ⁨months⁩ ago
We must be in different organization circles because almost every frontend I’ve seen at my jobs or those of my friends at other organizations uses Angular

source
- Phen@lemmy.eco.br ⁨9⁩ ⁨months⁩ ago
  I’ll be honest, I think it’s been years since I last saw anyone even mention Angular anywhere.
  
  source
fidodo@lemm.ee ⁨9⁩ ⁨months⁩ ago
Maybe I’m just too used to it, but with next.js static site generation I find react to also work really well for simple sites too. If you’re not dealing with state, react is basically just functions that return html. IMO it’s pretty sleek for static websites since tsx let’s you do basic templating with functions.

source