Re:Apple's follow-up to M1 chip goes into mass production fo...
by heipei on Tuesday April 27, 2021 @03:55PM
(#26960690)
I'm a self-taught JavaScript developer (front- and back-end) and I would love to read such a blog post. I mostly use language features for their expressiveness (map, filter, forEach) and rarely think about their performance implication unless there is reason to believe some piece of code is in a performance-critical path. However with a guide I might reconsider some scenarios where I'd be willing to give up expressiveness for performance.
[ Parent
| on HN ]
Re:Apple's follow-up to M1 chip goes into mass production fo...
by inDigiNeous on Wednesday April 28, 2021 @04:32AM
(#26967080)
Thanks for the encouragement. I will look into this more and write a blog post about, it is actually something I wanted to do for some time now, I'll make sure to post it to HN also and report what we have found ..
We have been developing this application since 2011 already, and I also develop in C++ and 3D graphics, so performance has been something I've had to think.
But yeah, there are many guides on what to avoid in JS already, how to optimize for speed and memory. But it is not definitely an easy thing to realize, as it's not inherently visible what can be slow and what not. Most blog posts at this time talk about how to optimize for the V8, and I'm not really interested in that so much, as it can be taunting to try to understand how V8 works for example.
Re:Apple's follow-up to M1 chip goes into mass production fo...
by greggman3 on Tuesday April 27, 2021 @10:11PM
(#26964639)
A blog post would be nice. You can also test