I don't think your anger about multiple assignment is valid.
I also use the Dev channel regularly, but I don't think it's fair to expect it to meet a high bar of quality. Typically issues are corrected within a few days.
> I don't think your anger about multiple assignment is valid.
He didn't express any anger about it, he just noted that it was broken. The anger he expresses is about Chrome's insanely aggressive caching (and every web dev I know agrees with that, even IE's caching was less over-the-top than Chrome's).
I'm taking his note on multiple assignment more as a supplementary piece of evidence re. Chrome's quality control: how can you break something as basic as multiple assignments and get that pushed to a build?
"While this build does get tested, it is still subject to bugs, as we want people to see what's new as soon as possible" and "Remember, Dev channel browsers and Canary builds may still crash frequently."
I know what the channel page says and what the dev channel is about, my issue is that multiple assignment is not a complex or advanced feature, which means either it's not tested or Chrome's devs don't even bother running any test suite before pushing changes.
What makes you think assignment is simple? V8 is a multi-stage, dynamically optimizing just-in-time compiler. That's complex and advanced, pretty much by definition.
As masklinn pointed out earlier, it's frustration with the lack of quality control rather than anger. While I'm certain that the multiple assignment bug will be fixed (if it isn't already, of course), I simply brought it out to illustrate a point: The Chrome(ium)? team needs to invest a bit more time in quality control, and less time on trying to make the web "faster" by taking shortcuts around well-established practices and specs.
I wouldn't be surprised if the multiple assignment bug was caused by some sort of speed-related optimization.
He didn't express any anger about it, he just noted that it was broken. The anger he expresses is about Chrome's insanely aggressive caching (and every web dev I know agrees with that, even IE's caching was less over-the-top than Chrome's).
I'm taking his note on multiple assignment more as a supplementary piece of evidence re. Chrome's quality control: how can you break something as basic as multiple assignments and get that pushed to a build?