4 ms·
Ha. That's like removing a bunch of methods from a program and claiming it's broken when it crashes. What did you expect to happen when blocking half of a sit
by SquareWheel 8y ago
Ha. That's like removing a bunch of methods from a program and claiming it's broken when it crashes. What did you expect to happen when blocking half of a site's libraries?
- tedunangst 8y agoAt the very least, I expect it to crash faster after removing methods. It should not pause for a long time and then work.
- jimbo1qaz 8y agoNews sites are hypertext, also known as formatted text, and not web-apps or programs which download and render websites. I expect news sites to load properly in the absence of the AMP CDN (not "half the methods"), not deliberately hide content from users. (I feel the same way about blocking page rendering when web-fonts don't download when their http connections hang instead.) EDIT: I just moved to desktop. If I block all scripts in uMatrix, OP's URL loads immediately (albeit with a full page of garbage above page content). If I block external scripts in uMatrix, I have to wait 8 seconds before anything appears.
- SquareWheel 8y ago>News sites are hypertext, also known as formatted text, and not web-apps or programs which download and render websites. No, there are many thousands of websites that render their content dynamically on the client - news or otherwise. Facebook, Twitter, and Reddit all make use of client-side rendering (and all provide news services). >not deliberately hide content from users Your browser also "deliberately hides content". It waits a few hundred milliseconds before triggering a paint, just to avoid content from jumping around. AMP pages do the same -- unless you break the mechanism of course.
- monadgonad 8y ago> Facebook, Twitter, and Reddit all make use of client-side rendering (and all provide news services) Oh, come on. You and I both know that those are social media apps which act as news aggregators, and are not themselves sources of textual news articles. jimbo1qaz was clearly talking about the latter.
- SquareWheel 8y agoWhat is the meaningful distinction between news websites and non-news websites? Client-side rendering is just a technique which isn't specific to any industry.
- askdlflkjklk 8y ago> News sites are hypertext, also known as formatted text, and not web-apps nope.
- manicdee 8y agoCompletely different. This is like a car that tries to phone home every time you start it, so either you keep the phone service active and get a salesperson talking to you while driving, or you disable the phone and the car leave the immobiliser active for a minute each time you try to start the car.
- SquareWheel 8y agoAre you upset that the website is using a CDN? That is the standard distribution method for common libraries. As for the other half of your analogy - stop poking holes in the gas tank and it won't need active service.
- pdkl95 8y agoUsing a CDN isn't the problem on it's own; the problem is the (unfortunately common) shoddy programming practice of assuming error never happen. Good programming almost always involves checking for and properly handling errors. Using the returned value from fopen(3) without checking if it was NULL probably results in the program crashing when displaying a simple "file not found" error message would have been more appropriate. This principle is also true when writing web pages; if you load an external resource, you need to check for and handle the case where that resource might not be available. Failing to load a resource can happen for many different reasons, not just someone blocking it with their client. Proper handling the error depends on what the resource is: display the content that is already available (perhaps in a less than ideal state), or if that isn't possible displaying an appropriate error message. This includes cases where the Javascript itself isn't available (for any reason). Networks are not reliable or universally available. Quality programming understand that and does the best it can when failures happen.
- SquareWheel 8y agoI agree with you. However understand that AMP actually does have a failsafe here, and it's exactly what the OP is complaining about. After a timeout (to allow for shoddy network conditions as you described) it will load the content as best it can. All three cases are actually covered (full-script support, partial-script support, and noscript support). That's more resilient than most apps.