Google lost any sense of reality about 6-8 years ago: there's no way to report bugs in their apps or phones (they are completely ignored), there's no way to get in touch with their dev team, there's no official forum which is frequented by Google employees, and no support of any kind.
It would be great if they had a resemblance of bug tracker in Google Play where people could vote for bugs or propose/vote fot features but I guess Google just don't want this kind of publicity because they "know" better what their users want and secondly, their development practices and the real attitude towards their audience will become apparent.
Every time they act on something is not because their completely dysfunctional groups attract hundreds of responses, it's because someone from the media also gets fed up with the issue and publishes a post/news which then gets attention probably from Google's PR department which then forced the dev team to take action.
Also, this particular CPU has its iGPU disabled completely which is actually quite weird - I don't remember the last time your released an i3 U part without an integrated GPU.
However could you maybe delve a little bit more into that please? Other fabs have seemingly had very few problems transitioning from 12nm (which is close to Intel's 14nm) to 7nm (which basically matches your 10nm). And unlike other fabs you started working on the 10nm node several years earlier, so you had quite an advantage.
Eugene Kaspersky still lives in Moscow and he's still an ex-KGB agent. These two facts alone make look Kaspersky highly untrustworthy considering that the Kremlin is waging e-war with the rest of the world.
the move from 22nm to 14nm to 10nm has been AWFULLY slow and it's one of the driving factors in why computer processing hasn't really improved hugely in the past 4 to 10 years
I believe it's more about the limits of current technology and the fact that the CPU frequency depends on the voltage and since the power consumption and dissipation varies with the square of the DC supply voltage you just cannot raise the voltage arbitrarily unless you want your CPU to consume hundreds of watts of energy. And also there's the speed of light at play - you cannot arbitrarily raise CPU frequency because electrons will not have enough time to traverse the chip. Another issue is that the x86-64 instructions set is very difficult to optimize because the architecture is so old.
Designing a 14nm tech process in the 70's/80's was impossible because it has taken billions of dollars of investments and new technologies (some of which weren't invented at Intel) to get there. Also, considering that they've rehashed their 14nm tech process twice and their first 10nm part is a castrated 2core CPU minus iGPU, it surely looks like 10nm is extremely difficult/costly to get right.
Most likely by mistake last Sunday Intel released Z390 chipset information. The page has since been pulled down because this chipset was rumored to be accompanied with octa-core Coffee Lake CPUs which are yet to be announced.
It's a weird situation really. Whatsapp/Facebook messenger and Viber, which are no less popular in this country, are not blocked which begs the question whether these three instant messengers shared their encryption keys with the authorities.
Also, to understand what this country really is, read for instance this. It's a mafia/authoritarian state where money rules and there's no law for those who have no money. Don't even get me started on health care, education and science - which are either semi-dead or completely dead, depending on your point of view.
This film is equal amounts of FUD and fearmongering. Almost nothing else (except some jobs will be replaced by AI - but that's been happening for over 200 years, except I'd replace "AI" with technology).
Most hardcore AI experts (and Musk is not one of them) don't see AGI happening any time soon. We just have no idea what intelligence and consciousness are. Not a freaking clue.
If you're referring specifically to hardware H.264 decoding support in Firefox, AIUI hardware decoding support has been included in the last few versions but may be disabled by default, requiring some tweaks to the preferences.
I was talking specifically about web browsers (since the original poster was talking about the difficulties of playing VP9 content on youtube). I'm perfectly aware that Mplayer/ffmpeg has had HW decoding acceleration for many years already - in fact I use VDPAU all the time.
VP9 is hardware accelerated in Firefox but only if you're on Windows 10 and have an appropriate CPU/GPU: Intel Skylake or better; NVIDIA Maxwell Gen2/Pascal; AMD Polaris/Vega;-)
I'm not aware of other web browsers but Chrome and Edge might support hardware decoding on Windows 10 as well.
As for Linux it's all very sad - even H.264 is not hardware accelerated.
As with VP9 earlier, the first reference AV1 encoder is absolutely slow: currently it's an order of magnitude slower than x265's veryslow preset (which is extremely slow to begin with).
AV1 is not currently supported by anything under the sun except an alpha build of Firefox (where it struggles to decode even a 3Mbps video on powerful PCs).
Most likely ffmpeg will include its own decoder (implementation) because ffmpeg and AV1 developers have contradicting views on coding styles. ffmpeg has its own VP9 decoder.
Apple joined the alliance just a few months ago when the development was almost over, which means Apple most likely didn't really contribute to it at all.
Last time I checked/. was an international website (besides CA/UK/AU and NZ have long finished metrication), so why do I keep seeing imperial units here?
Not with Telegram or its current implementation. It's a cloud based IM which has a single encryption key. All your data is stored in the cloud. P2P chats in Telegram are ostensibly end-to-end encrypted but they are so inconvenient, few people actually use them. You cannot backup them, you cannot save them.
He didn't meddle in the election, he meddled in the opponents who were basically buffoons with no presidential campaigns whatsoever and his only real opponent was barred from the election under the illegal premises.
There are only two ways for Putin to stop being a Tzar of Russia: either he will die from natural couses or he will be murdered. Democracy is basically a swear word in Russia. Russia had it just once in 1994 and only by chance.
Both vulnerabilities are blown out of proportions and you need to rush to actively fix them only when your platform runs untrusted code which is mostly relevant for VPS/clouds/etc.
When you only run your own trusted code (say a DB or an HTTP server), there's little if any need to patch them urgently. Of course, this implies that your authentication process is properly secured and when it's not, the intruder might as well find other local unpatched vulnerabilities.
Slashdot Mirror
Google lost any sense of reality about 6-8 years ago: there's no way to report bugs in their apps or phones (they are completely ignored), there's no way to get in touch with their dev team, there's no official forum which is frequented by Google employees, and no support of any kind.
It would be great if they had a resemblance of bug tracker in Google Play where people could vote for bugs or propose/vote fot features but I guess Google just don't want this kind of publicity because they "know" better what their users want and secondly, their development practices and the real attitude towards their audience will become apparent.
Every time they act on something is not because their completely dysfunctional groups attract hundreds of responses, it's because someone from the media also gets fed up with the issue and publishes a post/news which then gets attention probably from Google's PR department which then forced the dev team to take action.
It's all quite bleak really.
Quantum computers will solve current encryption algorithms as soon as we solve general AI. Oh, wait ...
Authoritarian regimes lie more than democracies.
Also, this particular CPU has its iGPU disabled completely which is actually quite weird - I don't remember the last time your released an i3 U part without an integrated GPU.
Thanks!
However could you maybe delve a little bit more into that please? Other fabs have seemingly had very few problems transitioning from 12nm (which is close to Intel's 14nm) to 7nm (which basically matches your 10nm). And unlike other fabs you started working on the 10nm node several years earlier, so you had quite an advantage.
Eugene Kaspersky still lives in Moscow and he's still an ex-KGB agent. These two facts alone make look Kaspersky highly untrustworthy considering that the Kremlin is waging e-war with the rest of the world.
I believe it's more about the limits of current technology and the fact that the CPU frequency depends on the voltage and since the power consumption and dissipation varies with the square of the DC supply voltage you just cannot raise the voltage arbitrarily unless you want your CPU to consume hundreds of watts of energy. And also there's the speed of light at play - you cannot arbitrarily raise CPU frequency because electrons will not have enough time to traverse the chip. Another issue is that the x86-64 instructions set is very difficult to optimize because the architecture is so old.
Have you seen their R&D expenditures?
Designing a 14nm tech process in the 70's/80's was impossible because it has taken billions of dollars of investments and new technologies (some of which weren't invented at Intel) to get there. Also, considering that they've rehashed their 14nm tech process twice and their first 10nm part is a castrated 2core CPU minus iGPU, it surely looks like 10nm is extremely difficult/costly to get right.
Most likely by mistake last Sunday Intel released Z390 chipset information. The page has since been pulled down because this chipset was rumored to be accompanied with octa-core Coffee Lake CPUs which are yet to be announced.
Next time I'm gonna web-archive their mistakes ;-)
No, it's Heise. Neowin's news team has been and remains a joke.
This could be hugely interesting: https://github.com/gcp/leela-z...
From http://parkersolarprobe.jhuapl... : "The deadline for submissions was April 27, 2018 at 11:59 PM EST and entries are no longer being accepted."
It's a weird situation really. Whatsapp/Facebook messenger and Viber, which are no less popular in this country, are not blocked which begs the question whether these three instant messengers shared their encryption keys with the authorities.
Also, to understand what this country really is, read for instance this. It's a mafia/authoritarian state where money rules and there's no law for those who have no money. Don't even get me started on health care, education and science - which are either semi-dead or completely dead, depending on your point of view.
This film is equal amounts of FUD and fearmongering. Almost nothing else (except some jobs will be replaced by AI - but that's been happening for over 200 years, except I'd replace "AI" with technology).
Most hardcore AI experts (and Musk is not one of them) don't see AGI happening any time soon. We just have no idea what intelligence and consciousness are. Not a freaking clue.
I was talking specifically about web browsers (since the original poster was talking about the difficulties of playing VP9 content on youtube). I'm perfectly aware that Mplayer/ffmpeg has had HW decoding acceleration for many years already - in fact I use VDPAU all the time.
VP9 is hardware accelerated in Firefox but only if you're on Windows 10 and have an appropriate CPU/GPU: Intel Skylake or better; NVIDIA Maxwell Gen2/Pascal; AMD Polaris/Vega ;-)
I'm not aware of other web browsers but Chrome and Edge might support hardware decoding on Windows 10 as well.
As for Linux it's all very sad - even H.264 is not hardware accelerated.
As with VP9 earlier, the first reference AV1 encoder is absolutely slow: currently it's an order of magnitude slower than x265's veryslow preset (which is extremely slow to begin with).
AV1 is not currently supported by anything under the sun except an alpha build of Firefox (where it struggles to decode even a 3Mbps video on powerful PCs).
Most likely ffmpeg will include its own decoder (implementation) because ffmpeg and AV1 developers have contradicting views on coding styles. ffmpeg has its own VP9 decoder.
Apple joined the alliance just a few months ago when the development was almost over, which means Apple most likely didn't really contribute to it at all.
The spec is 619 freaking pages long.
Last time I checked /. was an international website (besides CA/UK/AU and NZ have long finished metrication), so why do I keep seeing imperial units here?
OnePlus 5T
Huawei Mate 10
Xiaomi Mi A1 - costs around $200. Works with most cellular operators of the world.
Not with Telegram or its current implementation. It's a cloud based IM which has a single encryption key. All your data is stored in the cloud. P2P chats in Telegram are ostensibly end-to-end encrypted but they are so inconvenient, few people actually use them. You cannot backup them, you cannot save them.
He didn't meddle in the election, he meddled in the opponents who were basically buffoons with no presidential campaigns whatsoever and his only real opponent was barred from the election under the illegal premises.
There are only two ways for Putin to stop being a Tzar of Russia: either he will die from natural couses or he will be murdered. Democracy is basically a swear word in Russia. Russia had it just once in 1994 and only by chance.
Really? Like blocking TCP port 25? Tell us another joke.
All major web browsers have already been patched against this vulnerability. Nice joke, though.
Both vulnerabilities are blown out of proportions and you need to rush to actively fix them only when your platform runs untrusted code which is mostly relevant for VPS/clouds/etc.
When you only run your own trusted code (say a DB or an HTTP server), there's little if any need to patch them urgently. Of course, this implies that your authentication process is properly secured and when it's not, the intruder might as well find other local unpatched vulnerabilities.
Another reporter is confirming my findings: very old uTorrent clients (3.0) are not susceptible to these attacks.