Re:Is There Too Much CSS Now?
by naasking on Monday November 07, 2022 @01:08PM
(#33509634)
By that argument JavaScript is also compiled, so this point is wrong no matter how you interpret it: if "interpreted" means source code is transmitted and then executed in whatever fashion, then both JS and CSS are interpreted, if "interpreted" means a specific execution model on the client machine, then they are both JIT compiled and neither are interpreted.
[ Parent
| on HN ]
By that argument JavaScript is also compiled, so this point is wrong no matter how you interpret it…
The primary difference between a traditionally compiled language (like C) and CSS and JavaScript is C is compiled before execution and CSS and JavaScript are compiled during execution.
There’s a reason why JIT stands for Just In Time compilation [1].
Yes I know the difference, the point is that the original poster said CSS is faster because JS is interpreted. There is no way to intrepret that statement in a way that makes sense.
Sure there is - some people use interpreted to mean step-by-step, as in imperative. "CSS is faster because JS is imperative" is a charitable and correct reading.
But that is not correct, js is not interpreted/executed step-by-step in many cases (it is a bit more complicated, there are multiple interpreters and JIT compiler in the picture, it usually is started up by interpreting but then switched to JIT compiled native machine code).
The correct difference to make is the execution model, one being basically a Turing machine while the other is more similar to logic programming languages.
Re:Is There Too Much CSS Now?
by bryanrasmussen on Monday November 07, 2022 @02:35PM
(#33511133)
>By that argument JavaScript is also compiled, so this point is wrong no matter how you interpret it:
If JavaScript is not compiled how does hoisting work?