No. Even if it did, it doesn't matter because Android does NOT rely on Java for isolation or security. Each application runs as a separate Linux user, and the kernel enforces isolation between apps this way.
Because apps are isolated in this way, they can include native code.
One big argument I've heard against these systems is that the records tend to live forever, though backups, etc. If your company is subpoenaed, you may have to produce documents that you thought were destroyed long ago and no longer have any business use, yet might harm your case. At the very least, you may face some liability if confidential/protected documents leak out, like old payroll records that will inevitably have everyone's social security numbers.
I've interned at Google twice, so I know at least something about their infrastructure.
You can certainly use Google Docs for many things, including source code editing, version control, and bug tracking. However, I assure you that Google does NOT use Google Docs for these purposes. It's all about using the right tool for the job.
Google Docs might be perfectly fine for a one-way paging system to taxi cab drivers, but I'd imagine you'd want something a bit more customized. While I don't know much (if anything) about the taxi business, but you'd probably want to be able to track where your cabs are so you can dispatch jobs to the closest cab. You'd also need to know which cabs are free, and you'd might like to know where cabs are going and what their ETAs are. Sure, you could have your drivers type this in to Google Docs, but that's a pretty cumbersome and time-consuming UI. You could probably very quickly hack up a custom app to provide a nice UI for all of these features and get substantial time savings.
While they've been adding a lot of features to match Word (references, an equation editor, etc.), it still doesn't have everything. For example, I STILL can't make a two-column document in Docs (without using a table hack that's... less than optimal)! Until I can produce camera-ready scientific papers with Google Docs, for me it'll be a secondary tool to Word.
As the article states, duck.com was acquired when Google purchased On2 Technologies, previously known as The Duck Corporation. Duck made video codecs for Sega Saturn games, among others. On2 was finally acquired by Google for their VP8 video codec, which became part of the WebM video standard. No conspiracy here.
Not because he recorded video of people in public, but because he recorded audio. Audio has much stronger legal protections, and Washington is a two-party consent state, at least when it comes to telephone calls, etc.
"Manual controls for all key systems - keys and the like."
We had that, and the result was that cars were hotwired. In today's cars, there are cryptographic challenge/response schemes with the key, making them much harder to steal. Of course, this introduces a wireless digital interface...
Car systems are incredibly robust to random failures, but they don't do well against intentional failures that bypass the failsafe mechanisms.
I'm willing to bet it's far more likely that they'll need to patch security holes remotely than it is for the update mechanism itself to be exploited. That is, assuming they digitally sign the updates.
If a passenger is cleared for Precheck screening, a code is embedded in a traveler's boarding pass.... But Precheck travelers actually don't know if they will get to use the easy screening until the TSA officer checking IDs actually scans the boarding pass. If the pass has the code, a Precheck passenger is steered to a separate screening lane for what amounts to old-style airport screening.
Because terrorists don't have PDF417 scanners. Or PDF417 generators. I would be somewhat surprised if they actually did a proper DB lookup based on a boarding pass barcode.
If you're not signed in, they store your history for 180 days, but you can opt-out of that without a Google account: http://www.google.com/history/optout
3/4ths of both the House and Senate have to pass it, otherwise it gets put to a public vote.
Of course, the ESA could simply dissolve the ESRB, or refuse to rate any games shipped to Oklahoma. (Yes, the bill specifically mentions the ESRB and its ratings.)
'If you had the right (Internet) address, you could set up a laptop anywhere and you could watch the camera from there,' says Brigadier General Stewart Goodwin."
CHALLENGE ACCEPTED.
Who sets this kind of thing up without any authentication?!
I've thought about this a fair amount and have come to the conclusion that Native Client is not at all like ActiveX.
First, ActiveX targeted the Win32 APIs, ensuring that it only works under Windows. Native Client now uses the new Pepper APIs (which is a replacement for the old Netscape Plugin APIs) and runs under Windows, OS X, and Linux.
ActiveX relied on users to decide if a plugin is trustworthy. Native Client uses a sandbox to prevent code from doing anything that a regular web page couldn't do.
Work is underway to make Native Client work across multiple architectures. While x86, x64, and ARM are all supported today, soon you'll be able to build LLVM binaries that can be run on any architecture.
Microsoft's interest in ActiveX was tying web applications to Windows. Google's interest is in moving the web forward. After all, the more capable web applications can be, the better positioned they are to compete with traditional desktop software.
Google has long experimented with non-standard APIs in order to stimulate progress. For example Google Gears added geolocation, local databases and storage, background workers, and more. Due to the success of Gears, all of these are now in the HTML 5 standard. I think Google will pursue standardization of Native Client when it's more mature. In the mean time, it's giving people a glimpse of what web apps can be.
(And just to give Microsoft some credit, they sometimes move the web forward too. For example, they enabled AJAX with their XMLHTTP object in IE, which was later standardized as XMLHttpRequest.)
There's an app for that: http://dankaminsky.com/2010/12/15/dankam/
No. Even if it did, it doesn't matter because Android does NOT rely on Java for isolation or security. Each application runs as a separate Linux user, and the kernel enforces isolation between apps this way.
Because apps are isolated in this way, they can include native code.
... except Apple copied a lot of those ideas from Xerox PARC.
One big argument I've heard against these systems is that the records tend to live forever, though backups, etc. If your company is subpoenaed, you may have to produce documents that you thought were destroyed long ago and no longer have any business use, yet might harm your case. At the very least, you may face some liability if confidential/protected documents leak out, like old payroll records that will inevitably have everyone's social security numbers.
I've interned at Google twice, so I know at least something about their infrastructure.
You can certainly use Google Docs for many things, including source code editing, version control, and bug tracking. However, I assure you that Google does NOT use Google Docs for these purposes. It's all about using the right tool for the job.
Google Docs might be perfectly fine for a one-way paging system to taxi cab drivers, but I'd imagine you'd want something a bit more customized. While I don't know much (if anything) about the taxi business, but you'd probably want to be able to track where your cabs are so you can dispatch jobs to the closest cab. You'd also need to know which cabs are free, and you'd might like to know where cabs are going and what their ETAs are. Sure, you could have your drivers type this in to Google Docs, but that's a pretty cumbersome and time-consuming UI. You could probably very quickly hack up a custom app to provide a nice UI for all of these features and get substantial time savings.
While they've been adding a lot of features to match Word (references, an equation editor, etc.), it still doesn't have everything. For example, I STILL can't make a two-column document in Docs (without using a table hack that's... less than optimal)! Until I can produce camera-ready scientific papers with Google Docs, for me it'll be a secondary tool to Word.
If you're using Google Docs to dispatch taxis, you're doing something very wrong.
Google Docs is a great band-aid to quickly hack something together, but it's no substitute for real tools.
Super Star Fox Weekend (Official Competition). It was sold through Nintendo Power after the competition ended.
Oh come on... these polaroids look MUCH better than Instagram photos!
As the article states, duck.com was acquired when Google purchased On2 Technologies, previously known as The Duck Corporation. Duck made video codecs for Sega Saturn games, among others. On2 was finally acquired by Google for their VP8 video codec, which became part of the WebM video standard. No conspiracy here.
Perhaps they're just upset that they don't have the cool, new, hip calendar that Google invented, which doesn't include the month of December: https://code.google.com/p/android/issues/detail?id=39692
Not because he recorded video of people in public, but because he recorded audio. Audio has much stronger legal protections, and Washington is a two-party consent state, at least when it comes to telephone calls, etc.
"Manual controls for all key systems - keys and the like."
We had that, and the result was that cars were hotwired. In today's cars, there are cryptographic challenge/response schemes with the key, making them much harder to steal. Of course, this introduces a wireless digital interface...
Car systems are incredibly robust to random failures, but they don't do well against intentional failures that bypass the failsafe mechanisms.
Yes. This is why Project Pink (the Microsoft Kin) broke all sorts of sales records.
... that Apple already has a patent on this.
This applies to software tokens only.
I'm willing to bet it's far more likely that they'll need to patch security holes remotely than it is for the update mechanism itself to be exploited. That is, assuming they digitally sign the updates.
Because terrorists don't have PDF417 scanners. Or PDF417 generators. I would be somewhat surprised if they actually did a proper DB lookup based on a boarding pass barcode.
... because you haven't enabled Web History for your domain, so there's nothing to erase.
If, for some reason, you want Web History enabled on your domain, you can do it from the domain control panel.
I believe it was opt-in for a long time, but then it became opt-out for (new?) accounts. The change was announced here: http://googleblog.blogspot.com/2009/12/personalized-search-for-everyone.html
If you're not signed in, they store your history for 180 days, but you can opt-out of that without a Google account: http://www.google.com/history/optout
There is a version of Native Client called PNaCl which runs LLVM bytecode, but it's not finished yet...
Have you tried Dart? It's like JavaScript but with optional typing, and it compiles down to JavaScript.
3/4ths of both the House and Senate have to pass it, otherwise it gets put to a public vote.
Of course, the ESA could simply dissolve the ESRB, or refuse to rate any games shipped to Oklahoma. (Yes, the bill specifically mentions the ESRB and its ratings.)
'If you had the right (Internet) address, you could set up a laptop anywhere and you could watch the camera from there,' says Brigadier General Stewart Goodwin."
CHALLENGE ACCEPTED.
Who sets this kind of thing up without any authentication?!
I've thought about this a fair amount and have come to the conclusion that Native Client is not at all like ActiveX.
First, ActiveX targeted the Win32 APIs, ensuring that it only works under Windows. Native Client now uses the new Pepper APIs (which is a replacement for the old Netscape Plugin APIs) and runs under Windows, OS X, and Linux.
ActiveX relied on users to decide if a plugin is trustworthy. Native Client uses a sandbox to prevent code from doing anything that a regular web page couldn't do.
Work is underway to make Native Client work across multiple architectures. While x86, x64, and ARM are all supported today, soon you'll be able to build LLVM binaries that can be run on any architecture.
Microsoft's interest in ActiveX was tying web applications to Windows. Google's interest is in moving the web forward. After all, the more capable web applications can be, the better positioned they are to compete with traditional desktop software.
Google has long experimented with non-standard APIs in order to stimulate progress. For example Google Gears added geolocation, local databases and storage, background workers, and more. Due to the success of Gears, all of these are now in the HTML 5 standard. I think Google will pursue standardization of Native Client when it's more mature. In the mean time, it's giving people a glimpse of what web apps can be.
(And just to give Microsoft some credit, they sometimes move the web forward too. For example, they enabled AJAX with their XMLHTTP object in IE, which was later standardized as XMLHttpRequest.)