4 ms·

>at the moment tons of web-developers are targeting Chrome only. I'm a web developer and, in my 11 years of doing this, the only people I've ever seen do that

>at the moment tons of web-developers are targeting Chrome only. I'm a web developer and, in my 11 years of doing this, the only people I've ever seen do that are those experimenting with a new feature that only works in Chrome or rank amateurs. Knowledgeable web developers write code to standards, not browsers.

kuschku 11y ago
WhatsApp Web? Google Inbox? Very good examples that were unnecessarily "only works in Chrome". Changing your User agent also allowed you to use both in Firefox.
- Moter8 11y ago
  Both of these did not allow other browser when they were released, today both work fine on FF. Details on why Inbox wasn't available at first are available in this thread: https://news.ycombinator.com/item?id=8606879 https://news.ycombinator.com/item?id=8606879
  - kuschku 11y ago
    And still, for a few months two recent web products were limited to one browser, which is used by a minority, and is in many countries not even the largest minority.
  - gsnedders 11y ago
    And still rely on UA hackery in Opera, which given in principle it relies on the same version of the Chromium Content API as the current Chrome release, it's fairly obvious it's a business decision and not a technical one.
gsnedders 11y ago
> Knowledgeable web developers write code to standards, not browsers. Really? I certainly don't try and work out how the spec says the document should render — I trust if browsers interoperably render the document the same, that's what the spec says. And I'm not someone scared of specs, having contributed to them for years and worked on browsers for years.
- gopowerranger 11y ago
  Yes, really. You're saying the same thing I am, Geoffrey. Sort of. I expect browsers to render the same way as the spec says it should. I then verify in each browser. When they don't, I adjust, but I never write code, only test in ... Opera ..., and expect it to be identical everywhere. I don't only read the ... Opera ... blogs and specs and expect it all to work the same all the time.
toast0 11y ago
> Knowledgeable web developers write code to standards, not browsers Users are running browsers, not standards. Writing to standards only works once the standard is widely distributed and implemented.
- gopowerranger 11y ago
  Of course, you must wait for implementation. As I said in another post, you must still test in the browsers to make sure they work but to only use a property available in one browser, or to write code and test in only one browser (the subject of this thread), is a fault of the developer and an error of omission.

kuschku 11y ago

WhatsApp Web? Google Inbox? Very good examples that were unnecessarily "only works in Chrome". Changing your User agent also allowed you to use both in Firefox.

Moter8 11y ago
Both of these did not allow other browser when they were released, today both work fine on FF. Details on why Inbox wasn't available at first are available in this thread: https://news.ycombinator.com/item?id=8606879 https://news.ycombinator.com/item?id=8606879
- kuschku 11y ago
  And still, for a few months two recent web products were limited to one browser, which is used by a minority, and is in many countries not even the largest minority.
- gsnedders 11y ago
  And still rely on UA hackery in Opera, which given in principle it relies on the same version of the Chromium Content API as the current Chrome release, it's fairly obvious it's a business decision and not a technical one.

gsnedders 11y ago

> Knowledgeable web developers write code to standards, not browsers. Really? I certainly don't try and work out how the spec says the document should render — I trust if browsers interoperably render the document the same, that's what the spec says. And I'm not someone scared of specs, having contributed to them for years and worked on browsers for years.

gopowerranger 11y ago
Yes, really. You're saying the same thing I am, Geoffrey. Sort of. I expect browsers to render the same way as the spec says it should. I then verify in each browser. When they don't, I adjust, but I never write code, only test in ... Opera ..., and expect it to be identical everywhere. I don't only read the ... Opera ... blogs and specs and expect it all to work the same all the time.

toast0 11y ago

> Knowledgeable web developers write code to standards, not browsers Users are running browsers, not standards. Writing to standards only works once the standard is widely distributed and implemented.

gopowerranger 11y ago
Of course, you must wait for implementation. As I said in another post, you must still test in the browsers to make sure they work but to only use a property available in one browser, or to write code and test in only one browser (the subject of this thread), is a fault of the developer and an error of omission.