this post was submitted on 11 Sep 2023
29 points (78.4% liked)

Programming

17024 readers
321 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
29
Are we ready for javascript without a build step on the front end in 2023? (lemmy.fbmac.net)
submitted 1 year ago by fbmac@lemmy.fbmac.net to c/programming@programming.dev
48 comments fedilink hide all child comments
 

On the current typescript / anti-typescript internet drama I saw someone mention javascript without a build step.

Do you think we're already there?

Last time I attempted it:

  • there were too many libraries I couldn't import
  • JSX (using babel) had a warning saying you shouldn't do it in the browser for production
  • there was some advice against not using a bundler, because several requests for different .js files is slower and bigger than a bundled package
you are viewing a single comment's thread
view the rest of the comments
[–] Rooki@lemmy.world 25 points 1 year ago (14 children)

I dont get the third point. Its weirdly written.

Imagine not using typescript. The python community gaslighting the js community. Imagine a big project website, and all in plain js, + multiple devs. Thats is going to be a mess. Never going back from TS.

[–] icesentry@programming.dev 1 points 1 year ago (5 children)

If you want type safety and no build step you do like svelte did and use jsdoc instead. You can run the typescript type checker on those annotations so if you care about not having a build step you can still have type safety.

[–] realharo@lemm.ee 1 points 1 year ago (1 children)

That sounds like spending a lot of extra effort just to avoid a little up-front effort.

[–] icesentry@programming.dev 1 points 1 year ago

How is it extra effort? It's just a comment instead of inline types. It's not like going from no types to types everywhere.

load more comments (3 replies)
load more comments (11 replies)