Safari 6 is useless for development and has made me move to chrome for anything more than console.log.
They're losing.
Firefox + Firebug pulled webdevs away from IE like honey. Chrome is doing the same.
They're losing.
Firefox + Firebug pulled webdevs away from IE like honey. Chrome is doing the same.
These are in no particular order. The developer tools crashed several times (pre-release and all), and I don't have the time to keep going through all the other places.
I'll make this clear up front, as I mentioned it below, but want to make it clear:
"I'll admit there is more their than I originally thought, but still missing things I use daily."
Here are my notes:
* Lack of effective Network Tab
* This can be found in Timelines > Network Requests
* Basic problem is the Timeline is now trying to do two things at once, both with different reasons
* Browsing network requests is cumbersome at best.
* Cannot switch between headers and bodies
* No way to see raw headers
* No way to open request
* Copy row is pointless
* This is such an odd miss...
* Back button is not consistent
* From full frame console, it sends you back to the network requests
* From source, it sends you "back" to another source page (?)
* I see no way to define what is being repainted/drawn for each record of Layout & Rendering
* Consoles in other parts of don't seem to function at (at least, the response is put into the Console tab, and not in the console area that opens up).
* No way to edit JS
* No way to edit Breakpoints without specifically opening up the Debugger
* CSS editing is non-obvious
* It's also less than helpful when completion
* No easy mechanism to edit existing rules
* Debugging doesn't let you mouseover and see this (?)
* Cannot execute JS in scope while debugging
* Debugging just seems awfully buggy at the moment, it's a pre-release, but makes it hard to put through it's paces.
All together, the dev tools don't seem fluid. I'll admit there is more their than I originally thought, but still missing things I use daily. More so, nothing seems put together that makes sense. You can argue that it's because I'm used to Chrome Dev Tools, but I can move from Chrome to Firefox with relative ease, but debugging inside Safari is still painful. Couple that with the bugs, and it really makes it hard to give it a proper run through. For example, the debugger right now is set to break on all uncaught exceptions. Running this on http://www.apple.com/osx/preview/#ibooks, it stops on ac_retina.js:20, but it doesn't offer any information in the debugger, or in the console.
I get a feeling this was designed by people copying from Xcode, rather than people working with web developers. Tools I'm used to working with don't work, or work in a different way that is simply not useful.
I didn't spend much time digging through more of the timeline stuff, and as I mentioned, the debugger was cumbersome to use.
Heck, even the Resources tab was painful. I mean, the page is loaded, yet somehow clicking on scripts to view put them in a constant loading state.
Again, it's a pre-release, but it's all I have.