Hacker News Reader

> What happened to cross-browser testing, progressive enhancement and other best practices?

It is the responsibility of browser vendors to follow the spec, not of developers.

Otherwise, developers would have to test in 10+ different browsers every time they make a change in the code, which would mean madness (!)

View on HN

I get this sort of thinking, but it assumes Chrome follows specs 100%. None of the browsers do that unless it is a very old spec with no recent changes.

There's WebKit, Gecko and whatever they're calling the engine that powers Edge. I don't see a reason to test 10+ browsers if most of them are using WebKit.

I think there's EdgeHTML for Edge (fork), Trident for IE. Isn't Chrome using a fork now? (Blink?)

Chrome and Opera use Blink, a fork of WebKit, which is itself a fork of KHTML.

Developers need to be aware of differences in browsers and implement their projects accordingly. Anything less is simply unprofessional.

Developers work on browsers, too. It's a two-way street.

Agree.

Just a few years ago this was a common understanding.

It was kind of the hard thing about web development.

If course today the hard thing about web development is to keep the build environment working :-P

Reply on news.ycombinator.com