progers7

You have 3 comments in this thread stating that this wasn't reviewed correctly. It was, you're just looking at the wrong link in their bugtracker: http://trac.webkit.org/changeset/194667 "Reviewed by Tim Horton."

This was reviewed properly, you just have to click the actual commit: http://trac.webkit.org/changeset/194667 "Reviewed by Tim Horton."

The response time here might not be great, but the patch author and reviewer are both experts in this area. I wouldn't consider this patch evidence of declining software quality--it's just a simple bug.

At the bottom of the article Bruce mentions the slashdot comments went downhill. This is the first time I've visited slashdot in years and I'm sad to see an old haunt turned so bad. The equivalent reddit thread is significantly more interesting, positive, and hacker-ish: https://tech.slashdot.org/story/16/03/25/141256/chromium-bei... https://www.reddit.com/r/programming/comments/4bvswj/compile...

If you're interested in common handheld calculators, you might enjoy this light-hearted series by Matt Parker titled "Calculator Unboxing": https://www.youtube.com/watch?v=8Nzi1h2m7pE&list=PLt5AfwLFPx...

I don't think we want to be a community that shares content like this.

Another fun part of Chinese is that most characters are monosyllabic. This makes numbers easy to remember and, on average, Chinese speakers can remember a few more random digits than English speakers can.

It looks like the video is just reversed.

Opera is far from a "chromium skin maker". In addition to features like autosizing modes for mobile, Opera developers are heavily involved in specs as well as the entire Chromium stack:

https://blink.lc/blink/log/?qt=author&q=opera

https://blink.lc/chromium/log/?qt=author&q=opera

They have an incredible team.

Yeah, it will ship to Chrome users. The effect will be a console warning that SMIL will be removed. You should start seeing this in Canary in the next 1-2 days.

Excellent points.

SMIL usage is high so it's just being deprecated in blink to get the word out, but not removed just yet. If you're planning to ship both web animations and SMIL, I hope we can get everything you need in web animations before SMIL is finally removed. If you have specific examples you can share, please do post on the smil blink-dev thread.

SMIL support is rough in the old android browser. I suspect using the web animations polyfill will be a safer path than trying to support the SMIL edge cases.

SMIL does not work in IE and is fairly broken in old Android browsers. It's not a viable solution anywhere, today.

I'm sympathetic to hobbyists and SMIL enthusiasts who are losing out here, but removing SMIL isn't changing what common sites can deploy to users today.

This is the crux: "The goal of having Web Animations to take place of SMIL makes sense..."

Web animations are the modern approach forward. They are actively being developed in all browsers and work in both html and css. You can start developing this today using the polyfill: https://github.com/web-animations/web-animations-js

This is an excellent summary of the current state of things.

tl;dr: don't use SMIL.

Microsoft has (correctly, I think) publicly stated[1] that they do not intend to support SMIL/<animate>. It's best for our platform to double-down on the alternatives: javascript, css, and web animations. Dropping SMIL is painful but it's the only way to get to true interop and a consistent web platform.

[1] https://groups.google.com/a/chromium.org/d/msg/blink-dev/5o0...

If you enjoyed this story, I recommend "The Martian" by Andy Weir. It reads like it was written by an engineer (it was) and is a thoroughly researched, fun read.

For the curious, Oilpan is a tracing garbage collector inside Chromium. The original design docs are at [1].

[1] https://docs.google.com/document/d/1y7_0ni0E_kxvrah-QtnreMlz...

SMIL is not perfectly fluid. SMIL is not inherently hardware accelerated. SMIL animations are slower than the same animations driven from JS in all major browsers except IE which doesn't support SMIL but does support JS. As the OP showed, JS animations are the way to go for SVG.

Until they forked Blink, Google was the top contributor to WebKit: http://blog.bitergia.com/2013/02/06/report-on-the-activity-o...

Here's the description from chromestatus: https://www.chromestatus.com/features/5169444246519808

The keynote was recorded and will be up at some point.

Excellent points, thank you.

The players graph is tough. There are many 0 entries which means a true log scale is out. A linear graph ends up being dominated by Apple and Google so you can't really see the other organizations. I should call out the scale more explicitly though. Btw, the scale is technically a sqrt scale: https://github.com/mbostock/d3/wiki/Quantitative-Scales#sqrt

This idea is being considered: https://docs.google.com/a/google.com/presentation/d/1XvZdAF2...

This is a good benchmark for stressing rendering, layout, and style. We should be testing the real frameworks being used on the web and Speedometer is as good as any I have seen. Unlike IE's testdrive, Speedometer's source does not look like it was written by cherry picking examples that perform well in a specific browser.

I'm skeptical of a minor point though: synthetic events do not accurately simulate end-user responsiveness, especially when it comes to frame and event scheduling that occurs in a different process. There's a difference between simulated and real events even on the renderer side (see: http://trac.webkit.org/changeset/164871).

Opera will be using Chromium+Blink under the hood.