I have a hard time believing this is "for web developers" when most web developers used `.dev` for local development, which was broken because Google decided they wanted to own `.dev` for themselves.
Bad taste in my mouth.
21–30 of 264 posts
I have a hard time believing this is "for web developers" when most web developers used `.dev` for local development, which was broken because Google decided they wanted to own `.dev` for themselves.
Bad taste in my mouth.
I just ran their audit to https://mail.google.com , you guys (googlers) need to speed up your websites first, Gmail is terrible slow lately, just saying...
I also find it strange how I can get an A on every other page speed service, including GTMetrix, but get an F on Google's tes(s). Totally useless.
This looks kinda cool. I have a hard time believing this is "for web developers" when most web developers used `.dev` for local development, which was broken because Google decided they wanted to own `.dev` for themselves. Bad taste in my mouth.
Most web developers were wrong. The reserved TLD for local development has been .localhost since 1999.
This looks kinda cool. I have a hard time believing this is "for web developers" when most web developers used `.dev` for local development, which was broken because Google decided they wanted to own `.dev` for themselves. Bad taste in my mouth.
> when most web developers used `.dev` for local development Most web developers were wrong. The reserved TLD for local development has been .localhost since 1999.
Good because Lighthouse has some reasonable best practices to follow, and a few good performance timings, so lowering the barriers of entry is nice.
Bad because many of Lighthouses best practices aren't always applicable (our major media customers constantly say "stop telling me a need a #$%ing Service Worker!"). And while Speed Index and Start Render are great, Time-to-interactive, First CPU idle, and estimated keyboard latency are still fairly fluid/poorly defined, and of different value.
This all also overlooks the value that something like the Browser's User Timings provides (Stop trying to figure out what's a "contentful" or "meaningful" paint, and let me just use performance.mark to tell you "my hero image finished and the CTA click handler registered at X"), which Lighthouse doesn't surface up.
What is interesting is the monitoring side. WebPageTest, Lighthouse, Page Speed Insights, YSlow, etc are just point-in-time assessments that is largely commoditized. Tracking this stuff over time and extracting meaningful data is valuable, so that's pretty cool.
Disclaimer: I work in the web performance space. People replace homegrown Lighthouse, puppeteer, or WPT instances with our commercial software, so I'm biased. However I like a lot of the raising awareness and trail blazing about what Performance/UX means that Google is doing.
My biggest concern is the support outside of chrome.
While other browsers tend to come on pair with chrome in terms of features , chrome right now is the only one which supports PWA as "native" app..
Windows announced support for PWA natively a while ago [0] but there has been no news since then.
On Apple side it's silence radio...iOS have some support but for Mac it seems unlikely to happen...
[0]https://blogs.windows.com/msedgedev/2018/02/06/welcoming-pro...
Earlier quoted context omitted.
Precisely the opposite -- it's going to be available for open registration soon. https://get.dev/
Do you have to use Google's registrar service? That page isn't clear, and if you have to use Google's service, I don't view that as a good precedent.
I just ran their audit to https://mail.google.com , you guys (googlers) need to speed up your websites first, Gmail is terrible slow lately, just saying...
Google's pagespeed service is hot garbage. You can do things that make the page load significantly slower and get a perfect score than if you had a lower pagespeed score with a much faster page load. I also find it strange how I can get an A on every other page speed service, including GTMetrix, but get an F on Google's tes(s). Totally useless.