That chinese site says "shipped by Lenovo". Go to Lenovo's site and search for Ideapad 330. There are six models, none of them have Cannon Lake. You know why? Because it isn't available, it only ever was available in sample quantities. The NUC site you snivelled about says "this product is expected to ship by Mid September." Expected. By who, you? Your ferret friends? And if you think it will actually ship in mid-september that you are even stupider than you sound, and that's saying something
You showed a product announcement, you did not show evidence of product availability. It's clear you are talking out your ass, but that's perfectly understandable because that is where your head is, fortunately a pretty good fit for a weasel. Now see if you can actually buy this NUC.
It was released in May in China. Whether you personally can buy it on Newegg is not the measure of whether "any product currently ships with it."
Show evidence that the product is available anywhere, including China, or stop drivelling. BTW, Intel also announced a NUC with the part, also not available. The China argument doesn't let you weasel out of that one. Good luck.
Didn't miss it. Z-culling will improve the blinking cursor case, but not fix it completely. Again, note: I like this, but let's not attribute magical powers to the technique that aren't there.
Theory and practice are not the same though. Check the actual docs and videos on webrender. The DOM + Compositing process currently used to re-render a single pixel is more expensive than cutting out that entire code path and rendering the entire scene. If you're only thinking of the final piece of pushing the actual pixel to the screen, that's the quickest part of the entire process. Figuring out what value that pixel should have in the first place is where all the CPU time is currently being consumed. That's the whole reason they're doing this the way they are.
Check the actual docs and videos on webrender. The DOM + Compositing process currently used to re-render a single pixel is more expensive than cutting out that entire code path and rendering the entire scene.
The actual docs say the opposite. "The optimizations above have helped pages render faster in certain cases. When not much is changing on a page—for example, when there’s just a single blinking cursor—the browser will do the least amount of work possible."
This is practice, not theory. Again, don't get me wrong, I like this a lot, but for some cases it will eat a lot more battery than incremental render. Whether that is a problem in practice remains to be seen. My guess: not a problem even on handsets, and perceptibly smoother browsing. I'll take it.
Firefox is my main browser for a lot of reasons, not just that Google doesn't dominate it. Great to see the Mozilla team leading the way on this, and it's a big validation for Rust. Any serious systems programmer ought to take a close look methinks.
Continuously animate one single pixel on the screen and your assumptions break, the GPU will never be idle. Don't get me wrong, I like this a lot, but power efficiency is definitely not a reason. But it isn't a complete power hog either. Compared to 3D games, shaders will be trivial. No matrix multiplies for example and no perspective divides. The fan on the GPU should stay off, and even the lamest integrated GPU should be able to handle it easily.
Slashdot Mirror
I know, you're nuts. As if nobody has ever pointed that out to you before.
So you failed.
I invite you to crawl back into your hole. Bye, in advance.
Show me how to buy that laptop from Lenovo's site, like their other shipping products. Oh, you can't.
a computer model supported by Lenovo with a Lenovo-stated release date and specs appearing all over the internet...
...that Lenovo's site doesn't list. Idiot.
Bye. (In case you still don't understand, that means please do the internet a favor and crawl back into your burrow.)
You linked to a driver, not a computer. Don't believe me that Cannon Lake is not available? Then maybe you will believe your Apple friends.
I'm not the one who said they stalk people on the internet for fun.
That chinese site says "shipped by Lenovo". Go to Lenovo's site and search for Ideapad 330. There are six models, none of them have Cannon Lake. You know why? Because it isn't available, it only ever was available in sample quantities. The NUC site you snivelled about says "this product is expected to ship by Mid September." Expected. By who, you? Your ferret friends? And if you think it will actually ship in mid-september that you are even stupider than you sound, and that's saying something
You showed a product announcement, you did not show evidence of product availability. It's clear you are talking out your ass, but that's perfectly understandable because that is where your head is, fortunately a pretty good fit for a weasel. Now see if you can actually buy this NUC.
You can't, even if they do sell to weasels.
It was released in May in China. Whether you personally can buy it on Newegg is not the measure of whether "any product currently ships with it."
Show evidence that the product is available anywhere, including China, or stop drivelling. BTW, Intel also announced a NUC with the part, also not available. The China argument doesn't let you weasel out of that one. Good luck.
And it's likely that the trojaned plugins were not downloaded from the official Kodi site. Need to wait for the details of course.
Do you also sneak around at night and peer into windows?
Didn't miss it. Z-culling will improve the blinking cursor case, but not fix it completely. Again, note: I like this, but let's not attribute magical powers to the technique that aren't there.
Could you quote some text please.
Theory and practice are not the same though. Check the actual docs and videos on webrender. The DOM + Compositing process currently used to re-render a single pixel is more expensive than cutting out that entire code path and rendering the entire scene. If you're only thinking of the final piece of pushing the actual pixel to the screen, that's the quickest part of the entire process. Figuring out what value that pixel should have in the first place is where all the CPU time is currently being consumed. That's the whole reason they're doing this the way they are.
Check the actual docs and videos on webrender. The DOM + Compositing process currently used to re-render a single pixel is more expensive than cutting out that entire code path and rendering the entire scene.
The actual docs say the opposite. "The optimizations above have helped pages render faster in certain cases. When not much is changing on a page—for example, when there’s just a single blinking cursor—the browser will do the least amount of work possible."
This is practice, not theory. Again, don't get me wrong, I like this a lot, but for some cases it will eat a lot more battery than incremental render. Whether that is a problem in practice remains to be seen. My guess: not a problem even on handsets, and perceptibly smoother browsing. I'll take it.
Firefox is my main browser for a lot of reasons, not just that Google doesn't dominate it. Great to see the Mozilla team leading the way on this, and it's a big validation for Rust. Any serious systems programmer ought to take a close look methinks.
Even better, take out the Google spyware links. (Google is far from the only culprit, they just waste the most total time.)
Continuously animate one single pixel on the screen and your assumptions break, the GPU will never be idle. Don't get me wrong, I like this a lot, but power efficiency is definitely not a reason. But it isn't a complete power hog either. Compared to 3D games, shaders will be trivial. No matrix multiplies for example and no perspective divides. The fan on the GPU should stay off, and even the lamest integrated GPU should be able to handle it easily.
It's not just that, this also depends on an efficient educational feeder system, starting in elementary school or even before.
You just love to make declarations that are easily proven wrong
OK, prove your point then. I hope you understand the difference between announced and available. Show me where I can get this part on Newegg.
I suppose you don't see any irony. Interesting specimen of something.
Right, after all, it's not more idiotic than significant tabs. Just about exactly as idiotic.
Oh, look who engaged, Mr Congeniality himself. You Apple bellycrawlers break me up.
So sorry, you did wet your jammies.