ARM chips have an instruction with JavaScript in the name
11–20 of 312 posts
Re: ARM chips have an instruction with JavaScript in the name
#12I mean, if float-to-integer performance is so critical, why was this not fixed a long time ago in the language? What am I missing?
Re: ARM chips have an instruction with JavaScript in the name
#13FTA: > Which is odd, because you don't expect to see JavaScript so close to the bare metal. This seems to ignore all the work done on server-side javascript with projects such as node.js and deno, as well as the fact that cloud service providers such as AWS have been developing their own ARM-based servers.
No it doesn’t, it’s still surprising to see a CPU instruction added specifically to cater for such a high level language like JS. It does totally makes sense though, given the importance of JS and it’s common use in mobiles.
Re: ARM chips have an instruction with JavaScript in the name
#14Re: ARM chips have an instruction with JavaScript in the name
#15So it was easier to add an instruction in silicon to cater for an ill-designed programming language, than to change the language itself? I mean, if float-to-integer performance is so critical, why was this not fixed a long time ago in the language ? What am I missing?
Re: ARM chips have an instruction with JavaScript in the name
#16My guess is that this is what JIT people asked for.
Re: ARM chips have an instruction with JavaScript in the name
#17So it was easier to add an instruction in silicon to cater for an ill-designed programming language, than to change the language itself? I mean, if float-to-integer performance is so critical, why was this not fixed a long time ago in the language ? What am I missing?
Technically someone can just make a better VM engine for JavaScript to execute inside of, but whatever I guess they decided this would be easier.
Re: ARM chips have an instruction with JavaScript in the name
#18Re: ARM chips have an instruction with JavaScript in the name
#19But I do think one day (might take a while) JS will no longer be the obvious choice for front-end browser development.