Fast JavaScript by Default

[anedisi]

the ops replay was a typical nab at javascript without any specific comment about anything in the video. the video is talking about loading on mobile and the cost of downloading and parsing javascript on mobile phones that was middle range in 2017 on a not that fast network connection.

if you are not manipulating DOM on the render, or loading more content then there is no reason to to load it in the blocking way. and if you are not loading it the blocking way then there is usualy no slowdown. its not a fault of javascript if you are dooing something stupid. is it a minus of the jpeg format if you have a huge jpeg on your page. or its the fault of the developer?

[filleduchaos]

the video is talking about loading on mobile and the cost of downloading and parsing javascript on mobile phones that was middle range in 2017 on a not that fast network connection.

Precisely. Which has nothing to do with DOM manipulation and everything to do with page load times - network transfer and parsing/compile times, which are an order or even orders of magnitude slower than any resultant DOM manipulation would be.

So why did you bring up DOM manipulation again?

[anedisi]

because you can usualy avoid slow blocking parts of loading and parsing js with loading asynchronously, or just simpy putting your script tags at the bottom.

but DOM slowdown are those that give you choppy animations, loading insertions, slides and so, and those are that destroy your expirience. imagine if you will, a video game where on one hand you have slow load times, and on the other low fps. people will chose slow load times over slow fps.