After all the recent drama in the Node.js community, which has been on-going for a long time actually, I was almost tempted to believe that a lot of this is really because problems deeply rooted within the american society leak into the (open source) tech community. And to a certain extent that’s probably true. But only to a certain extent. There’s more about the broader tech community that makes it an extremely hostile environment, without being influenced (directly) by the american society. A lot more than that.
In this article (originally published on ponyfoo.com), we’ll discuss how
Object.prototype.toString() performs in the V8 engine, why it’s important, how it changed with the introduction of ES2015 symbols, and how the baseline performance can be improved by up to 6x (based on findings from Mozilla engineers).
In the past couple of days there’s been lots of discussions and ramblings around the so-called
and what it means for the tech industry, and maybe the world as a whole. I strongly and wholeheartedly
disagree with what’s being said in that document, and I realize that not stating this publicly doesn’t
help anyone! I don’t believe that inherent psychological or biological differences may explain why we don’t
see equal representation of women in tech and leadership.
Following up on part one of this series last week, here’s another
for more than four years). This week we’re going to look into an optimization called Function Context Specialization,
The name is a bit misleading. What it essentially does is to allow TurboFan to constant-fold certain values when
generating optimized code, and it does that by specializing the generated machine code for a function to its surrounding
context (which is V8 speak for the runtime representation of scope).