Why do we allow loosey-goosey things to exist in code? Because the emphasis for software development has shifted somewhat from correctness, infinitesimal detailed knowledge/attention to detail, and memory efficiency to productivity, ease of programming, and rapid application development. It’s not like programmers can’t do lots of really stupid things in C/C++, but in most cases these strongly typed languages force the programmer to advertise their intention up-front, in the code (explicit casting) for everyone to see (and question) rather than quietly hiding what could be fatal flaws that arise when type inference goes wrong. People who came into programming via C based languages and especially C++ with its “strong typing,” which is the polar opposite of type inference, often see languages like JavaScript as being a little too loosey-goosey or weak in the knees because they allow things that would be punished in C++ to be quietly ignored in these weaker languages, like JavaScript. I wouldn’t point any fingers at Google here because the root cause of this specific issue is really tied to the “type inference” feature (or flaw depending on your viewpoint) of JavaScript. However, it sounds like they patched the more generic V8 issue earlier.

This is actually more than just a browser concern since it involves the V8 JavaScript engine which is the basis for Node.js, the underlying technology used in Electron apps, like Visual Studio Code.

Chrome for macos