News for hackers. Stuff that matters.
Re:Explanation of the state of uBlock Origin and other block... by Wowfunhappy on Friday September 20, 2019 @05:40PM (#21031584)
It's quite important that developers actually test their desktop layout and functionality (hover states, etc which don't work on a touch screen) with Safari's engine.
Re:Explanation of the state of uBlock Origin and other block... by scarface74 on Friday September 20, 2019 @10:03PM (#21033022)
If a site doesn’t work with desktop Safari well, you can tell them to just use Chrome.
Re:Explanation of the state of uBlock Origin and other block... by Wowfunhappy on Saturday September 21, 2019 @09:17AM (#21035192)
No, that would be precisely the problem!

We don't want websites to be written for compatibility with a single browser engine. That means developers are writing to Chrome's quirks, not to actual web standards. Over the long term, that gives Google complete control over how the web is run.

There are currently between 3 and 2.5 browser engines that matter, depending on how you count webkit vs blink. I'd really rather that not fall down to only 2 on desktop.

Re:Explanation of the state of uBlock Origin and other block... by scarface74 on Saturday September 21, 2019 @10:42AM (#21035643)
I’m not saying what we want I’m saying that whether we want it or not, it doesn’t matter whether Safari’s desktop market share drops from the current 3.6% (https://netmarketshare.com/browser-market-share.aspx?options...) to 1.8%, it won’t change the calculus on whether web designers care about desktop safari when they can just tell people who are complaining - use Chrome.
Re:Explanation of the state of uBlock Origin and other block... by Wowfunhappy on Sunday September 22, 2019 @07:43AM (#21040872)
It makes a big difference for me, at my job. 3.6% is enough users that I can justify spending (some) time to test and fix bugs. As that number approaches 1%, however, it gets much harder.