Also one could argue that if Apple did not invest so much in WebKit then chrome would have had a harder time achieving its current usage and would probably be a very different browser than what it is today.
My 2cents
Also one could argue that if Apple did not invest so much in WebKit then chrome would have had a harder time achieving its current usage and would probably be a very different browser than what it is today.
My 2cents
That's really grasping for straws. All modern browsers almost fully support ES6 features. Tail optimization are more controversial because they can actually lead to a performance decrease in some cases.
Far more important are things like custom elements and service workers on which Safari is lagging behind.
How exactly can the tail-call elimination optimization decrease performance?
Sounds more like an implementation problem.
[0]: https://github.com/tc39/proposal-ptc-syntax#performance
How exactly does anyone think that v8 doing something badly, is proof that something cannot be done well?
However, you're asking me to prove a negative. I've given arguments, which apparently you find unconvincing. The people you are disagreeing with (not I) are responsible about 85% of the JavaScript engines on the Internet, an incredibly competitive space with billions in funding. I submit that they are probably neither incompetent nor lazy. (Evidence for "not lazy": the V8 team implemented it and turned it off.) If you are convinced that it's a (presumably fixable) implementation problem, I'm sure they'd love a patch or at least something more actionable than your insistence that they're doing it wrong.
Sure, but at the risk of repeating myself: That sounds like an implementation problem.
> I've heard no argument why the PTC mode should be intrinsically faster than the non-PTC mode
There's a simple one: Hitting the stack less means you hit less memory.
> The people you are disagreeing with (not I) are responsible about 85% of the JavaScript engines on the Internet, an incredibly competitive space with billions in funding. ... I'm sure they'd love a patch
Happy to oblige. I'll implement TCO on V8 for a billion dollars in a way that beats these benchmarks.
> However, you're asking me to prove a negative.
And you're making straw men instead: At the beginning of your response, it's not even clear you read my complaint, but at the end, it's quite clear.
The simple answer would probably have been "yes, it's about an implementation, but it remains unknown where else we can go", but instead you doubled down...
> there's a simple one: Hitting the stack less means you hit less memory.
But I explicitly acknowledge this in my comment:
> (yes; you elide a stack frame at the cost of a whole-function analysis pass -- heuristically, "stack frame" isn't the expensive one of the two)
(Completely ignoring that there are already plenty of optimizations where a compliant interpreter may avoid the stack frame already anyway, so it's not even true that PTC must be faster for that reason.)
You keep picking on V8, but remember that there is so far only 1 major JS implementation that managed to do this without impact. It would seem that it's more probable that it's the other way around: it's an implementation detail that JSC had it easy.
> And you're making straw men instead: At the beginning of your response, it's not even clear you read my complaint, but at the end, it's quite clear.
I'd be happy to address this point, but I genuinely don't know which straw man I've supposedly built.
> > there's a simple one: Hitting the stack less means you hit less memory.
> But I explicitly acknowledge this in my comment!
Not really sure what your point is. If you agree that's an argument as to why tail-call elimination should be intrinsically faster, I'm not sure why you'd say it isn't.
I can't shake this feeling you think you're having a very different argument than I am.
> remember that there is so far only 1 major JS implementation that managed to do this without impact.
Which for some reason you think means this isn't an implementation issue.
I did not put an exclamation mark there, but a colon, pointing out the specific reason why PTC can end up slower.
Is there even a consideration on how these new features become just another tool to spy on people?
To me it is far more important that Apple take its time letting these APIs mature and being reviewed for security and performance than blindly implementing anything that Google demands.
This is deceptive. They purposefully do not support critical features that other browsers do support. As a developer, if there's one browser that consistently gives me headaches, it is Safari.
https://developer.mozilla.org/en-US/docs/Web/API/FormData/ge...
Brave seems promising but doesn't yet have extensions.
> Also one could argue that if Apple did not invest so much in WebKit then chrome would have had a harder time achieving its current usage and would probably be a very different browser than what it is today.
The same can be said on an even larger scale about microsoft and IE 5 and 6; that doesn't mean in anyway that years later they were not a pain stopping the web from going forward. In other word, I don't see how that has any impact on the conversation at end (neither for or against the point made).
EDIT: Not sure why the downvotes.
Apple invested a lot into Safari (and thus webkit which lead to chrome). Doesn't change in any way if Safari is or isn't holding the web back currently, which is why I say it's irrelevant to paren't countering argument.
And in fact, we have a previous examples since we lived the same scenario with Microsoft who invested a lot into IE 5/6 (and leading into DHTML, XMLHttpRequest, ...), which then definitely hold the web back.
This is, literally, the same argument. I don't see how I can be downvoted for stating that obvious fact unless you think that IE 6 didn't hold the web back after a while.
Thread says "Safari is holding the web back". Parents answers "Safari created the tools that lead to big parts of the modern web".
My answer is: so did IE 5/6. That doesn't mean after a while and for a long time they weren't holding the web back, it's a side fact that has no relevance.