I hate Service Worker. It literally provides a tools for website to abuse and judging from the trend things will be much worst in the next few years.
Neither PWA nor AMP are needed to make a website load fast
91–100 of 225 posts
Re: Neither PWA nor AMP are needed to make a website load fast
#92Want to load fast? Load less.
Re: Neither PWA nor AMP are needed to make a website load fast
#93>I’m not saying practices promoted by AMP are bad or useless. They are good practices. But nothing stops you from following them in the regular web. Disagree. The most important feature of AMP is that it makes it impossible to add the kind of bloated crap that causes poor performance on something like a large media company website. Something like a news website likely has 2-4+ analytics integrations, and a similar nu…
You are taking about policy here. The article is talking about technical implementation.
Re: Neither PWA nor AMP are needed to make a website load fast
#94Earlier quoted context omitted.
I assume you mean video editing. Many reasons, but the top one in my opinion is having a single code base across all devices. I think it's a worthwhile goal, personally.
Sure, but this is just as achievable, if more agreeably challenging on the desktop as a platform as it is on the web. I'm not sure if it's a particularly convincing axiom here for heavy payloads of web-apps, particularly when we're talking about simply delivering content to cite a singular code base for why a web application that would benefit from AMP (which was the central conceit of the actual blog post we're all…
Hmm, I don't think I ever mentioned AMP in my posts. I know the blog post talked about it, but I was focusing on the PWA bit, as it's something I'm fairly experienced with. When the guy mentioned 15MB, I was simply saying that it's not an outlandish size if you're delivering a PWA which provides 15MB worth of solid functionality.
I guess you got your wires crossed, as AMP is not something I was talking about - my focus was specifically on PWAs and the fact that it's not a problem if their payloads are large.
But yes, AMP (read: glorified CDN) wouldn't solve much if you have 15MB to download each time you visit a site (aside: you wouldn't need to do this with PWAs because of caching).
Re: Neither PWA nor AMP are needed to make a website load fast
#95>I’m not saying practices promoted by AMP are bad or useless. They are good practices. But nothing stops you from following them in the regular web. Disagree. The most important feature of AMP is that it makes it impossible to add the kind of bloated crap that causes poor performance on something like a large media company website. Something like a news website likely has 2-4+ analytics integrations, and a similar nu…
You are taking about policy here. The article is talking about technical implementation.
You missed GP’s point. They were saying that the devs generally didn’t need to be convinced, it’s the business owners who did. Being that AMP dictates none of the bloatware, the business can’t steamroll their demands over the engineers.
Re: Neither PWA nor AMP are needed to make a website load fast
#96Earlier quoted context omitted.
The outside bits of a Trojan horse are attractive for a reason.
It is the only available solution to a real problem. If you have a better solution, by all means, be a hero. Meanwhile, the rest of the search and content aggregation industry has gone with AMP, which works today.
> It is the only available solution to a real problem.
Don't shove JavaScript and random bloat into your website? That's what I do.
Re: Neither PWA nor AMP are needed to make a website load fast
#97Earlier quoted context omitted.
Not really - imagine if you're looking to create a fully featured video editor, complete with 3d effects and whatnot. It could well exceed 15mb to deliver all the required functionality.
Shouldn't this be a native desktop application versus foisting it onto web clients? If we're talking "fully featured"?
This is where the paradigm shift is coming. Your past experiences say it must be a desktop native app, but I believe things like WASM, web workers etc will allow such things to run comfortably in the browser.
I really do believe people will build for the browser more than they will for the desktop because it's a more universal platform.
I can even imagine a future where, for the majority, the only native app you have on your machine is a browser, and everything else is some variant of a PWA. I really feel this will happen very soon.
Re: Neither PWA nor AMP are needed to make a website load fast
#98In my experience AMP makes a website not load, until it times out and redirects to the non-AMP.
Re: Neither PWA nor AMP are needed to make a website load fast
#99Earlier quoted context omitted.
While everything you note is true, it's hardly the fault of the engineers. One cannot expect engineers to hand code css and optimize every time. These things should be handled by tools. With the advent of css-in-js and compilers, this is slowly but surely happening. What amp did was prove at scale, and with tooling, that performance can be achieved. That philosophy is dripping into other tools.
In some cases, sure, it's not the fault of engineers — if an engineer is in an environment where they're not able to take the time to do things right. In some cases, it is the lack of tools. But I think it's often not either of those, and it is in fact the chosen priorities of the engineers. A lack of attention to craft. We see a similar split in GameDev. Some game developers (Carmack, Blow, Acton) sweat every millis…
I think a lot of people program at work purely for monetary reasons. For this reason they follow the “it works, ship it” mentality because then they can focus on other tasks to make money from. If a sluggish program makes a million dollars but a beautifully written program makes 0, which shows more better craftsmanship? Admittedly that’s an unrealistic situation, but people have different motivations for coding.
Re: Neither PWA nor AMP are needed to make a website load fast
#100>I’m not saying practices promoted by AMP are bad or useless. They are good practices. But nothing stops you from following them in the regular web. Disagree. The most important feature of AMP is that it makes it impossible to add the kind of bloated crap that causes poor performance on something like a large media company website. Something like a news website likely has 2-4+ analytics integrations, and a similar nu…
You are taking about policy here. The article is talking about technical implementation.
Yes in that sense AMP is a business contact rather than a technical innovation. "Follow these rules and we'll tell users that we think your site is fast and maybe prioritise it in search results".
That's why you can't have a fast news site without it - because new site owners won't follow the rules needed to make their site fast unless they get something in return other than speed. Only AMP gives that.
If Google based is lightning bolt etc. on measured page speed instead then yes you might not need AMP. But they don't.