If Apple does something remarkable, or if somebody does something remarkable with Apple products, then by all means post such a story. This sort of article doesn't qualify, however.
Disagree. This is about things skilled hackers do for the general good and therefore is on topic for Slashdot.
I wonder why the AMD and NVidia results are separated, and there is no direct comparison between them? By comparing tables from different pages, my take is: Radeon 6990 kicks the GTX 590 by roughly 30%, with comparable lower end cards showing a similar pattern. Both companies do great, but AMD does greater.
I don't have a problem with MIT license or anybody spinning off a proprietary for-profit version. Charge what the market will bear, that does not devalue the original gift to the community. I do have to say though that the "developer wall" barrier is just going to drive away most developers. Prove me wrong!
The developer wall is not a complete stopper for me. It just puts this project right near the bottom of my interest list. My take on it at the moment is that Stanford as an institution does not get open source.
Did anybody succeed in checking the source out of Subversion?
I'm sure there will be plenty of fanbois in this discussion, but this is the person you chose to call out?
Half truths are the most insidious kind. So somebody discovers that Bulldozer likes a certain kind of scheduling and runs faster with it. That is not "one benchmark", that is an interesting optimization technique. Completely fair, and nobody can claim that Intel fails to benefit from optimizations directed at their exact architecture as well.
I ditched Skype ever since Version5 started an OS-level crashfest due to terrible video handling and essentially a "nofix" spat in my face.
Skype is relegated here to a lowly eee, which is used for nothing but Skype. It is not allowed on any real machine. Skype is actually pretty horrible considering what it could be. It could actually tell the truth about who is online with reasonable latency, for example. It could actually handle running on two machines with the same login id for example. But whatever. Not supporting Android properly means that Skype is doomed, and good riddance.
I have a pretty fast android device (Archos 43) and the UI feels smooth about half the time, the other half it's flaky and unresponsive.
Building the whole UI in Java instead of just supporting Java applications was a completely stupid idea. I just wonder how long this mistake is going to last - less than forever? We can only hope.
Im guessing they are running compiler in ARM virtual machine, compiler is of course written in JAVA.
I would hope you're wrong, there is such a thing as a cross compiler. But truth to tell, I have seen Googlers do such things and not even get thrown immediately into the proverbial alligator pit.
Just by way of illustration, there was one guy on my team at Google whose solution to a QA problem was to run the whole build under QEMU, increasing the latency of the build by two orders of magnitude. Turning it into an overnight process in fact. And this guy's approach had the full support of my manager, even being tech lead of the team I was not allowed to overrule that braindamage. No technical reason at all, just pure process of its own sake. This kind of mess is endemic at Google, including in some of the highest profile projects. Oh wait, we just saw that, didn't we?
I'm really curious as to what it is that they're doing that's going to require more RAM than most of these devices have in total storage space.
Being lame. Apparently, being a certified smart person does not necessarily imply understanding how to code efficiently, including not understanding how to code a build efficiently. An excellent example of how Google hobbles its development pace by its fear of embracing community developers.
Slashdot Mirror
If Apple does something remarkable, or if somebody does something remarkable with Apple products, then by all means post such a story. This sort of article doesn't qualify, however.
Disagree. This is about things skilled hackers do for the general good and therefore is on topic for Slashdot.
See, it's not about Apple, it's about us.
I wonder why the AMD and NVidia results are separated, and there is no direct comparison between them? By comparing tables from different pages, my take is: Radeon 6990 kicks the GTX 590 by roughly 30%, with comparable lower end cards showing a similar pattern. Both companies do great, but AMD does greater.
By the way, one of the nice features of the MIT license is, anybody can take the code and GPL it.
I don't have a problem with MIT license or anybody spinning off a proprietary for-profit version. Charge what the market will bear, that does not devalue the original gift to the community. I do have to say though that the "developer wall" barrier is just going to drive away most developers. Prove me wrong!
The developer wall is not a complete stopper for me. It just puts this project right near the bottom of my interest list. My take on it at the moment is that Stanford as an institution does not get open source.
Did anybody succeed in checking the source out of Subversion?
I'm sure there will be plenty of fanbois in this discussion, but this is the person you chose to call out?
Half truths are the most insidious kind. So somebody discovers that Bulldozer likes a certain kind of scheduling and runs faster with it. That is not "one benchmark", that is an interesting optimization technique. Completely fair, and nobody can claim that Intel fails to benefit from optimizations directed at their exact architecture as well.
What lack of "proper" Android support are you referring to?
Video.
Now that MS bought Skype, it's essentially dead on Linux.
You can stop at "essentially dead".
Then no real friend?
Skype should really go after the morons for design their UI, because it has the worst possible user interface EVER.
Worse than Oracle Applications?
If Skype, or even Flash, brought down your OS, you need a new OS (and more than likely a new computer).
I can see getting rid of Windows for that reason, but why a new computer?
I ditched Skype ever since Version5 started an OS-level crashfest due to terrible video handling and essentially a "nofix" spat in my face.
Skype is relegated here to a lowly eee, which is used for nothing but Skype. It is not allowed on any real machine. Skype is actually pretty horrible considering what it could be. It could actually tell the truth about who is online with reasonable latency, for example. It could actually handle running on two machines with the same login id for example. But whatever. Not supporting Android properly means that Skype is doomed, and good riddance.
You can always hate on Microsoft. It's a Slashdot right, don't you know?
True, the right to hate on the hateful.
Wow, Intel fanbois are out in force.
So solving a QA problem is not a technical reason? Surely there is more to this story.
Obviously, there were other solutions to the problem not requiring running under QEMU, as you might expect.
I remember when compiling the Linux kernel took hours on my Pentium 2.
Interesting. It never took longer than about 20 minutes for me, usually building Linus's defaults.
I have a pretty fast android device (Archos 43) and the UI feels smooth about half the time, the other half it's flaky and unresponsive.
Building the whole UI in Java instead of just supporting Java applications was a completely stupid idea. I just wonder how long this mistake is going to last - less than forever? We can only hope.
Quick question for those with giant codebases such as this. How the heck do you test, and debug the software with those kind of lag times?
You have a lot of code monkeys with high pain threshold and tolerance for less than perfect quality of life in return for a paycheck.
Im guessing they are running compiler in ARM virtual machine, compiler is of course written in JAVA.
I would hope you're wrong, there is such a thing as a cross compiler. But truth to tell, I have seen Googlers do such things and not even get thrown immediately into the proverbial alligator pit.
There should be a build flag to select between "just build sorta fast code and don't take all day" vs "go crazy". Obviously.
As a fringe benefit, you then get more test coverage.
I would guess the default Android build is optimized for the Google Android team, and so speed is the most important factor
Well, but the build speed sucks too. I feel comfortable stating that what we have here is a problem of too much suck.
Just by way of illustration, there was one guy on my team at Google whose solution to a QA problem was to run the whole build under QEMU, increasing the latency of the build by two orders of magnitude. Turning it into an overnight process in fact. And this guy's approach had the full support of my manager, even being tech lead of the team I was not allowed to overrule that braindamage. No technical reason at all, just pure process of its own sake. This kind of mess is endemic at Google, including in some of the highest profile projects. Oh wait, we just saw that, didn't we?
I'm really curious as to what it is that they're doing that's going to require more RAM than most of these devices have in total storage space.
Being lame. Apparently, being a certified smart person does not necessarily imply understanding how to code efficiently, including not understanding how to code a build efficiently. An excellent example of how Google hobbles its development pace by its fear of embracing community developers.
Figures.
Fear mongering headlines followed by outright lies in the summaries, and people eat it up...
Google has brought this on themselves by being less than forthcoming.
There is probably a battle between lawyers and engineers going on within the walls...
Good and evil.