Programming

17313 readers

102 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

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 1 year ago

MODERATORS

[email protected]

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] 6 points 1 year ago (2 children)

About the third point, the performance of your JavaScript code can be worse if it's broken down into several small files rather than a single, bundled file. When a browser encounters a script tag linking to an external JavaScript file, it makes an HTTP request to fetch that file. This process occurs for each separate file. Each HTTP request involves time for network latency, server processing, and data transfer.

I'm usually preferring typescript too, but this point got me curious. I'm guessing it wasn't an honest point, almost everywhere I look people are still using a build step, and I didn't notice any move in a different direction

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

Http/1.0 would require serial connections, and the "multiple files bad" absolutely applies. Bundling and minification into a single JS file was common, even required - and I would consider that a build step. Otherwise you are dealing with all your code in a single massive file.

On http/1.1 browsers would open 6-8 concurrent connections to fetch files simultaneously. At this point, code splitting had benefits.

Most webservers now run http/2 which can fetch multiple files at the same time over the same connection. I believe it is "virtually unlimited" and the initial connection setup - which is often the largest performance hit - only happens once. At which point code splitting has such little impact on the transport layer, that it is more perfomant than transferring and loading all the code.

https://blog.vespa.ai/http2/ Has an more details as well as some load testing against http/1.0, http/1.1 and http/2

[–] YourAvgMortal 1 points 1 year ago

There is also a limit to the number of files the browser can download in parallel, so if many files have to be fetched, they have to wait until the previous downloads are finished. This slows down performance even more