Or the fact that those high clockrate Prescotts (I don't think they ever made a 3.4GHz Northwood) had shit for branch prediction on their extremely long pipeline, and stalls were merciless.
Actually, you get however much of that memory is split off to userspace. The default on Windows is a 2GB/2GB split. Linux defaults to a 3GB/1GB split, offering more available to the application. In both cases, that is a user-configurable option.
Because various things suddenly take up twice as much memory, and thus require more memory bandwidth to operate at the same speed. In reality, the performance hit is slight, and more than accounted for by the increased register space available to applications properly compiled for x86-64.
Thank you. The people spouting nonsense about 32-bit programming, and how they can't understand why 64-bit computing would be faster (in the x86 world) drive me loony...
To be fair, increased register space is completely independent of 32-bit versus 64-bit processors. It was a much needed architectural improvement that just happened to coincide with the transition. The only direct computational improvement of a 64-bit CPU is when doing 64-bit integer math.
Actually, the x87 FPU has always been 80-bit precision, even on old 32-bit processors. There was no significant improvement in floating point performance between K7 and K8, besides clock rate. 32-bit versus 64-bit only holds relevance for integer math and pointers.
That always pissed me off when trying to load large datasets. I remember buying a pricey, brand new dual-core Opteron and 2GB of memory back in 2005, so I could work on some things at home, and having to reboot into Linux to actually make use of it. Even on XP64, 32-bit applications still fell under the same restriction.
Current intel mainstream desktop CPUs support four DIMMs and current high end high end desktop CPUs support eight DIMMS
Not exactly. Memory controllers support ranks, not DIMMs. One rank is one fully populated bus width. Standard DDR memory controllers are 64-bits wide, and memory modules are typically 8-bits, meaning you have eight modules to a rank. The memory controllers on desktop CPUs typically support two ranks per channel at full speed, and four ranks at reduced speed, so two ranks per double-sided DIMM, and two DIMMs per channel. On the other hand, if you get high density quad-rank DIMMs, then you can only add one per channel.
The GPL restricts what a developer can do with that code. If they make any modifications, and redistribute those modifications, they have to make the whole thing available as source. On the other hand, since you have already differentiated a developer as not an end user, the end user does not care about the source and thus loses nothing they consider valuable when a BSD-licensed chunk of code is reused in a closed source application.
Apple hired one of the original creators of the LLVM compiler, and put him in charge of a team to maintain and develop LLVM. The team working at Apple subsequently wrote and open sourced the Clang frontend for C-like languages (C/C++/ObjC). Clang/LLVM has recently supplanted GCC as the primary tool chain used by FreeBSD.
The anger is towards people claiming this was a terrorist action in response to the events at Waco compound 20 years ago. Until there is some significant evidence showing otherwise, this was just a simple, catastrophic, industrial accident.
That's because you don't squeeze text through. Text messages are placed into what is otherwise wasted padding in the periodic keep-alive packets between your cell phone and the tower. If you are connected, you can send a text message.
Real world efficiency is on the order of 30-35%, and that's for multi-junction GaAs cells that only see use in concentrated solar and space-based power systems. The best crystalline silicon units do in the 20-25% range, and amorphous silicon units do around 15%. Most plants run around 2-3% of conversion of sunlight into biomass, however sugar cane tops the list at close to 10%. Note that's not just chlorophyll activation, but the whole process of using that to drive ion pumps and produce storage molecules.
A 25" VGA monitor would likely be some hulking 100lb beast from SGI capable of 2048x1536, considerably better than some "HD" 1080p display, but that's besides the point. Industry recommended viewing angle for a television is 30, or 56 arcseconds per pixel on a 1920 pixel wide display. 20:20 vision is stated as roughly 60 arcseconds of resolution, although that is expecting a uniformly colored display, rather than one with individual RGB subpixels, as well as a display considerably higher resolution than the resolving limit of the viewer, so even though that is used as the measure for a "retina display", it doesn't really apply.
Anyway, for the sake of comparison, a 25" 4:3 monitor would be 20" wide, for a 12 angle and 67.5 arcseconds per pixel. A 25" 16:9 monitor, which is more likely considering the 640x360 resolution, would be 21.7" wide, for a 13 angle and 73 arcseconds per pixel. That's still decent pixel density for the average computer monitor, but far lower than common for an HD TV.
To be fair, it is a reflex display, focused such that the image it produces appears to be eight feet away. It's not like that was just some arbitrary distance.
This means Silverlight will dynamically adjust the video and audio bitrate so that even users on less-than-fast lines can stream Silverlight video content.
I doubt that Silverlight is anything special in that regard. I would be stunned to learn that it used anything other than a standard codec like vc1 and just switches between a couple of different bit-rate streams that were pre-encoded.
It really has nothing at all to do with Silverlight in the first place. Silverlight is a client-side application. The server decides what bitrate to stream to the client. The server could just as easily send a variable bitrate stream to a Flash or HTML5 player.
Also, a lot of people don't understand that genes only spread when they're evolutionary beneficial to the organism receiving them.
Funny thing, because those people would be correct. Genes spread because that's just what they do. Reproduction spreads genes as far and as fast as possible. If you reproduce, you have spread your genes, so the only way to prevent genes from spreading is to cause sterility. Natural selection is a statistical long game. Over many generations, those genes which are not beneficial will have a slightly lower likelihood of surviving to reproduce, and thus will occur in the population with reduced frequency.
Slashdot Mirror
Or the fact that those high clockrate Prescotts (I don't think they ever made a 3.4GHz Northwood) had shit for branch prediction on their extremely long pipeline, and stalls were merciless.
There is no "31-bit size limit". It's a 32-bit computer, able to access 32-bits, or 4GB, of memory.
Actually, you get however much of that memory is split off to userspace. The default on Windows is a 2GB/2GB split. Linux defaults to a 3GB/1GB split, offering more available to the application. In both cases, that is a user-configurable option.
Because various things suddenly take up twice as much memory, and thus require more memory bandwidth to operate at the same speed. In reality, the performance hit is slight, and more than accounted for by the increased register space available to applications properly compiled for x86-64.
Thank you. The people spouting nonsense about 32-bit programming, and how they can't understand why 64-bit computing would be faster (in the x86 world) drive me loony...
To be fair, increased register space is completely independent of 32-bit versus 64-bit processors. It was a much needed architectural improvement that just happened to coincide with the transition. The only direct computational improvement of a 64-bit CPU is when doing 64-bit integer math.
Actually, the x87 FPU has always been 80-bit precision, even on old 32-bit processors. There was no significant improvement in floating point performance between K7 and K8, besides clock rate. 32-bit versus 64-bit only holds relevance for integer math and pointers.
you're limited to about 1.2GB of heap space
That always pissed me off when trying to load large datasets. I remember buying a pricey, brand new dual-core Opteron and 2GB of memory back in 2005, so I could work on some things at home, and having to reboot into Linux to actually make use of it. Even on XP64, 32-bit applications still fell under the same restriction.
Current intel mainstream desktop CPUs support four DIMMs and current high end high end desktop CPUs support eight DIMMS
Not exactly. Memory controllers support ranks, not DIMMs. One rank is one fully populated bus width. Standard DDR memory controllers are 64-bits wide, and memory modules are typically 8-bits, meaning you have eight modules to a rank. The memory controllers on desktop CPUs typically support two ranks per channel at full speed, and four ranks at reduced speed, so two ranks per double-sided DIMM, and two DIMMs per channel. On the other hand, if you get high density quad-rank DIMMs, then you can only add one per channel.
You only get a sniff for now, if you know what I mean.
Do you mean the person who came up with this shit was huffing glue?
That's not racism. He was deriding your country, not your ethnicity.
The GPL restricts what a developer can do with that code. If they make any modifications, and redistribute those modifications, they have to make the whole thing available as source. On the other hand, since you have already differentiated a developer as not an end user, the end user does not care about the source and thus loses nothing they consider valuable when a BSD-licensed chunk of code is reused in a closed source application.
Apple hired one of the original creators of the LLVM compiler, and put him in charge of a team to maintain and develop LLVM. The team working at Apple subsequently wrote and open sourced the Clang frontend for C-like languages (C/C++/ObjC). Clang/LLVM has recently supplanted GCC as the primary tool chain used by FreeBSD.
Are you counting Boston as two separate explosions, or was there one I missed?
The anger is towards people claiming this was a terrorist action in response to the events at Waco compound 20 years ago. Until there is some significant evidence showing otherwise, this was just a simple, catastrophic, industrial accident.
If it can charge in seconds, then by very definition it has a huge power density. Perhaps you meant energy density?
That's because you don't squeeze text through. Text messages are placed into what is otherwise wasted padding in the periodic keep-alive packets between your cell phone and the tower. If you are connected, you can send a text message.
What the hell is a "sell" phone? Who the hell is Laura, and why does she live like a bird?
Real world efficiency is on the order of 30-35%, and that's for multi-junction GaAs cells that only see use in concentrated solar and space-based power systems. The best crystalline silicon units do in the 20-25% range, and amorphous silicon units do around 15%. Most plants run around 2-3% of conversion of sunlight into biomass, however sugar cane tops the list at close to 10%. Note that's not just chlorophyll activation, but the whole process of using that to drive ion pumps and produce storage molecules.
A 25" VGA monitor would likely be some hulking 100lb beast from SGI capable of 2048x1536, considerably better than some "HD" 1080p display, but that's besides the point. Industry recommended viewing angle for a television is 30, or 56 arcseconds per pixel on a 1920 pixel wide display. 20:20 vision is stated as roughly 60 arcseconds of resolution, although that is expecting a uniformly colored display, rather than one with individual RGB subpixels, as well as a display considerably higher resolution than the resolving limit of the viewer, so even though that is used as the measure for a "retina display", it doesn't really apply.
Anyway, for the sake of comparison, a 25" 4:3 monitor would be 20" wide, for a 12 angle and 67.5 arcseconds per pixel. A 25" 16:9 monitor, which is more likely considering the 640x360 resolution, would be 21.7" wide, for a 13 angle and 73 arcseconds per pixel. That's still decent pixel density for the average computer monitor, but far lower than common for an HD TV.
" I'm not paranoid" yes you are, what you mean to say is that you are not delusional paranoid. Which, based on your post, is also false.
Isn't all paranoia delusional? I thought it stopped being paranoia if everyone actually was out to get you.
The field has been around for several decades. This is merely its first mass market foray.
To be fair, it is a reflex display, focused such that the image it produces appears to be eight feet away. It's not like that was just some arbitrary distance.
It's alright. We've got sparkles.
This means Silverlight will dynamically adjust the video and audio bitrate so that even users on less-than-fast lines can stream Silverlight video content.
I doubt that Silverlight is anything special in that regard. I would be stunned to learn that it used anything other than a standard codec like vc1 and just switches between a couple of different bit-rate streams that were pre-encoded.
It really has nothing at all to do with Silverlight in the first place. Silverlight is a client-side application. The server decides what bitrate to stream to the client. The server could just as easily send a variable bitrate stream to a Flash or HTML5 player.
Also, a lot of people don't understand that genes only spread when they're evolutionary beneficial to the organism receiving them.
Funny thing, because those people would be correct. Genes spread because that's just what they do. Reproduction spreads genes as far and as fast as possible. If you reproduce, you have spread your genes, so the only way to prevent genes from spreading is to cause sterility. Natural selection is a statistical long game. Over many generations, those genes which are not beneficial will have a slightly lower likelihood of surviving to reproduce, and thus will occur in the population with reduced frequency.