And you're typing this on your computer made in China, hurling on your flatscreen made in China, while licking the cheeto crust off your fat fingers (somewhere along the line that processed cheese touched China). You're fairly delusional.
There's always good 'ol SICP. Although the focus isn't on learning Scheme (lisp dialect) you end up picking it up along the way. I can't think of a good CS undergrad program that doesn't make you read it, anyway.
Too bad that same behavior happens in firefox2. Try it - start typing an address, the autocompletions pop up, choose the bottom one a few times. It goes to the top. You're complaining about nothing.
Way to beat on that straw-man...
Besides, if you bothered to read the article:
"There are also tens of thousands of additional species pages not authenticated by scientists but still containing a wealth of information.
Later this year the public will be able to contribute text, videos, images, and other information about a species and the best of it will be incorporated into the authenticated pages."
By the way, it's spelled "elitist".
The problem is that more and more its technologically infeasible to increase clock speed without frying chips built with ever tinier components. We still have the ability to cram a few more transistors onto the silicon, though. This by itself doesn't solve anything - having the ability to cram transistors on doesn't do jack if you can't make use of them. Right now, increasing the core count seems to be best way to utilize the room on the chip, which is why all the major processor manufacturers have banked on it for the near future.
Basically, we've chosen parallelization as the way of the future. Concurrency is a tough problem to tackle, though, which is why a lot of programs either don't make use of it as much as they could. Some tasks just can't be parallelized anyway. The difference between the core race and the gigahertz race is that at least the cores have some potential. Sure, you can bump the clock up to 3GHZ if you make an incredibly long pipeline, but if you can't fill that pipeline or it get stalled or you get interrupted and have to flush the whole thing, the 3GHZ isn't all that useful. Much of those problems are out of the software developers' control. If you have enough jobs for the cores, though, and write a program that makes good use of parallelization (much easier said than done), multi-core will actually give you a big performance increase.
Slashdot Mirror
And you're typing this on your computer made in China, hurling on your flatscreen made in China, while licking the cheeto crust off your fat fingers (somewhere along the line that processed cheese touched China). You're fairly delusional.
There's always good 'ol SICP. Although the focus isn't on learning Scheme (lisp dialect) you end up picking it up along the way. I can't think of a good CS undergrad program that doesn't make you read it, anyway.
Too bad that same behavior happens in firefox2. Try it - start typing an address, the autocompletions pop up, choose the bottom one a few times. It goes to the top. You're complaining about nothing.
Way to beat on that straw-man... Besides, if you bothered to read the article: "There are also tens of thousands of additional species pages not authenticated by scientists but still containing a wealth of information. Later this year the public will be able to contribute text, videos, images, and other information about a species and the best of it will be incorporated into the authenticated pages." By the way, it's spelled "elitist".
The problem is that more and more its technologically infeasible to increase clock speed without frying chips built with ever tinier components. We still have the ability to cram a few more transistors onto the silicon, though. This by itself doesn't solve anything - having the ability to cram transistors on doesn't do jack if you can't make use of them. Right now, increasing the core count seems to be best way to utilize the room on the chip, which is why all the major processor manufacturers have banked on it for the near future. Basically, we've chosen parallelization as the way of the future. Concurrency is a tough problem to tackle, though, which is why a lot of programs either don't make use of it as much as they could. Some tasks just can't be parallelized anyway. The difference between the core race and the gigahertz race is that at least the cores have some potential. Sure, you can bump the clock up to 3GHZ if you make an incredibly long pipeline, but if you can't fill that pipeline or it get stalled or you get interrupted and have to flush the whole thing, the 3GHZ isn't all that useful. Much of those problems are out of the software developers' control. If you have enough jobs for the cores, though, and write a program that makes good use of parallelization (much easier said than done), multi-core will actually give you a big performance increase.
Did you bother to try this one yourself? Ubuntu 7.10 is definitely affected out of the box.