News for hackers. Stuff that matters.

A comment on Chrome treats DELETE requests as GET and caches them. Parent comment

Re:Chrome treats DELETE requests as GET and caches them by masklinn on Monday July 30, 2012 @03:03PM (#4314072)
> 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?

[ Parent | on HN ]
Re:Chrome treats DELETE requests as GET and caches them by wickedchicken on Monday July 30, 2012 @04:25PM (#4314495)
From the dev channel page[1]:

"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."

[1] http://www.chromium.org/getting-involved/dev-channel/

[ Parent | on HN ]
Re:Chrome treats DELETE requests as GET and caches them by masklinn on Monday July 30, 2012 @04:37PM (#4314546)
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.
[ Parent | on HN ]
Re:Chrome treats DELETE requests as GET and caches them by cwp on Tuesday July 31, 2012 @02:31AM (#4316011)
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.
[ Parent | on HN ]