tkirchner
Isn't the main purpose of an OS to bridge between the applications and the hardware? The hardware is pretty accurately abstracted as sth. with a state and input/output streams.
What is the purpose of abstracting the hardware as sth. without a state?
Isn't the main purpose of an OS to bridge between the applications and the hardware? The hardware is pretty accurately abstracted as sth. with a state and input/output streams.
What is the advantage of abstracting the hardware as sth. without a state?
Isn't the main purpose of an OS to bridge between the applications and the hardware? The hardware is pretty accurately abstracted as sth. with a state and input/output streams.
What is the purpose of abstracting the hardware as sth. without a state?
...maybe that the reason for all of this is that the CSS API (box model ..., box properties ...) is too complex and as a result browser implementations tend to f* it up easily.
Lets say JS's user-base is pretty huge in relation to other languages (which is not an argument for JS). The stats show that a lot of languages transcompile to javascript, so I would indicate a real need for such projects, otherwise there would probably just exist a few as fun/proof-of-concept-projects.
Similar situation for C/C++ (maybe due to lack of high-level features) and Java (due to lack of practical features).
On the other hand: languages that only have a few or no transcompilers that compile to them, does not mean, they are better useable. There could be other things that make writing transcompilers very hard.
This is neither an argument against JavaScript nor was it indended as one, just a personal observation from a long-time JavaScript programmer.