Also, is there a physical home button? I can't tell from the photos. A tablet needs at least that one physical button.
There's not one, not two, but *THREE* physical buttons! Power, volume up, and volume down - just like on the Xoom and the Nexus 7.
The tablet is a Pentile display.
Nope, RGB subpixels - standard LCD layout. It is *NOT* pentile. Hence the "RGB Real Stripe", which is Samsung marketing for "we didn't fuck with it"
Android doesn't do subpixel hinting either. It falls apart with GPU-accelerated rendering and rotation. Not to mention it doesn't work unless you know the subpixel layout. Android just has a better font in Roboto. At high densities subpixel rendering simply isn't useful.
So people get a "'Holy shit!' mind blowing moment" because they realise it was programmed in JavaScript instead of Java? That's only because they're programmers, and they know that HTML/JavaScript has historically had shit performance and a crappy UX.
Judging by the video of the device in action, it *still* has shit performance and a crappy UX. That's probably how they figured out it was JavaScript. "Why is this thing so bloody slow and unresponsive? Oh hey, it must be JavaScript! Cool!"
No, you are completely wrong. CSS is built to be murder on a CPU that is completely unable to be GPU accelerated, modern CSS even more so. See all these rounded corners here on Slashdot? Ever wonder how those are rendered? It's not just a bitmap that gets blitted onto the screen like it would be on Android or iOS. Oh no, that's not how HTML+CSS rolls, that's old school trash. No, it's a gradient that is then clipped by an anti-aliased path. Guess what GPUs can't do at all? Paths. And that's just the work needed for the green headers!
Also note that Chrome OS is not targeting smartphones (afaik). It's really quite different.
Correct, they are only targeting hardware that is suitably fast. HTML5 is too bloody slow. Firefox OS will never, ever manage to beat native Android apps in speed, especially not on lower end devices.
"Hey, let's take this slower architecture than our competitors, and put it on slower devices than our competitors - brilliant!"
In other words, "Google already provides a combination of non-intuitive and user-download-required ad hoc ways to do one fourth of something that's being standardized elsewhere, so we should think it's OK for them to ignore the standardizations under way."
Hmm... for a minute there I thought you were shilling for Google. But now I realize you're just cognitively impaired.
Google supports DNT - both on their websites and on their browser. I know slashdoters don't read the article, but is it so hard to even read the title?
Hmm... for a minute there I thought you were FUDing against Google. But now I realize you're just cognitively impaired.
Oh, but really impressive work there - spinning that Google was way ahead of DNT on privacy as a negative thing. Yes, how dare they give you forms of opt out long before there is a standard way of doing that? Those evil bastards!
"find a way around it"?
I think you mean "just don't bother implementing support on the server side". By default DNT doesn't do anything at all. DNT only works on sites that take the engineering time to support it on their servers. Google has gone out of their way and spent time and money to support DNT - why would they then search for a way around it? That doesn't make any sense.
The mobile phone number is used for security to allow you to recover your account if you are one of the (many) idiots that picks a guessable password, re-uses passwords, or completely forgets their password.
That's been way faster for a while. Try the Intel x86 ones (which are very fast), or the GPU acceleration option for the ARM ones.
Censorship is far more than a "mere filtering of words". The sheer stupidity and ignorance of what you said is staggering.
Then again, you basically said "censorship is far and away more dangerous than censorship" and managed to get modded insightful, so whatever.
Collecting more information doesn't allow Google to show more ads or make more money, that's not how advertising works. You are also incredibly delusional on the value of your information (then again, most of slashdot is). Similarly, targeted advertising requires very *little* information - demographics are huge and wide. We're talking basic keyword matching, with a bit of age range & gender sprinkled in - that's it. Google will also happily show you and let you edit or delete your ad profile, by the way. But there really isn't much information there - there doesn't need to be.
No, Google collects a ton of information because information allows you to solve interesting problems. Any engineer will tell you much the same.
I remember when the tegra 2 was hot shit.
Tegra 2 was *never* hot shit. Nvidia didn't know what they fuck they were doing when they built it, and it is obvious. GPU was weak compared to the competition, the CPU was missing obvious stuff like NEON, it is so memory bandwidth starved it's ridiculous, etc...
What Nvidia managed to do really well, though, was *pretend* it was hot shit, which was convincing enough for tech bloggers.
So enable encryption - that's a fully supported option in Chrome. All Google's servers ever get are an encrypted blob.
You seem to care more about NVIDIA's image than about what the Linux community actually needs.
I truly don't understand what the big deal is. Just open up your damn specifications already.
AMD did this, and the Linux community still recommends people buy NVIDIA cards. Vote with your wallet, or shut the fuck up. Keep buying from the company with closed specs instead of open ones, and you'll keep getting closed specs instead of open ones. Not a difficult concept, people.
Beware of all enterprises that require new clothes, and not rather a new wearer of clothes. -- Henry David Thoreau
