om2

47 ms·

451.
Speedometer: A Benchmark for Web App Responsiveness(webkit.org)
50 points by om2 12y ago|6 comments
452.
by om2 12y ago
I'm confused about how this comment applies. In this controversy, who is it that is failing to understand something, for salary-dependent reasons?
453.
by om2 12y ago
Job losses as the mechanism of inequality would very little nothing to do with Piketty's claims, which are about concentration of wealth at the very top due to intrinsic properties of returns on capital. Piketty's theory doesn&#x2
454.
by om2 12y ago
The post seems like strong evidence that the finding of the paper is wrong, or at least not justified by the study performed. "Hoax" taken literally would imply deliberate malfeasance, and that doesn't seem to be proven
455.
by om2 12y ago
The FT data objections are far from the strongest objections to Pinketty's work. Here are a few criticisms seem much more serious than nitpicking the data: http://www.econ.nyu.edu/user/debraj/Papers/Piket
456.
by om2 12y ago
It can still count as parody even if some people got genuinely confused. Consider that some people get fooled by articles from The Onion.
457.
by om2 12y ago
Google was a valuable contributor. But a lot of Google's commits were not necessarily that high value to non-Chrome ports of WebKit. They had forked code paths for a lot of things (so changes on their side of the #ifdef fork don't
458.
by om2 12y ago
Even then, I'm not sure it's a simple linear relationship. Crankshaft is better on some code, and FTL is better on some code. There's even cases where DFG (plus the tiers below it) does better than Crankshaft. (Talking about
459.
by om2 12y ago
The hypothesis of JSC folks is that it will be able to get very good results without any special case handling for code labeled as asm.js just by having a great general compiler, particularly with more tuning. On the things we profiled, the
460.
by om2 12y ago
V8 has multiple tiers too, so I'm not sure you can express it quite that simply.
461.
by om2 12y ago
In some ways, it's easier to go fast when you don't have to argue over basic strategy or maintain duplicate code paths. Even if you lose some contributors in the process.
462.
by om2 12y ago
Part of this project was building support into LLVM that you would need to build a really great dynamic language JIT. Another key aspect was having lower compilation tiers that don't use LLVM. Using LLVM as a fourth tier works much b
463.
by om2 12y ago
Counterpoints: (1) It requires a pause to compile a bunch of stuff before you even get going. While in our case LLint would have executed it a few times already. (2) Even for asm.js-style code, dynamic profiling info can help you optimize t
464.
by om2 12y ago
You can try it yourself with a WebKit nightly if you want. http://nightly.webkit.org/
465.
by om2 12y ago
JavaScriptCore also has bump-pointer allocation, as mentioned by the post. We don't use it for all things but we think our tradeoff choices are pretty good.
466.
by om2 12y ago
We already get a huge speed boost on asm.js code, without having to special case it. It's likely that LLVM could do even better on it, but at this time we're not sure that a specific hint that it's asm.js would help.
467.
by om2 12y ago
If you care a lot about 99.9999% of web code, as in code found on real webpages, try JSBench < http://jsbench.cs.purdue.edu> . It's the only JS benchmark made from JS found in actual real-world production webpages. Java
468.
by om2 13y ago
I don't check in to WebKit as much as I used to but I probably would not choose to make my own commit messages quite so inside jokey. That being said, we try to have fun on this project.
469.
by om2 13y ago
Many WebKit developers are very actively commenting on the Web Components family of specs. We don't generally comment specifically on future implementation plans though.
470.
by om2 13y ago
Specifically, the references to 60fps, mobile, and 8.8 million lines are all jokes. I hate to explain jokes. But I see a lot of people in the comments trying to read serious deep meaning into these that is just not there.
471.
by om2 13y ago
When and if WebKit implements Shadow DOM, we won't use these vestiges of the old code. Note that this checkin (and the earlier actual removal of the old implementation) are not a commentary on our long-term plans to support it or not
472.
by om2 13y ago
As the Apple person in question, my primary objection isn't about whether I "want it standardized yet". It's more that this hasn't even reached step 0 of the standards process (writing an "editor's draft&q