this post was submitted on 22 Sep 2023
26 points (90.6% liked)

Programming

17417 readers
81 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
26
Why are NodeJS projects often "bundled", but not other interpreted languages? (lemmy.ml)
submitted 1 year ago* (last edited 1 year ago) by cyclohexane@lemmy.ml to c/programming@programming.dev
10 comments fedilink hide all child comments
 

I mean, sure, that's probably heavily influenced by the need for bundling for the frontend.

But it isn't done blindly. Bundlers reduce the overall size of the code, either due to minification or tree-shaking (removing unused modules). It also removes the filesystem overhead of resolving and opening other modules.

Would bundling be useful in other interpreted languages?

I suppose you may count JVM's compilation to bytecode as being very similar.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] cyclohexane@lemmy.ml 2 points 1 year ago (2 children)

The size of the code still impacts your deployment. Moreover, if you're using something like AWS lambda, small changes can have significant influence on cold start time.

I agree that an extra step is not desirable, but this would only be done for production deployments (and consequently pre-prod if you do that).

[โ€“] palebluethought@lemmy.world 3 points 1 year ago* (last edited 1 year ago)

Lambda is certainly an interesting case for this, I'll give you that. Outside of that, though, the impact on deployment speed is also not relevant; the bottlenecks for deployment are things like CI, canarying, even rolling blackout windows across AZs, etc. The actual time spent transmitting your build artifact over the network is completely negligible even at huge sizes