News for hackers. Stuff that matters.

A comment on Using const/let instead of var can make JavaScript code run 10× slower in Webkit. Parent comment

Re:Using const/let instead of var can make JavaScript code r... by coddle-hark on Wednesday October 21, 2020 @01:00AM (#24844873)
Does it? It’s not like people are constantly running comparison benchmarks of var/const/let between browsers.
[ Parent | on HN ]
Re:Using const/let instead of var can make JavaScript code r... by brundolf on Wednesday October 21, 2020 @01:06AM (#24844901)
If every large JS app on Safari is 10x slower than it is on Chrome, and the user base of Safari has been dealing with that since who-knows-when, and no developer noticed because they're all testing on Chrome, that's a problem.
[ Parent | on HN ]
Re:Using const/let instead of var can make JavaScript code r... by asdfasgasdgasdg on Wednesday October 21, 2020 @01:48AM (#24845097)
Yeah. A problem Safari's developers should address. Apple is not a wee baby company that lacks the resources to keep up with Chrome in any dimension.
[ Parent | on HN ]
Re:Using const/let instead of var can make JavaScript code r... by mattnewton on Wednesday October 21, 2020 @01:23AM (#24844980)
Or they are all compiling their JavaScript to legacy JavaScript specs for WebKit.
[ Parent | on HN ]
Re:Using const/let instead of var can make JavaScript code r... by microcolonel on Wednesday October 21, 2020 @01:16AM (#24844942)
It's Apple's problem to solve though, I mean, outside of developers writing code that's more efficient to begin with so it doesn't really matter when it's 10x slower, but they should probably be doing that anyway.
[ Parent | on HN ]