Also, one can write a generic Android app that integrate well enough with Honeycomb that one do not really need to advertise it as Honeycomb-specific. Just add some artwork and layout specifications for the larger screens and your good to go.
Also, i suspect companies and individual developers are waiting for Ice-cream Sandwich. This as it will integrate the fragments UI stuff from Honeycomb with the 2.x series of Android.
Well, nothing is perfect. But how many changes would a airline implement on its fleet if they where not mandated by an authority that could ground them? Hell, a recent accident was likely because a relevant authority made a refit "optional" rather mandatory.
And consider that the Challenger accident likely happened because the people running the o-ring supplier prioritized their company over the safety of the crew. I recall the example used was that the chief-engineer/CEO green-lighted the flight once he replaced his engineer pov with the CEO pov.
The reason for this is that there have been a transition from APM to ACPI. The former leaves the details up to the OS, the latter have some kind of meta-language for "describing" the hardware capabilities. Sadly it was set up while MS was still doing their EEE thing, and so we have something that on paper should be a standard, but in reality only really work in Windows. The rest of the world have to second guess everything.
And EFI seems to be heading in the same direction...
Also, unless they have some kind of watchdog with actual teeth breathing down their necks, corporations rarely bother with customer security. This thanks to the beancounter ways of balancing X years between lawsuits for Y amount against projected security costs over the same period.
Mostly the direction problem in government is pork hunting. End result is a whole lot of "tulip farms" dotting the map. And this will eventually appear in any large organization.
Supposedly the tablet initiative within Microsoft belly flopped because some exec at the Office division did not see the light and would not approve any changes to the office suite that would make it more tablet friendly. End result was that attempting to use MS Office on a tablet because a sequence of kludges.
I suspect this is because, as found by Phoronix, Linux is unable to turn hardware off when it is not in use. This thanks to buggy ACPI or similar that the OEMs work around in their own drivers for Windows, but that the Linux devs have to find out about the hard way. Hell, not too long ago there was a desktop motherboard that was unbootable if Linux was honest about itself. This thanks to a garbage ACPI entry for anything other then Windows.
There was something here on/. a while back about the various issues with thumbnailing systems in file managers. So even if autorun may not get you, there are still risks.
As i think was stated way back in the early days of the word geek, they are nerds with social graces. These days, geek seems to blend into hipster, and becoming every more nebulous.
Slashdot Mirror
Americans hate paying taxes, even if its something for their own good, and they receive a direct benefit from those taxes.
A attitude that seems to be spreading to Europe as well.
Also, one can write a generic Android app that integrate well enough with Honeycomb that one do not really need to advertise it as Honeycomb-specific. Just add some artwork and layout specifications for the larger screens and your good to go.
Also, i suspect companies and individual developers are waiting for Ice-cream Sandwich. This as it will integrate the fragments UI stuff from Honeycomb with the 2.x series of Android.
Well, nothing is perfect. But how many changes would a airline implement on its fleet if they where not mandated by an authority that could ground them? Hell, a recent accident was likely because a relevant authority made a refit "optional" rather mandatory.
And consider that the Challenger accident likely happened because the people running the o-ring supplier prioritized their company over the safety of the crew. I recall the example used was that the chief-engineer/CEO green-lighted the flight once he replaced his engineer pov with the CEO pov.
And these days they go by masseuse...
http://www.flickr.com/photos/danperdue/26204311/
Sounds interesting, if only as a look into how they prioritized security of their subsystems...
And across history...
https://secure.wikimedia.org/wikipedia/en/wiki/Grain_supply_to_the_city_of_Rome#Politics_and_the_grain_supply
Difference is that the mentioned tech was limited to a single appletalk network. The new stuff got a potential global reach.
And given a big buzz thanks to Mac fanboys being media involved. Seriously, how else did the update of Final Cut Pro end up on prime time tv?
Sounds like a security nightmare...
Well, there are LEDs for that...
Hell, with the right LED setup, one can even do color changes to fit the mood.
So it is yet another "Foxconn" rerun?
There is the bumblebee project for Nvidia that seems to have some progress.
The reason for this is that there have been a transition from APM to ACPI. The former leaves the details up to the OS, the latter have some kind of meta-language for "describing" the hardware capabilities. Sadly it was set up while MS was still doing their EEE thing, and so we have something that on paper should be a standard, but in reality only really work in Windows. The rest of the world have to second guess everything.
And EFI seems to be heading in the same direction...
Also, unless they have some kind of watchdog with actual teeth breathing down their necks, corporations rarely bother with customer security. This thanks to the beancounter ways of balancing X years between lawsuits for Y amount against projected security costs over the same period.
Mostly the direction problem in government is pork hunting. End result is a whole lot of "tulip farms" dotting the map. And this will eventually appear in any large organization.
Supposedly the tablet initiative within Microsoft belly flopped because some exec at the Office division did not see the light and would not approve any changes to the office suite that would make it more tablet friendly. End result was that attempting to use MS Office on a tablet because a sequence of kludges.
Could be the age old "skimp on safety because one lawsuit in x years is less expensive then the added costs for the same period"...
I suspect this is because, as found by Phoronix, Linux is unable to turn hardware off when it is not in use. This thanks to buggy ACPI or similar that the OEMs work around in their own drivers for Windows, but that the Linux devs have to find out about the hard way. Hell, not too long ago there was a desktop motherboard that was unbootable if Linux was honest about itself. This thanks to a garbage ACPI entry for anything other then Windows.
There was something here on /. a while back about the various issues with thumbnailing systems in file managers. So even if autorun may not get you, there are still risks.
What if one make it a phased array antenna instead?
https://secure.wikimedia.org/wikipedia/commons/wiki/File:Satellite_phone.jpg
if that can reach sats, one should not need a big square to reach much shorter distances.
Now to give it some buzzsaw jaws and some target tracking sensors.
I wonder if urban will be the battleground of choice of these things. Tanks seems to have a real problem with urban areas.
As i think was stated way back in the early days of the word geek, they are nerds with social graces. These days, geek seems to blend into hipster, and becoming every more nebulous.
Java? Makes it about as much web as x86 assembly then.
Dunno about log off and reboot, but shutdown can be done by simply hitting the power button on most computers these days.