⚡️ The Cost Of JavaScript (2017 - 2023)

Rant Time
I don't know when it started, but frontend development began to compete on "high-end knowledge," constantly bringing up browser underlying principles and how V8 works. It's not that these topics are useless, but the trend suggests that if you don't understand these things, you can't even build a simple webpage.
In my work, I've collaborated with kernel teams and VM teams and consulted them about these related issues. Their attitude is very clear: when facing large-scale engineering projects with tens of millions of lines of code, even as professionals, they don't understand everything. If you happen to meet someone who truly understands everything, they definitely wouldn't be doing frontend work. This makes the "eight-part essay" battles between interviewers and candidates seem ridiculous.
So if you really encounter scenarios that require learning related knowledge, or you're simply personally interested in understanding the principles and details, what's the best approach? It's simple: directly read the blogs or talks from relevant teams or core developers. This is first-hand information, aside from the source code itself, and the quality is much higher than those second-hand dealers.




