This extension allows users to save any web page they're on as a PDF file and share it or download it to disk.
Chrome has had these capabilities built-in for years. Go to the Print window and choose "Save as PDF".
Stop trying to surf the web with your toaster.
But seriously, I expect the answer to performance issues has something to do with pleasing the people who complain about browser memory usage. If you open 15 web pages with tons of graphics and videos and whatever they're going to use a lot of memory. If your computer can't handle it all, something is going to give, and a performance hit has to happen SOMEWHERE as a part of that.
When you open that photo, you're ONLY opening the photo. Easy. When you open a web page with the photo on it, you're downloading the file from the server, caching it on your local hard disk as well as in memory, loading the whole web page and all included files including scripts, not just a single image. The image viewer knows how to scale images fast because that is what it is designed to do. Your browser does as well but it wasn't designed to scale images for any specific purpose so it can't assume, for example, that the image won't be overlayed or it won't have an imagemap for interactivity or any number of things.
1. When all browsers do it, and it's not a standard, should you ignore it? I would say no. From a developer's perspective, you should reasonably try to support these things. This could also potentially be an accessibility issue... if the browser sees a page of content as different than how your web page sees it, I suppose there could be some sort of issue there.
2. OK, but the space bar scroll hasn't changed in that time.
3. You can scroll by page with the mouse by clicking on the scrollbar track. It's not just the keyboard that can do it.
4. I still find when scrolling through very large documents it's far easier on me to scroll by a page at a time to navigate faster.
Google had already finalized the latest security update when Dirty COW was discovered. December's update will be their first chance to patch it.
Furthermore given Android is an open platform ANYONE can develop for it, and this isn't Google's code at fault here. This is just a case of getting what you pay for when you buy a low-end Android phone that was made without adequate code review or security testing.
This is not Windows 10's fault. The game dev and/or publisher is responsible for this.
Before I get into it, I must admit it's not clear if refilled cartridges work or not. I think we have just some anecdotes that they don't but it could be isolated cases. So HP's claims there might have merit.
Now that that's over with, I want to draw your attention to this gem that caught my eye from HP's statements:
We updated a cartridge authentication procedure in select models of HP office inkjet printers to ensure the best consumer experience and protect them from counterfeit and third-party ink cartridges that do not contain an original HP security chip and that infringe on our IP,
This is amazing when you break it down. First of all you have this reasonable part:
We updated a cartridge authentication procedure in select models of HP office inkjet printers to ensure the best consumer experience and protect them from counterfeit and third-party ink cartridges
So far so good. Without any context it seems a reasonable enough statement.
The use of "that" here, though, indicates they are talking about a specific subset of counterfeit or third party ink cartridges (or that they believe all of them fit the following criteria). This is where they shoot themselves in the foot I think.
do not contain an original HP security chip
So, in other words, they are requiring you to only buy cartridges with their DRM in order to ensure you only buy cartridges with their DRM. Great circular logic there. But the best part is next:
and that infringe on our IP,
Why do they infringe? Because big companies have lobbied for laws to give themselves more power when it comes to their IP, and its these laws that give HP the authority to do what they do (as opposed to laws that might protect creators of competitive products). So HP's reasoning here is because it's legal, they're gonna do it. So if you strip away will the corporate speak, their OFFICIAL statement is not too far from that they're doing it because they thought they could get away with it.
fortune: cpu time/usefulness ratio too high -- core dumped.