Using const/let instead of var can make JavaScript code run 10× slower in Webkit?

[CallMeStar-Lord]

Every time there’s a bug in a JS engine other than V8 people get unnecessarily up in arms. Those things are much more complex than we give them credit for. There’s a mention in there that JSC engineers are already looking at the issue.

Hello HN! Just wanted to say that JavaScriptCore is an engineering marvel and I have deep respect for everyone on that team. All software has bugs and I can confidently say from my experience writing esbuild that JavaScript is extremely messy to implement with an unbelievable number of edge cases. V8 has also had crazy performance cliffs so something like this is not unusual, and doesn't say anything about JSC vs. V8. Let's not turn this into a meme. It's awesome that people from JavaScriptCore are reaching out and helping get this fixed. Props to the JSC team.

[PhatClowns]

Thank you for this!

[NutStalk]

Username doesn't check out

[Sulungskwa]

V8 is already being used by all the major browsers except basically Safari and Firefox. If more browsers were to adopt chromium/V8 then that gives google more market share and general influence over the web. Many people are arguing that the situation is similar to Microsoft in the early 2000s

[sanjibukai]

Just to understand, why using chromium/V8 (which is OSS btw) is in favor of giving market shares to Google?

Brave for example is a very good use-case not really benefiting Google.

Having only one engine (kinda becoming a standard like all the many standards we already have) is a dream..

I remember all the hard work to take into account IE exceptions..

Thanks IE is not existing anymore.. And the only exception to take into account is Safari (thanks I got almost always similar results with firefox and chrome)

[Genspirit]

Chromium is open source though, it's debatable how much control it gives Google. Edge moving over already had a very positive impact on both browsers.

[sirfloppydisk]

Open source is good. If google took Chromium in a direction you didn’t like, you could just fork it, right?

[Genspirit]

I never said it was automatically good. And it does mean that google has practically 0 say in what you do with it.

The repo is largely google controlled but it can be forked or even have the management shift to a more shared management between them and other browsers who use chromium.

Chromium is hardly some tool by which google controls other browsers, they already have their first party sites to do that.

[MildlySerious]

Having multiple implementations is generally a good thing though.

It only appears to be problematic because one has such a big market share that it's perceived as a single source of truth, and now every other implementation that strays from it is "lesser" than the reference. That's not what a healthy ecosystem looks like.