3 ms·
> the computing world finally moves on from C. The computing world has moved on from C, mostly. To Javascript. The main impact of that seems to be a couple of
by pjc50 5y ago
> the computing world finally moves on from C.
The computing world has moved on from C, mostly. To Javascript. The main impact of that seems to be a couple of numeric conversion instructions on ARM?
(OK, not entirely fair: the computationally heavy stuff has moved away to GPUs. But if you ask the question for every button press a human makes on a computer where the dominant execution time is you might have some interesting answers, and for a lot of them it is going to be JITted Javascript)
I think it's fairly clear that for general purposes VLIW is not what either the programmer or the compiler writer wants to deal with. In-order execution is such a convenient mental model that people are willing to accept any tricks that keep it working.
- IshKebab 5y agoNonsense. A ton of code is still written in C/C++. What do you think runs all of that Javascript? The C world isn't moving to Javascript, it's moving to Rust, Zig and Go.
- cto_of_antifa 5y agoWhat the heck is zig
- the_only_law 5y agoKinda veering a bit off topic, but I’ve always seen go marketed as a systems languages alongside C, Rust, etc., but in practice I’ve only really ever seen it used to developer high level web applications.
- sophacles 5y agoDocker and k8s, flannel, etc are all written in go and something I'd consider "systems programming" - I mean they have to do some pretty complex coordination w/ the kernel to do thier work.
- kmeisthax 5y agoThe numeric conversion instructions you're thinking of are branded "JavaScript", but actually exist to emulate Intel x86 floating-point behavior. It just so happens that the ECMA specs call for said behavior because existing code relied upon it.