> And if that weren’t enough to make you curious, Google didn’t just take WebKit’s Rending Engine and call it Chrome…
They didn't rebrand WebKit, they wrote a ton of code on top. This sounds like an unfair dismissal of Google's efforts.
> they created a new JavaScript Engine known as V8. This new JavaScript engine is perhaps the fastest engine available
Mostly true, but it depends on the benchmark of course.
> and Google chose to add engineering complexity by making it standalone/embeddable; incidentally making projects like NodeJS possible.
Not at all true. The JS engine in WebKit, JavaScriptCore, is also embeddable and used in various places (for example, Seed in GNOME). Ditto SpiderMonkey.
> The engineering energy that went into creating the V8 Engine Is no small matter, as it was written entirely in C++ and designed to convert JavaScript to machine code to increase speed.
True, but all JS engines I am aware of are written in C++ and compile to machine code (and they did so from around when V8 launched, in the case of JavaScriptCore and SpiderMonkey).