News for hackers. Stuff that matters.

gonchuki

add to that list that the Chrome dev tools don't display errors in red in the network tab. A 200 next to a 404 is nearly to impossible to distinguish at first sight (basically, if you are looking at the name of the file, you are not looking at the response code at the same time.)

Every time I use the dev tools I find them lacking a lot of UI/UX details that Firebug had there forever.

Being unable to quickly switch between the CSS and Layout/Metrics view is another major downer. Tabs beat scrolling, always.

Chrome updates also result in JavaScript breakage.

File/Blob API is an example that, while being experimental and a moving target, happened on the background and broke from one launch of the browser to the other without the dev knowing what the heck was going on.

Same breakage happened from Firefox 4 to 5, but at least the end user (the dev in this case) knows that something important happened and might be related to that. This is key.

Function.prototype.apply.apply(console.log, [console, arguments]);

Works both on IE9 broken console.log, and regular console.log from other vendors. Same hack as using Array.prototype.slice to convert arguments into a real array.