Live data from Hacker News

The Double Edged Sword of the Web

ponyfoo.com

11–20 of 48 posts

Re: The Double Edged Sword of the Web

#11
post #4

I wish I could downvote this article. It is from a developer who is married with Google Chrome and who is trying to tell us that other browsers are stupid because they don't have the same bugs as Chrome does. It's especially unnerving for me as a firefox user since these days I come across a lot more sites that make stupid mistakes that just works fine in their Chrome. This mindset makes me angry. The same applies wh…

I have to agree on this one. I have lots of respect for Nicolás and his work, but I think this article shows a little bit of arrogance towards users who don't use Chrome as their primary user. On top of that he disabled accessibility on Firefox entirely in favour of design preferences. Many developer might not care, but it's an attitude which needs to stop.

[deleted]

Re: The Double Edged Sword of the Web

#12
post #4

Earlier quoted context omitted.

I have to agree on this one. I have lots of respect for Nicolás and his work, but I think this article shows a little bit of arrogance towards users who don't use Chrome as their primary user. On top of that he disabled accessibility on Firefox entirely in favour of design preferences. Many developer might not care, but it's an attitude which needs to stop.

It's more than a little arrogance, it's a superiority complex. My jaw dropped when I read the following because it speaks volumes about his mindset. > As such, visitors are mostly privileged web developers using macOS and Google Chrome.

[deleted]

Re: The Double Edged Sword of the Web

#13
post #2

"Who is correct isn’t important. What should be important is that browsers put consistency across themselves first." No way - The only way we'll end up with compatibility across browsers is to have unambiguous (as much as possible) specifications that define how they should behave and for browser users to insist their browser vendor aligns with the standard. I lived through that past and have no desire to repeat it.…

"Who is correct isn’t important. What should be important is that browsers put consistency across themselves first."

I saw that quote too, and thought that's a weird way to look at it. The other way to look at it, which makes quite a lot more sense to me, is that Chrome is creating the inconsistency by being flat out wrong...

Re: The Double Edged Sword of the Web

#14
Weird layout.

The article text on the far left, and the side column on the far right with a LOT of white space between. The white space in the middle is as wide as the article text itself.

BTW, I'm on a 2560 width screen, using Firefox.

And this is what it looks like:

http://i.imgur.com/bWwMuNH.png

If this is considered good web design, I'm going back to Lynx ...

Re: The Double Edged Sword of the Web

#15

I wish I could downvote this article. It is from a developer who is married with Google Chrome and who is trying to tell us that other browsers are stupid because they don't have the same bugs as Chrome does. It's especially unnerving for me as a firefox user since these days I come across a lot more sites that make stupid mistakes that just works fine in their Chrome. This mindset makes me angry. The same applies wh…

I didn't get this at all from the article. He didn't say that other browsers are stupid, he said that they have bugs; the outline thing is a particularly nasty Firefox bug. It might also be a spec bug if the spec is not detailed enough on how to draw outlines; but it's also definitely a Firefox bug because it looks terrible. There's nothing wrong with calling a spade a spade.

Re: The Double Edged Sword of the Web

#16

Weird layout. The article text on the far left, and the side column on the far right with a LOT of white space between. The white space in the middle is as wide as the article text itself. BTW, I'm on a 2560 width screen, using Firefox. And this is what it looks like: http://i.imgur.com/bWwMuNH.png If this is considered good web design, I'm going back to Lynx ...

It's even more weird on a 40 inch 4K monitor. But it's tuned for a different kind of privileged web developer. The specific privilege that you and I are bringing (large, high resolution displays) evidently makes us not the target audience.

Jokes aside, virtually no sites are tuned for large displays, and there's widespread consensus that you shouldn't simply use the full width of the window for text because lines would be too wide to read comfortably. Still, I think my expectation is that most sites just end up centered within large windows.

The layout seen here, with columns anchored on the left and right sides, is unfamiliar and looks weird to my eye as well.

Re: The Double Edged Sword of the Web

#17
post #15

