LEDs are far more efficient than incandescent. I have an LED/incandescent flashlight that lasts far longer in LED mode than incandescent mode but is not quite as bright. ie. Led brightness * LED time far greater than incandescent brightness * incandescent time.
... both on ARM simulators (ie a reasonable comparisons). Android is about 5-10 times as fast as WinCE for equivalent tasks.
As others have posted, 200MHz is nothing to sniff at (unless you're throwing it away with bloatware). If Windows 3.11 could run snappily on a 50MHz 486 then there is no good reason for slow software on a 200MHz ARM.
One of the interesting outcomes of the speed difference is that this means Android based devices should have far better power figures than equivalent Windows CE devices.
Efficiency is something you have to design in early. The idea that you caan make a bloaty architecture efficient is broken. You don't get a gazzelle by shaving an elephant's legs.
Maybe they'd communicate by farting and think we're answering them?
Seriously though,there is a missing factor fd = fraction of those civilisations communicating in a way that we can detect.
We've been in existence for some 100s of thousands of years, maybe millios of years and we've only had proper radio comms for 60 or so years - a small fraction of that. Its pretty arrogant to think that they'd use radio because that's the best technology we have. If other beings have SETI programs, perhaps they're using different communications methods. Perhaps direct brain communications but unfortunately we lock up the receivers in mental hospitals.
Although it seems pretty silly, I can see MS's point of view. Autopatcher is essentially becoming a Windows patch "distro" and the more people that use this the less control MS have over patch roll out.
Say in the future MS want to push out a patch that is so mean and so unethical that Autopatcher refuse to include it (kids, don't say that's impossible - we all know MS has infinite Evilness). Suddenly MS has a large body of people that won't swallow the patch.
Less tinfoil-hat-wearing is that Autopatcher shows up MS's own ineptness.MS have shown for a long time that Windows users are their assets ("our install base") and don't treat them as customers. Customer service is secondary to asset control.
Industrial espoinage has always been part of doing business since Ugg hid behind a bush to watch Ogg's special way of cracking rocks to make a sharp cutting edge. Since then we've had the bronze age, etc etc, the west thieving silk, gunpowder and porcelain from the east and pretty much everyone stealing everyone else's IP. Nothing new here.
MS CFO, Chris Liddell, ( http://www.stuff.co.nz/4395049a28.html ) has driven up the aquisition rate and is proud of having done so. He says that MS should be prepared to borrow (for the first time) to make aquisitions.
Considering that they were prepared to spend 40-odd bn for yahoo when Vista probably cost them 5 bn, they are very serious about aquisitions.
MS have never really got far with their aquisitions (except office and MSDOS) so this new policy will probably burn a hole in the bottom of the ship.
THis looks like command line vs GUI wars all over again. GUIs are fine for rapidly hitting easy-to-find targets but sometimes typing is far easier and faster. Lumbering crap GUIs are really hard to drive (eg. MS Visual Studio).
Semantic webs might be OK for small document sets where you can visualy search tags and click them. Want to look up something about monkeys? Look for the tag that says monkeys (or maybe find primates first, then monkeys) and click it.
But for huge data sets this sucks. After a smallish number of documents & subjects it must be far easier to type monkeys in search box and have Google etc do the search.
This might work for handling some queries, but will suck supremely for complex queries over large data sets (eg. the whole www).
Cores are really a lot more like software than hardware and GPL or BSD or whatever makes a lot of sense, depending on what the releaser is trying to achieve. OpenCores is doing pretty well.
Real hardware is a bit more challenging to release in open source form for many reasons: * Hardware definitions are done in layout packages with very different file structures etc making it difficult to share designs across diferent tool chains. * RF and power designs are more physical implementations than schematic ones. That is, it is easy to render a schematic in different physical forms some of which will work and some of which won't.
The POC code needs to have different alignments for x86 and x86_64 but that in itself does not mean that the same concept could not be used to break other architectures, (eg. ARM which probably runs the majority of Linux systems out there... all the phones etc).
What is important is whether the explotable code is being run. This is only relevant to VMs. Very few Linux phones etc will be using VMs and probably none are using this explotable architecture.
Slashdot Mirror
LEDs are far more efficient than incandescent. I have an LED/incandescent flashlight that lasts far longer in LED mode than incandescent mode but is not quite as bright. ie. Led brightness * LED time far greater than incandescent brightness * incandescent time.
then it becomes visible
Isn't that one of those oxymoron things like "Military Intelligence".
Go to China to clean hotel rooms and hopefully get pregrant so that your kids are Chinese and have a Real Future and can live the Chinese Dream.
What next for
Ubuntu installed: $50.
As others have posted, 200MHz is nothing to sniff at (unless you're throwing it away with bloatware). If Windows 3.11 could run snappily on a 50MHz 486 then there is no good reason for slow software on a 200MHz ARM.
One of the interesting outcomes of the speed difference is that this means Android based devices should have far better power figures than equivalent Windows CE devices.
Efficiency is something you have to design in early. The idea that you caan make a bloaty architecture efficient is broken. You don't get a gazzelle by shaving an elephant's legs.
When you post the material you are agreeing to their terms of use and giving them the appropriate rights to hold the images or whatever.
Seriously though,there is a missing factor
fd = fraction of those civilisations communicating in a way that we can detect.
We've been in existence for some 100s of thousands of years, maybe millios of years and we've only had proper radio comms for 60 or so years - a small fraction of that. Its pretty arrogant to think that they'd use radio because that's the best technology we have. If other beings have SETI programs, perhaps they're using different communications methods. Perhaps direct brain communications but unfortunately we lock up the receivers in mental hospitals.
You should be able to see those with Hubble.
Earth girls only have one vagina. How lame is that?
"Not on MS servers" is FUD, not a valid reason. For MS it is all about controlling the distribution chain.
Although it seems pretty silly, I can see MS's point of view. Autopatcher is essentially becoming a Windows patch "distro" and the more people that use this the less control MS have over patch roll out.
Say in the future MS want to push out a patch that is so mean and so unethical that Autopatcher refuse to include it (kids, don't say that's impossible - we all know MS has infinite Evilness). Suddenly MS has a large body of people that won't swallow the patch.
Less tinfoil-hat-wearing is that Autopatcher shows up MS's own ineptness.MS have shown for a long time that Windows users are their assets ("our install base") and don't treat them as customers. Customer service is secondary to asset control.
Make hay while the sun shines and all that. People daft enough to pay $4 for a coffee are prime candidates to sting for some wifi too!
and at the big sales meeting... ...
sales, sales, sales,
sales, sales, sales,
sales, sales, sales,
sales, sales, sales,
now it is probably:
SP1, SP1, SP1,
SP1, SP1, SP1,
SP1, SP1, SP1,
SP1, SP1, SP1,
Gotta give it Ballmer, he sure understands innovation.
Deja vu?
"DOS isn't done until Lotus doesn't run."
he'd be trying to nail them with Sarbaney-Oxley for leading investors to think they have better products and a better market position than they do.
and they will just not allow you in and put you on the next plane outta there.
Industrial espoinage has always been part of doing business since Ugg hid behind a bush to watch Ogg's special way of cracking rocks to make a sharp cutting edge. Since then we've had the bronze age, etc etc, the west thieving silk, gunpowder and porcelain from the east and pretty much everyone stealing everyone else's IP. Nothing new here.
Considering that they were prepared to spend 40-odd bn for yahoo when Vista probably cost them 5 bn, they are very serious about aquisitions.
MS have never really got far with their aquisitions (except office and MSDOS) so this new policy will probably burn a hole in the bottom of the ship.
Expect MS to go on a big shopping spree.
If so, I predict very bad handling for aircraft coming from Nigeria.
Semantic webs might be OK for small document sets where you can visualy search tags and click them. Want to look up something about monkeys? Look for the tag that says monkeys (or maybe find primates first, then monkeys) and click it.
But for huge data sets this sucks. After a smallish number of documents & subjects it must be far easier to type monkeys in search box and have Google etc do the search.
This might work for handling some queries, but will suck supremely for complex queries over large data sets (eg. the whole www).
TFS is broken. A core is really software. It is written in code (eg. VHDL or Verilog). That source code is copyrightable just like any other code.
Real hardware is a bit more challenging to release in open source form for many reasons:
* Hardware definitions are done in layout packages with very different file structures etc making it difficult to share designs across diferent tool chains.
* RF and power designs are more physical implementations than schematic ones. That is, it is easy to render a schematic in different physical forms some of which will work and some of which won't.
What is important is whether the explotable code is being run. This is only relevant to VMs. Very few Linux phones etc will be using VMs and probably none are using this explotable architecture.