this post was submitted on 11 Sep 2023
32 points (80.8% liked)

Programming

18101 readers
48 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 [email protected]

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
32
Are we ready for javascript without a build step on the front end in 2023? (lemmy.fbmac.net)
submitted 1 year ago by [email protected] to c/[email protected]
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
[–] [email protected] 13 points 1 year ago (9 children)

Why though? I think I am missing the point, but I don't see the problem with having a build step in your projects. Especially for frontend it is not just JavaScript, but things like Sass/SCSS to consider etc.

[–] [email protected] 7 points 1 year ago* (last edited 1 year ago) (7 children)

When there's no build step, all the time is spent coding. None of it is spent configuring or setting up.

The hardest part of any software class in my experience is the triple combo of:

  • installation
  • "well it works on my machine" and
  • "well this code worked for last semester's class"

When I have students start off editing one html file using pinned URL imports, the reliability is just insane. People might claim "installing typescript is reliable" but doesn't even come close to the reliability of not having a build step at all. No build step Just Works™, no M1 Mac edgecases, no npm audit, no rm rf node_modules.

[–] [email protected] 4 points 1 year ago
  • Svelte/Vue/React components need to be compiled
  • JavaScript should be minified if the project has a significant size
  • File names should have a content hash, so they can be cashed in the browser
  • Even with HTTP/2, there's still a case to be made for bundling hundreds or thousands of JS modules into a single file for better performance
  • Bundlers give you a dev server with live reload and hot module replacement for great developer experience
  • Setting up Vite is really easy and requires minimal configuration (compared to Webpack, for example)
load more comments (6 replies)
load more comments (7 replies)