251–260 of 264 posts
These comments really highlight how Hacker News is slowly devolving into Slashdot with a stuck in the past mentality and no constructive criticism just groupthink attacks on "stuff we don't like or understand".
Earlier quoted context omitted.
I see no explanation given why an asset that never changes would need to be requested once a day, and they clearly state they do record it. > We only [sic] see 1 CSS request per font family, per day, per browser. Google Fonts logs records of the CSS and the font file requests, and access to this data is kept secure. I read that as what's written there. It's for tracking. Tracking popularity is still tracking.
> Tracking popularity is still tracking. Tracking usually refers to tracking users, which as I read the FAQ isn't what it's for.
Earlier quoted context omitted.
Sorry, I'm not letting you get away with an illogical argument here. There's nothing hypocritical about the authors of web.dev making an auditing tool because some other people who work for the same company work on site that (may) do badly. In fact, it wouldn't be hypocritical even if the authors of web.dev themselves worked on a site that did badly. It is, after all, a tool. It's not a declaration of superior intell…
The hypocritical statement is on the part of the company, not the specific authors. The efforts represent the company, as do their efforts in standards organizations, browser implementations, and email user interfaces. It is completely logical to question their inconsistencies especially as one of the primary drivers of standards. If the company cannot present a consistent front, we can ask ourselves whether their at…
Earlier quoted context omitted.
> The reason progressive enhancement has fallen away is because Javascript support is now ubiquitous. Your browser has it. Your screen reader has it. Even web crawlers have it. That's only part of the problem: every day I encounter sites which fail because the developers assumed not just that everyone has JavaScript but that they can load tons of assets reliably and instantaneously. The key part of progressive enhanc…
I'd put network use in a different category. It is an important issue though. Thankfully the tools are getting better for this. The recently supported font-display property is a great one. It allows devs to choose how to handle web font rendering over slower internet connections. Now I just wish more devs would start to take advantage of all the great performance tools available. Those best practices are unfortunatel…
My rationale for considering it to be included is that as the concept was developed I took the spirit of progressive enhancement to be doing the best with what your users have rather than only catering to people with the same setup you have.
> Now I just wish more devs would start to take advantage of all the great performance tools available. Those best practices are unfortunately rarely taught.
Agreed. I think one of the challenges has been both showing business value from performance — once you're putting things into a cost/benefit comparison it's a lot easier to get people to routinely consider the performance impact of their decisions.
Earlier quoted context omitted.
> The reason progressive enhancement has fallen away is because Javascript support is now ubiquitous. Your browser has it. Your screen reader has it. Even web crawlers have it. That's only part of the problem: every day I encounter sites which fail because the developers assumed not just that everyone has JavaScript but that they can load tons of assets reliably and instantaneously. The key part of progressive enhanc…
>A couple of weeks back, I was using a family member's Spectrum “high-speed” cable modem service at a whopping 5Mbps with latency measured in the hundreds of milliseconds. And that's still great internet compared to some places. I have a house out in the middle of nowhere that is only served by a single satellite internet provider (surrounded by trees that block the view to other providers' sats). I get 20Mbs at ~500…
Earlier quoted context omitted.
> The reason progressive enhancement has fallen away is because Javascript support is now ubiquitous. Your browser has it. Your screen reader has it. Even web crawlers have it. That's only part of the problem: every day I encounter sites which fail because the developers assumed not just that everyone has JavaScript but that they can load tons of assets reliably and instantaneously. The key part of progressive enhanc…
I'd put network use in a different category. It is an important issue though. Thankfully the tools are getting better for this. The recently supported font-display property is a great one. It allows devs to choose how to handle web font rendering over slower internet connections. Now I just wish more devs would start to take advantage of all the great performance tools available. Those best practices are unfortunatel…
Earlier quoted context omitted.
Sorry, I'm not letting you get away with an illogical argument here. There's nothing hypocritical about the authors of web.dev making an auditing tool because some other people who work for the same company work on site that (may) do badly. In fact, it wouldn't be hypocritical even if the authors of web.dev themselves worked on a site that did badly. It is, after all, a tool. It's not a declaration of superior intell…
The hypocritical statement is on the part of the company, not the specific authors. The efforts represent the company, as do their efforts in standards organizations, browser implementations, and email user interfaces. It is completely logical to question their inconsistencies especially as one of the primary drivers of standards. If the company cannot present a consistent front, we can ask ourselves whether their at…
Earlier quoted context omitted.
I'd put network use in a different category. It is an important issue though. Thankfully the tools are getting better for this. The recently supported font-display property is a great one. It allows devs to choose how to handle web font rendering over slower internet connections. Now I just wish more devs would start to take advantage of all the great performance tools available. Those best practices are unfortunatel…
for font-display, do you prefer swap or fallback?
Weirdly it also points out that my elements have non-unique Ids which is false and the list of failing elements shows that, it looks like they are stopping their search at the colon character, but they should not.
This is useless to me because I have a website, not a web application. I got a 46/100 on PWA which is astonishing because the site being tested is not a progressive web application at all. Imagine vim getting a 40/100 score in the category of web browsers. Weirdly good score. The accessibility audit is garbage as well. Apparently I should add an image to the site just so I can put an alt attribute in it. I should inc…