Forgot your password?
typodupeerror

Comment Re:Why do we need more efficiency (Score 2) 570

Some great points, however we don't even need greenhouses or irrigation to do this. Check out this story of the transformation of some of the most arid, salty and generally hard to farm land in Jordan that has been transformed into productive farmland that captures and stores its own water supply completely self sufficiently:
Greening the desert
Chrome

Submission + - Chrome 10 Beta Boosts JavaScript Speed By 64% (computerworld.com)

CWmike writes: "Google released the first beta of Chrome 10 on Thursday, and Computerworld found it to be 64% faster than its predecessor on Google's V8 JavaScript benchmarks. But in another JS benchmark — WebKit's widely-cited SunSpider — Chrome 10 beta was no faster than Chrome 9. Yesterday's Chrome 10 beta release was the first to feature 'Crankshaft,' a new optimization technology. Google engineers have previously explained why SunSpider scores for a Crankshaft-equipped Chrome show little, if any, improvement over other browsers. 'The idea [in Crankshaft] is to heavily optimize code that is frequently executed and not waste time optimizing code that is not,' said the engineers. 'Because of this, benchmarks that finish in just a few milliseconds, such as SunSpider, will show little improvement with Crankshaft. The more work an application does, the bigger the gains will be.' [Chrome 10 beta download here.]"

Comment Re:Why not build upon J2ME then? (Score 1) 341

This pretty much explains the reasons behind Google's decision to go with Dalvik (well, except the specifics of the failed negotiations over J2ME licensing).

In short J2ME as licensed by Sun/Oracle under the GPL has deliberately had the 'classpath exception' removed. Developers targeting a GPL J2ME are forced to release their code as GPL due to the linking with all of the GPL'd libraries. According to their plan this would make paid J2ME licensing under non-GPL license a the only option for mobile vendors. Sun specifically did this for J2ME and not J2EE or J2SE as this is where they saw the most licensing money.

All this talk of complete implementation getting a patent license is moot it seems. Google decided that the paid licensing from Sun was prohibitive for one reason or another and that forcing the GPL on Android app developers was unacceptable. So when they took the decision to clean-room a VM from scratch any efforts to make the implementation complete would not have been rewarded with a patent grant.

Comment Re:Yay you. (Score 1) 245

My 'works for me' attitude is only the equivalent of your 'they suck as it won't work for me' attitude. I was just making a counter example where the results from the open source radeon driver have been excellent.

I can't stand fanboism either, my emphasis on the word *Ubuntu* was meant to mean : 'hey, its been stable for me *even* on Ubuntu' who don't have the best record on QA and have a reputation for putting features before stability.

Anyway its a shame you've had such a nightmare with the radeon driver but don't paint the efforts being made by AMD as worthless for everyone from your bad experience with one mobile GPU, there's a lot of happy users out there too.

Comment Re:And they suck. (Score 1) 245

Mobility X1400 (r500) in Thinkpad T60 user here. Radeon has been working great for well over a year now and KMS seems totally solid now, laptop goes for up to week or more at a time between reboots (suspend to RAM every night). 2D compiz is superbly smooth, even Flash plays smoothly full screened at 1650x1050. And thats on 64-bit *Ubuntu*.

Comment Re:Here is your benefit (Score 3, Informative) 245

You are missing the fact that when AMD introduced their open source strategy, they had a huge backlog of 'IP' to trawl through and review before releasing the documentation. Things started slowly and the wait for my R500 based laptop GPU to reach a decent level of support felt like a long time.

But from what we are seeing now AMD have made steady gains and have reached a point where they are releasing an OSS *driver* (albeit an immature one) for their latest GPU series less than a year after the hardware was released. Being able to 'drop' support for the proprietary drivers on legacy hardware earlier (in favour of the OSS driver option) will free up more developers within AMD to work on drivers for the latest GPUs. As the OSS driver team become and more more integrated within the workflow of the company we can expect to see OSS driver code and documentation get closer and closer to the hardware releases.

In short it looks like things are paying off for AMD and the OSS driver strategy. Keep up the good work AMD!

Windows

Peru To Be First To Put Windows On OLPC Laptop 292

Da Massive writes "The government of Peru will run the first ever trial of the One Laptop Per Child association's XO laptop running Windows XP. This puts the nation at the heart of a software controversy that has been raging for years between those who advocate making software and its source code free, such as Linux OS developers, and those who charge for software and keep the development recipes secret, such as Microsoft."

Slashdot Top Deals

"Of course power tools and alcohol don't mix. Everyone knows power tools aren't soluble in alcohol..." -- Crazy Nigel

Working...