Top
Best
New

Posted by speckx 14 hours ago

98% isn't much(whynothugo.nl)
471 points | 311 commentspage 9
cj17382 13 hours ago|
This whole article is a categorical error. Whether something is good or not entirely depends on the frame of reference and the context. You can argue endlessly by shifting the topic that 98% is used on. I guess that's what people are doing here.
miltonlost 13 hours ago|
"Whether something is good or not entirely depends on the frame of reference and the context" is exactly what the article was saying....
ninjahawk1 11 hours ago||
Jesse, we need to refactor the edge cases Jesse
cantalopes 13 hours ago||
I am not exactly sure what is the article trying to point out
217 13 hours ago||
while true, the people who will read this and then think twice about implementing and applying things are exactly the people who already doing too much thinking
apexalpha 12 hours ago||
Can you imagine a venue refusing entry to former clients 2% of the time just because they’ve “improved their experience”?

Sure, it's called a 'dress code'.

vb-8448 13 hours ago||
If it's uptime it's definitively not much!
dango369 13 hours ago|
this made me lol
Unai 13 hours ago||
I blame it in big part on the WebDX community group, their absolutely useless "Baseline" guidelines, and on them allowing Apple to be part of that group and make decisions on what features are "ready" to use whilst being behind the only non-evergreen browser in 2026.

The "baseline" means nothing. The percentage in caniuse means nothing. The only number that matters is the number of Safari users stuck using a no longer supported Apple device that access your website. Of course Apple makes sure to hide usage stats of older devices.

Everyone complains about only having three browser engines out there, but I'll be happy to go down to two if that means freeing the world from Safari.

timw4mail 12 hours ago|
And I see the opposite: Safari is a valuable check on constant additions and bloat to the web platform.
WaitWaitWha 13 hours ago||
The author seems to equivocate by comparing completely different domains.

Whether 98% is acceptable, it depends on the cost of failure, not the percentage itself.

1970-01-01 13 hours ago||
60% of the time, it works every time
artisin 9 hours ago|
Reading the comments, I expected this blog post to be about something fundamental. But nope. It's just about native CSS nesting. A convenience feature that merely adopts functionality that preprocessors have long provided. Maybe I'm alone in this viewport, but this isn't even worth debating unless you, the developer, are the priority.
More comments...