No, the GP isn't kidding, and has a very relevant question. A signal dos not traverse the CPU in a clock cycle, as it also does not need to traverse a communication bus every clock cycle. If that were the case, we wouldn't be able to make intercontinental fiberglas links. We have pipelines and latency independent designs for solving those problems. Also, processor IO is way slower than its main clock.
Where the speed of light becomes very important is in two-way communication. AMD is trying to turn a GPU into something you want to have two-way communication with, and, hence, they must deal with the speed of light. Yet, it is not the sole botleneck they are facing.
"Electricity doesn't travel at the speed of light."
Funny... From my physics classes, I remember that all eletromagnetical waves propagated at the speed that eletromagnetical waves propagated. Maybe I missed something. By the way, it'd be ok if you said that electricity doesn't travel at the speed of light in vacuum, what you didn't.
Now, about the overall thread, the speed of light does not by itself limit switching time or bandwidth of a device, it doesn't matter its size. But, as the original poster said, it makes things harder, and some common restriction applying, it is a significative bottleneck.
They've beeing available, that is true. But they didn't use to work before Ubuntu. Nowadays the driver commes compiled and included at the kernel package, with the GLX dependency controlled by apt. Now it works.
I was comming from a broken Red Hat install, that succeded a broken Connectiva one, that succeded another broken Connectiva one, all of those refused to install my software due to dependency problems. Debian stable simply installed everything, and from the very few packages you couldn't install from testing, most become installable once you added the stable tree to sources.list, and most of the others just become installable a week or so after that. And it upgrades, and upgrades, and still you can install all those packages, even if you are using testing. That awesome.
And, of course, after you feel what is like having a desktop system where it is easier to find new software at the repository list than on Google, there is no comming back. I once tried to switch my desktop to Suse, just to find that I'd need to install (and keep up to date) nearly all my software by hand. That and the fact that you can configure it all by ssh, without any GUI program changing the settings that you choosed later makes it way easier to maintain than Red Rat and Suse on a server.
Guessing things based on context makes the life of the compiler much harder, and if the compiler has a hard time understanding your code, you'll have a hard time understanding what the compiler will output once it sees your code. All those aparently harmless simplifications lead to horrendous corner cases down the road. On this case, the worst problem isn't with the if(a=b) that could be defined to have a single meaning, just try writting: boll b = c = false; bool a = b == c; with your syntax.
Yes, epaper is only better if you read on a well lighted evironment, but it is way better on this kind of evironment. If you care about your vision you shouldn't be reading on dark places anyway, even with your facy pad. Ebooks also win in that you just need to carry a 300g device, without even caring about recharging it. With an iPad you'll carry 2kg of equipment, and you'd better not go too far from a power outlet.
It is way colder than 12K, but the density of matter in space is very small, what makes it hard to conduct any heat into it. You could still radiate the heat away, if you were able to carry enough radiative area, and dealed with the problem that is the Sun heating your radiators, instead of deep space cooling them.
It's a huge codebase, and it seems it is getting stable just now. Some tens of thousands of fixes more and I can even start thinking about switching to KDE 4:)
That group is also composed of unsavy people that will refuse to buy the game if they hear people complaining that the game doesn't work on their computer.
For one thing, gainning market share is the only long term viable protection against the kind of atacks free software is suffering today. Nobody would care if Linux users knew about software patents or not if corporations didn't have enough money to "convince" legislators, for example.
As a for profit gate keeper, Canonical is the less usefull friend of FOSS they can be, but the entry barriers on that market are quite low, so they can't be too harmfull either. If everybody turns against them, they'll be gone in no time (and that is what they are fighting here). Now, about politics, most people simply don't care. They wouldn't start caring if they knew you personaly, and even if they cared, they wouldn't care enough to help. I repeat myself here, the best we can get from them is they not helping the proprietary software makers that want to destroy us.
About why contributing to Debian, I guess they are worth to have an awesome operating system to use. Wasn't that the goal from the begining? (I really don't know, I only met Debian at Woody.) But I can't really say much, since my contributions are much much much smaller than yours, of course.
Funny that every time I tried to use Ubuntu (tose were a few), something simply didn't work. Somehow, the free drivers aren't at par with Debian's, but yeah, the proprietary ones work. Who need devices that lack proprietary (first class on Ubuntu) drivers, because the manufacturers publish their drivers at the Linux kernel. I'm not compiling a custom kernel just because a distro wants to make free drivers second class, thank you.
By the way, Debian stable just plain works. You get from the CD to a default set of application in little time more than the one it takes to download everything. And if you miss proprietary drivers, you just need to add the non-free and contrib branches and get them. Yes, it is harder than having they installed from the start, it takes a full 15 minutes of configuring.
Oh, and it is quite funny that you use a Debian distro just because apt trolls tell you they are better. It seems as if (nonsense, I'm sure) they are right, after all.
That is right, electrons on a metal have way bigger energy than what you'd expect from atoms at the same temperature. That happens because electrons are on a fermi condensate, and all the low energy states are ocupied. They don't follow the Boltzman distribution at all.
Slashdot Mirror
The point seems to be to avoid confusion once they start selling their CPU/GPU combos.
Ok, I just repeated TFS, mod me redundant if you wish, but I'm answering the parent.
No, the GP isn't kidding, and has a very relevant question. A signal dos not traverse the CPU in a clock cycle, as it also does not need to traverse a communication bus every clock cycle. If that were the case, we wouldn't be able to make intercontinental fiberglas links. We have pipelines and latency independent designs for solving those problems. Also, processor IO is way slower than its main clock.
Where the speed of light becomes very important is in two-way communication. AMD is trying to turn a GPU into something you want to have two-way communication with, and, hence, they must deal with the speed of light. Yet, it is not the sole botleneck they are facing.
Funny... From my physics classes, I remember that all eletromagnetical waves propagated at the speed that eletromagnetical waves propagated. Maybe I missed something. By the way, it'd be ok if you said that electricity doesn't travel at the speed of light in vacuum, what you didn't.
Now, about the overall thread, the speed of light does not by itself limit switching time or bandwidth of a device, it doesn't matter its size. But, as the original poster said, it makes things harder, and some common restriction applying, it is a significative bottleneck.
Only if you want to talk how the next SP of Windows 7 will sudenly suck 100GB more of disk, for no obvious benefit.
It's a widely known fact that work machines are cheap, and toys are the really expensive lot. That isn't an exclusivity of yours.
Did you search aptitude (or synaptic if you are on that kind of thing) for a driver or just Google? Google is a lousy source of software for Debian.
They've beeing available, that is true. But they didn't use to work before Ubuntu. Nowadays the driver commes compiled and included at the kernel package, with the GLX dependency controlled by apt. Now it works.
Give stable a try, you won't regret it. Those days that stable was old as hell are gone.
I was comming from a broken Red Hat install, that succeded a broken Connectiva one, that succeded another broken Connectiva one, all of those refused to install my software due to dependency problems. Debian stable simply installed everything, and from the very few packages you couldn't install from testing, most become installable once you added the stable tree to sources.list, and most of the others just become installable a week or so after that. And it upgrades, and upgrades, and still you can install all those packages, even if you are using testing. That awesome.
And, of course, after you feel what is like having a desktop system where it is easier to find new software at the repository list than on Google, there is no comming back. I once tried to switch my desktop to Suse, just to find that I'd need to install (and keep up to date) nearly all my software by hand. That and the fact that you can configure it all by ssh, without any GUI program changing the settings that you choosed later makes it way easier to maintain than Red Rat and Suse on a server.
I'm planning on making a week long trip without caring about having a power brick. Can I spend a week reading on an iPad without recharging?
The device weights a pound and a half. Add the weight of the power brick, the protective pack, and so on. You won't stay under 2kg.
One could read most Onion editions as a real newspaper. The only problem is that this one would get out with some faifh on humanity.
Guessing things based on context makes the life of the compiler much harder, and if the compiler has a hard time understanding your code, you'll have a hard time understanding what the compiler will output once it sees your code. All those aparently harmless simplifications lead to horrendous corner cases down the road. On this case, the worst problem isn't with the if(a=b) that could be defined to have a single meaning, just try writting:
boll b = c = false;
bool a = b == c;
with your syntax.
Yes, epaper is only better if you read on a well lighted evironment, but it is way better on this kind of evironment. If you care about your vision you shouldn't be reading on dark places anyway, even with your facy pad. Ebooks also win in that you just need to carry a 300g device, without even caring about recharging it. With an iPad you'll carry 2kg of equipment, and you'd better not go too far from a power outlet.
When your LAN has an entire country connected in it, it stops being local. Or if the entire world connected to it you'd still call it a LAN?
And, no, you are quite wrong. The hard part is getting gigabit links to every home. The back end is easy.
It is way colder than 12K, but the density of matter in space is very small, what makes it hard to conduct any heat into it. You could still radiate the heat away, if you were able to carry enough radiative area, and dealed with the problem that is the Sun heating your radiators, instead of deep space cooling them.
You are right that gravity does change with density, but scape velocity doesn't change with the density of the pack.
There are big nuclear things happening on Earth all the time. You can bet that episode created huge nuclear reactions.
It's a huge codebase, and it seems it is getting stable just now. Some tens of thousands of fixes more and I can even start thinking about switching to KDE 4 :)
It's KDE. Any change is a reasonable change for a user to do. That's why I use it.
That group is also composed of unsavy people that will refuse to buy the game if they hear people complaining that the game doesn't work on their computer.
Yet, it is way better to have 10% of a 100,000 market than 50% of a 1,000 one. TFA is too simplist to get into any usefull conclusion.
For one thing, gainning market share is the only long term viable protection against the kind of atacks free software is suffering today. Nobody would care if Linux users knew about software patents or not if corporations didn't have enough money to "convince" legislators, for example.
As a for profit gate keeper, Canonical is the less usefull friend of FOSS they can be, but the entry barriers on that market are quite low, so they can't be too harmfull either. If everybody turns against them, they'll be gone in no time (and that is what they are fighting here). Now, about politics, most people simply don't care. They wouldn't start caring if they knew you personaly, and even if they cared, they wouldn't care enough to help. I repeat myself here, the best we can get from them is they not helping the proprietary software makers that want to destroy us.
About why contributing to Debian, I guess they are worth to have an awesome operating system to use. Wasn't that the goal from the begining? (I really don't know, I only met Debian at Woody.) But I can't really say much, since my contributions are much much much smaller than yours, of course.
Funny that every time I tried to use Ubuntu (tose were a few), something simply didn't work. Somehow, the free drivers aren't at par with Debian's, but yeah, the proprietary ones work. Who need devices that lack proprietary (first class on Ubuntu) drivers, because the manufacturers publish their drivers at the Linux kernel. I'm not compiling a custom kernel just because a distro wants to make free drivers second class, thank you.
By the way, Debian stable just plain works. You get from the CD to a default set of application in little time more than the one it takes to download everything. And if you miss proprietary drivers, you just need to add the non-free and contrib branches and get them. Yes, it is harder than having they installed from the start, it takes a full 15 minutes of configuring.
Oh, and it is quite funny that you use a Debian distro just because apt trolls tell you they are better. It seems as if (nonsense, I'm sure) they are right, after all.
That is right, electrons on a metal have way bigger energy than what you'd expect from atoms at the same temperature. That happens because electrons are on a fermi condensate, and all the low energy states are ocupied. They don't follow the Boltzman distribution at all.
Looks more like L1 cache to me.