Re:Chrome treats DELETE requests as GET and caches them
by jperras on Monday July 30, 2012 @05:07PM
(#4314691)
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.
I wouldn't be surprised if the multiple assignment bug was caused by some sort of speed-related optimization.