I wish I could downvote this article. It is from a developer who is married with Google Chrome and who is trying to tell us that other browsers are stupid because they don't have the same bugs as Chrome does. It's especially unnerving for me as a firefox user since these days I come across a lot more sites that make stupid mistakes that just works fine in their Chrome. This mindset makes me angry. The same applies wh…

I didn't get this at all from the article. He didn't say that other browsers are stupid, he said that they have bugs; the outline thing is a particularly nasty Firefox bug. It might also be a spec bug if the spec is not detailed enough on how to draw outlines; but it's also definitely a Firefox bug because it looks terrible. There's nothing wrong with calling a spade a spade.

A quick search turns up that it is indeed a Firefox bug and not a bug in the spec[0]. Honestly it is very disappointing that such an obvious issue has been left open for so long. This is part of a very old spec and that any browser doesn't have compliance with this is surprising.

[0] https://bugzilla.mozilla.org/show_bug.cgi?id=266122

Re: The Double Edged Sword of the Web

#18
post #15

I wish I could downvote this article. It is from a developer who is married with Google Chrome and who is trying to tell us that other browsers are stupid because they don't have the same bugs as Chrome does. It's especially unnerving for me as a firefox user since these days I come across a lot more sites that make stupid mistakes that just works fine in their Chrome. This mindset makes me angry. The same applies wh…

I didn't get this at all from the article. He didn't say that other browsers are stupid, he said that they have bugs; the outline thing is a particularly nasty Firefox bug. It might also be a spec bug if the spec is not detailed enough on how to draw outlines; but it's also definitely a Firefox bug because it looks terrible. There's nothing wrong with calling a spade a spade.

I agree that calling out bugs, especially if they've been reported and ignored, is worthwhile.

That said, I think what the parent comment is saying is that Chrome too has bugs and a web developer who exclusively tests in Chrome forgives those bugs as "just the way HTML rendering works." This makes the developer effectively blind to Chrome's defects.

A developer who uses Firefox exclusively will have a similar feeling of privileged disdain for Chrome's bugs: "How can Google ship a browser with this problem? This is unacceptably broken!"

I know I felt that way for ages with Chrome's font rendering [1]. Chrome's font rendering was so poor compared to Firefox that it was difficult for me to use even for short bursts of testing. Although admittedly—and in a way confirming my point—those who used Chrome regularly were conditioned to its rendering and in some cases didn't even perceive the difference when comparing them side-by-side.

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=25541

Re: The Double Edged Sword of the Web

#19
post #4

Earlier quoted context omitted.

I have to agree on this one. I have lots of respect for Nicolás and his work, but I think this article shows a little bit of arrogance towards users who don't use Chrome as their primary user. On top of that he disabled accessibility on Firefox entirely in favour of design preferences. Many developer might not care, but it's an attitude which needs to stop.

It's more than a little arrogance, it's a superiority complex. My jaw dropped when I read the following because it speaks volumes about his mindset. > As such, visitors are mostly privileged web developers using macOS and Google Chrome.

Meet the new bullies. Same as the old bullies.

There's a lot of this going on in the tech community. Far cry from when got pushed around... Now they're (we? I hope I'm not like this) the ones doing the pushing.

Re: The Double Edged Sword of the Web

#20
post #16

Weird layout. The article text on the far left, and the side column on the far right with a LOT of white space between. The white space in the middle is as wide as the article text itself. BTW, I'm on a 2560 width screen, using Firefox. And this is what it looks like: http://i.imgur.com/bWwMuNH.png If this is considered good web design, I'm going back to Lynx ...

It's even more weird on a 40 inch 4K monitor. But it's tuned for a different kind of privileged web developer. The specific privilege that you and I are bringing (large, high resolution displays) evidently makes us not the target audience. Jokes aside, virtually no sites are tuned for large displays, and there's widespread consensus that you shouldn't simply use the full width of the window for text because lines wou…

I don't know about the "widespread consensus", but forcing people to manually resizing their browser window to fit whatever they currently are reading is bad design in my book.

Most good sites, I think, (strangely not Hacker News though) have a width limiting, centered layout which makes it easy to read and browse.

Post reply on HN