3 ms·

"Modern Web Development" does not mean "Works in Webkit", and it does a disservice to future/novice developers to reinforce that notion. What's dominant now was

by potch 14y ago

"Modern Web Development" does not mean "Works in Webkit", and it does a disservice to future/novice developers to reinforce that notion. What's dominant now was not in the not-too-distant past, and may not be in the not-too-distant future.

tomdale 14y ago
When Mozilla ships better developer tools than Chrome, I'm sure there will be posts just like this one. The fact that developers prefer Chrome is not a failing of developers; it's a failing of Mozilla to provide compelling tools.
- karlshea 14y ago
  Firebug is pretty close, but you're right.
- agumonkey 14y ago
  I don't know much, but I don't understand Mozilla's effort to reimplement firebug natively. Right now their solution seems unusable and far beyond firebug.
  - mhansen 14y ago
    They're reimplementing it because Firebug is an unmaintained mess.
    - sirclueless 14y ago
      Mozilla is just in an unfortunate situation, where Firebug's ground-breaking functionality was duplicated as a first-party feature of other browsers. So now as Chrome Inspector continues to add more and more deep functionality, Firebug is hampered both by being third party code and subsisting on Firefox's addon API.
jtaby 14y ago
I acknowledge WebKit's monopoly on the mobile landscape today, I make no claim whether it's a good thing or a bad thing, that argument would distract from the reality that if you want to make a mobile web app work well, you need to build it on webkit and debug it on webkit
- tagawa 14y ago
  ... and test it cross-browser. WebKit has a majority on mobile (around 75%) but not a monopoly. (Source: http://gs.statcounter.com/#mobile_browser-ww-monthly-201103-201203 http://gs.statcounter.com/#mobile_browser-ww-monthly-201103-... )
  - tomjen3 14y ago
    But if you do your part to break it in other browsers you can help make your job easier and make it easier to innovate in the future.
deleted 14y ago
[deleted]
pavpanchekha 14y ago
You misunderstand. This was how modern web applications are written. I know very few people who write modern web apps but do not use Chrome for it. The reason is that Webkit has the best tools. Cross-browser independence isn't the point, since when I'm developing I'm using only one set of tools.

by potch 14y ago

tomdale 14y ago

When Mozilla ships better developer tools than Chrome, I'm sure there will be posts just like this one. The fact that developers prefer Chrome is not a failing of developers; it's a failing of Mozilla to provide compelling tools.

karlshea 14y ago
Firebug is pretty close, but you're right.
agumonkey 14y ago
I don't know much, but I don't understand Mozilla's effort to reimplement firebug natively. Right now their solution seems unusable and far beyond firebug.
- mhansen 14y ago
  They're reimplementing it because Firebug is an unmaintained mess.
  - sirclueless 14y ago
    Mozilla is just in an unfortunate situation, where Firebug's ground-breaking functionality was duplicated as a first-party feature of other browsers. So now as Chrome Inspector continues to add more and more deep functionality, Firebug is hampered both by being third party code and subsisting on Firefox's addon API.

jtaby 14y ago

I acknowledge WebKit's monopoly on the mobile landscape today, I make no claim whether it's a good thing or a bad thing, that argument would distract from the reality that if you want to make a mobile web app work well, you need to build it on webkit and debug it on webkit

tagawa 14y ago
... and test it cross-browser. WebKit has a majority on mobile (around 75%) but not a monopoly. (Source: http://gs.statcounter.com/#mobile_browser-ww-monthly-201103-201203 http://gs.statcounter.com/#mobile_browser-ww-monthly-201103-... )
- tomjen3 14y ago
  But if you do your part to break it in other browsers you can help make your job easier and make it easier to innovate in the future.

deleted 14y ago

[deleted]

pavpanchekha 14y ago

You misunderstand. This was how modern web applications are written. I know very few people who write modern web apps but do not use Chrome for it. The reason is that Webkit has the best tools. Cross-browser independence isn't the point, since when I'm developing I'm using only one set of tools.