i) They don't fix the appalling font rendering issues on Windows promptly and as a priority. Most of Google's own web fonts are unusable in production because of this.
I haven't used Windows since about 2000, so I have no comment on this. I will point out that it appears work is in progress: https://code.google.com/p/chro...
ii) They don't follow standard most-recently-used order when ctrl-tab between tabs and they don't see the problem and close any bug report as won't fix.
I disagree with this one. The Chrome tab ordering is better. most-recently-used sucks when you have 20 tabs and have bounced around between them somewhat randomly (as is normal). It makes ctrl-tab completely unpredictable unless you're just jumping back one or two levels. The Chrome way is better.
iii) They start adding animations to html elements you can't restyle with CSS e.g. the zoom ease-in they added to select elements in a recent Chrome.
Got a link to more information? I'm not sure what you're referring to.
There were wide-spread issues on their recent releases. You can only auto-update if you are rock-solid.
Link? I certainly never noticed any issues, but perhaps that's -- again -- because I don't use Windows.
v) They fork from the web-kit project, a once high-point in cross company collaboration for the betterment of the web. Now... beginning of the end.
Nonsense. There is still cross-collaboration between Blink and Webkit, and Google isn't the only company working on Blink.
I also fundamentally disagree with the common /. meme that forks are bad. There is this mistaken notion that having all of the developers interested in a certain space collaborating on one implementation will improve the pace of development, but that view ignores the fact that software engineering isn't like ditch-digging; with software there are definitely diminishing returns on larger and larger collaborative groups, particularly if the software isn't of a sort that lends itself to crisp, well-separated modules. In practice, we tend to find that with sufficiently-important spaces (e.g. web browsers) the ecosystem is better-served by friendly competition among open source projects. That reduces the amount of inter-group communication needed to reach consensus on approaches and therefore increases the speed of iteration. The fact that all are open source means that when one project implements a great new idea the others can see the details of the implementation and more easily incorporate the idea, even if they can't actually use the implementation.
I think the "we should all work on one implementation" theory has basically the same merits as the old Soviet one-gigantic-factory model for production of goods. On the face of it one would think that producing many different designs for one type of product and then building all of them in separate production facilities, distributed through different distribution networks, etc., is very inefficient. One design, one huge factory to maximize economies of scale should be better, right? But history showed that the opposite is true, that a competitive market produces more goods, better goods and does it at a lower cost. The issues in software are different, but at a high level the emergent properties are similar.
vi) And now they are going to spend their time re-implementing a cross-platform widget toolkit.
They already implemented it. It's been used in ChromeOS for a while. My guess is that they've decided it will take less engineer effort to port and maintain Aura than to keep up with Gtk+. I also wouldn't be surprised if a goal isn't to remove some unused cruft from Chrome on platforms (like Windows) that don't tend to have Gtk+ libs lying around. I doubt Chrome uses more than a tiny fraction of the Gtk+ functionality.