3 ms·
I agree. All the things we could be doing and we're making CPU improvements for the flaming pile of hot trash that is JS? Why?
by FridgeSeal 8y ago
I agree.
All the things we could be doing and we're making CPU improvements for the flaming pile of hot trash that is JS? Why?
- wild_preference 8y agoWe? You had zero stake in the matter. How many homeless people did you help out today? None while you were writing that comment.
- dang 8y agoWe've already asked you to stop being nasty in HN comments. Continuing to do that will get you banned, so please stop. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- olliej 8y agoFloating point to integer conversion instructions already exist - this changes sentinel value and rounding conversion behavior only, which is a minor conditional change at the end of the existing conversion pipeline. I would expect that the only actual change here is the final rounding and register store which is not significant. Those are already things that have to happen.
- koffiezet 8y agoMaybe because it's a considerable part of the code that CPU's are executing these days? Certainly UI stuff that should be responsive and fast. Even many 'native' apps, mobile or desktop (electron) are written in javascript, and how much of your time do you spend in your browser or electron apps every day? Think vscode, atom, Spotify, Slack, facebook, reddit, twitter, ...