|Chrome Prototype To Throttle Your Web Pages|
|Written by Ian Elliot|
|Wednesday, 06 February 2019|
How to make the web go faster? It's easy, you simply impose guillotine policies on what is being downloaded. If a web page loads a resource that is "too big" - just block it!
This gives you some idea just how out of touch browser developers are. The real worry is that the wider subculture of browser developers might just be in the same bubble and actually go through and implement it.
OK, we are all guilty of adding to web pages so that they get bigger and bigger. No one is denying that page bloat is a real problem but it is the web page/app developer's problem not the browser maker's.
Caps do not apply to workers and size caps are lifted for resources loaded from Service Worker Cache Storage.
And if these limits don't take your breath away you have no creativity.
The details of the new mode aren't 100% clear and as it is only an internal proposal we have to hope that it will never happen, but it gives you food for thought about how browser people are focused on their software rather than yours. You might over-stuff the page. It might not even be your doing given the number of inputs there are to a page. Even so in the end it is you, or the company you are working for, which determine how well-crafted and svelte the final product is. Whatever its eventual qualities, it is your page, your site and it has been constructed as best you can, given the constraints, and it does what you intend it to.
Now along comes a browser and starts to tear your work to shreds. It sometimes isn't as bad as aborting resource downloads. Sometimes it can be just be an option to view your page in condensed or simplified mode. Imagine if Picasso had had to suffer his works been reprocessed in simplified mode? An artist has a right to have his work displayed as the artist intended and I would argue that the same applies to us. Browsers should concentrate on rendering a page as closely as possible to the intent of its creator. Browsers shouldn't go beyond the standards and impose clever tricks on the web developer's work.
For us programmers, the years since the introduction of the personal computer and the open internet have seen nothing but restrictions on what we can do. Apps stores control what apps we can make available, boot loaders refuse to load custom operating systems and browsers block anything they think might be used inappropriately. Now it seems the browser designers value the speed and efficiency of their product over the integrity of ours. One might think that they should be on our side.
Perhaps it's time for a "Works best as I designed it" campaign.
Or perhaps - "Never Slow; Always Broken".
or email your comment to: email@example.com
|Last Updated ( Wednesday, 06 February 2019 )|