Re:Firebug 2.0
by andrethegiant on Tuesday June 10, 2014 @01:25PM
(#7873956)
I'm always surprised when I read comments about how the Firefox devtools offer the best developer experience. Every single one of these new features (except searching the dom via CSS selectors or regex) have been available in Safari's Web Inspector for OS X for at least a year. Plus, I think the UI is more thought out and easy to use in Safari. Can someone explain what Safari's Web Inspector is lacking?
[ Parent
| on HN ]
Now that Chrome and Safari inspectors have started to diverge significantly I find the Chrome inspector far superior. It just feels like more time has been invested in it.
Only issue I have is the fact it changes more or less every release, leading to a day or so of re-learning how to do certain tasks.
Does Safari support source-maps yet?
Yes, Safari supports source maps (has for a while).
Can someone explain what Safari's Web Inspector is lacking?
It has a platform limitation.
Even as a Mac user, Safari completely has vanished from my radar. Apple seems too slow to adopt the latest web technologies and Safari to me is a completely lackluster browser. It has neither the market share of IE nor the raw speed of Chrome nor the versatility and configurability of Firefox.
Safari does not work on anything but MacOS and iOS, so developing for it requires additional testing.
It doesn't run on PCs.
Re:Firebug 2.0
by TazeTSchnitzel on Wednesday June 11, 2014 @07:47AM
(#7877459)
Which is a shame. Apple should bring back Windows Safari.
Would be good to bring it back to Windows, so that we can test our web sites. However last time when I was using it on Windows it was making my hard drive to make strange noises. I think that it was using my hard disk constantly.