Yeah, but the fact that it took Dell five additional years could also be interpreted in the way that the introduction of the iMac wasn't really that groundbreaking. The same could be said about the 3.5" floppy drive -- they continued to be included in many PCs for many years after that, and the real killer there was reasonably the CD writers and (USB!) flash drives, in addition to very widespread networking. The original iMac didn't have a CD writer, and as small USB flash memories were non-existent, I would argue that they were too early. (BTW, I hope no one would say that the original Macintosh killed the 5.25" floppy...)
Flash might give you better latency than a HD. It's a very far shot from a proper DRAM memory controller, if only so due to the fact that it will be connected by the SATA bus. Hey, any data transfer from flash will need to go through DMA! If the problem is not inherently serial, latency is very expensive and even the hughest CPU cache might help little. The fact that he uses Matlab also (might) indicate that this prototyping, or at least "once-off" analysis. You don't want to optimize heavily for memory locality and VM-friendly prefetching if you can just throw more hardware at the problem and get a solution.
Windows 1.0 also had a taskbar with active (minimized) apps. In function, I think it even could be classified as a tad more similar to what 95 provided relative to CDE. The CDE taskbar is after all more of a launcher and a "tray" equivalent, rather than the mundande list of running tasks.
Not with aggressive enough down-clocking (depending on the methodology used for counting used time). I think the original example was a P4, with quite limited abilities in that regard, but it's certainly something that needs to be considered. Even with a correct cycle counter used for estimating idle time, the power state transitions will, on their own, inflate the CPU usage when it's basically idle. A somewhat benign background task could then give numbers like this. One reason to at least consider this is that Vista will turn Speedstep/Cool'n'Quiet and similar features ON by default, while they defaulted to OFF on XP desktops.
As noted in russlar's post, that episode is one DS9 episode I wouldn't be the least bit embarassed about remembering. I generally call bullshit on the claims that DS9 is superior by being darker and more real, but here is one of the few episodes where that overall idea really shines. Depending on the mood, you can actually feel bad about feeling that the episode ended "well".
It's a matter of making the equations nicer. If it seems like matter in a significant way (i.e. gravity, possibly weak interactions, but no electromagnetic ones), it makes sense to call it matter and add it as matter in the equations, rather than adding it as an independent second-order correction or something that just happens to coincide...
They detect metal quite well. Reactive sodium is generally in the metal state. It's not like you can create a fire with salt, salt is what you get when you put the fire out.
Seagate gets to 1 TB with a lower number of physical platter( side)s. They all fit in 3,5-inch enclosures, but that still doesn't make them equal. However, equating reliability with (lower) platter density is quite strange, especially when we get into the matter of one manufacturer using perpendicular recording.
That's not the only thing to take into account. As it is a coating, things like (off the top of my head) different thermal expansion coefficients and the thickness of the actual coating might mean that sapphire is the better choice.
There is a theoretical possibility of negative temperatures (states where you see a higher population in more energetic states, despite their multiplicity). In this specific context, it should be noted that infinite positive and infinite negative temperature will be asymptotically identical, i.e. uniform distributions. It's all about Beta being a more natural metric than T.
Are you sure that you're not simply comparing apples against oranges? (Any app running under Aero, x64 or otherwise, will report a really huge VM size relative to XP.) I've no real problems with WOW64, not in XP x64, and not in Vista.
GCC targets everything and still is more heavily optimized for x86. Despite that, it's FAR from the best x86 compiler around, performance-wise. The pool of people with a "can read, cannot write it good without great pain" grasp of x86 assembler is also damn huge.
Other x86-specific assumptions inherent in code (like atomic writes of different sizes, context switches limited to instruction boundaries) means that a platform porting of seemingly good multithreaded code can cause very subtle bugs. It's even possible to write Java code that is almost impossible to turn into a race condition on x86, but where you might do it on other platforms. You might argue that it's rare or that the code is "bad" and incorrect in the first place, but it's still there.
I don't agree about mathematical proofs in wikibooks. Proofs for individual theorems only rarely require a book-sized volume of text. It also makes little sense to collect proofs of separate theorems into "books", or about as much sense as collecting articles on different subjects into an encyclopedia. Maybe there should be a separate wiki namespace equivalent to Mathworld, but proof of central math theorems certainly should be readily available from wikipedia.
500 contiguous lines or 500 lines in total? I would doubt your guesstimate for the former, while the latter seems far more believable. After all, it would be enough to have 50 ten-line snippets found in forums describing solutions to specific issues to get that number.
Now, I am a complete idiot here, but isn't there some quite high-profile open-source projects where the normal source distribution doesn't include artwork or other material that's needed to build a properly branded version?
The changes from the more cataclysmic cooling events, whether by giant volcano eruptions or impact events, can and would probably be far more rapid. Historically observed eruptions have only given significant effects (rather than just a small semi-permanent change in atmospheric content) the first year, but even for a larger one with decade-long effects, the most significant changes would come within a year.
There are several other viruses that are affected to some degree by drugs, e.g. Tamiflu and many others. The main problem is that one generally wants to hit early in the lifecycle, as the point is to stop the exponential growth. The other problem is that treatment by for example interferone can certainly help against several viral infections (but, again, you would generally need to administer it before you see any symptoms), but it would frequently also cause worse effects than the original disease.
The special advantages of Python are kind of similar to the special advantages of C or Java in this regard: you don't need a special interface to interact with a total wealth of existing code. If the core logic can be expressed with equal consistency and productivity in two languages, go for the one with the best toolset and highest acceptance.
Small-to-medium generally tends to go up to the range of low hundreds. The less-than-ten people businesses won't account for a that large percentage of the total employment in most economies.
Slashdot Mirror
Yeah, but the fact that it took Dell five additional years could also be interpreted in the way that the introduction of the iMac wasn't really that groundbreaking. The same could be said about the 3.5" floppy drive -- they continued to be included in many PCs for many years after that, and the real killer there was reasonably the CD writers and (USB!) flash drives, in addition to very widespread networking. The original iMac didn't have a CD writer, and as small USB flash memories were non-existent, I would argue that they were too early. (BTW, I hope no one would say that the original Macintosh killed the 5.25" floppy...)
That's what Office 2003 used to do. Click-yes syndrome is a dangerous thing.
Better up, they could right-click and unhide them!
OS/2? The 80s called and they really want your 10 MB HPFS partition back.
Flash might give you better latency than a HD. It's a very far shot from a proper DRAM memory controller, if only so due to the fact that it will be connected by the SATA bus. Hey, any data transfer from flash will need to go through DMA! If the problem is not inherently serial, latency is very expensive and even the hughest CPU cache might help little. The fact that he uses Matlab also (might) indicate that this prototyping, or at least "once-off" analysis. You don't want to optimize heavily for memory locality and VM-friendly prefetching if you can just throw more hardware at the problem and get a solution.
Windows 1.0 also had a taskbar with active (minimized) apps. In function, I think it even could be classified as a tad more similar to what 95 provided relative to CDE. The CDE taskbar is after all more of a launcher and a "tray" equivalent, rather than the mundande list of running tasks.
Not with aggressive enough down-clocking (depending on the methodology used for counting used time). I think the original example was a P4, with quite limited abilities in that regard, but it's certainly something that needs to be considered. Even with a correct cycle counter used for estimating idle time, the power state transitions will, on their own, inflate the CPU usage when it's basically idle. A somewhat benign background task could then give numbers like this. One reason to at least consider this is that Vista will turn Speedstep/Cool'n'Quiet and similar features ON by default, while they defaulted to OFF on XP desktops.
As noted in russlar's post, that episode is one DS9 episode I wouldn't be the least bit embarassed about remembering. I generally call bullshit on the claims that DS9 is superior by being darker and more real, but here is one of the few episodes where that overall idea really shines. Depending on the mood, you can actually feel bad about feeling that the episode ended "well".
It's a matter of making the equations nicer. If it seems like matter in a significant way (i.e. gravity, possibly weak interactions, but no electromagnetic ones), it makes sense to call it matter and add it as matter in the equations, rather than adding it as an independent second-order correction or something that just happens to coincide...
They detect metal quite well. Reactive sodium is generally in the metal state. It's not like you can create a fire with salt, salt is what you get when you put the fire out.
You don't see any sampling problems in the very definition of the situations where civilians intervene, versus police?
Seagate gets to 1 TB with a lower number of physical platter( side)s. They all fit in 3,5-inch enclosures, but that still doesn't make them equal. However, equating reliability with (lower) platter density is quite strange, especially when we get into the matter of one manufacturer using perpendicular recording.
That's not the only thing to take into account. As it is a coating, things like (off the top of my head) different thermal expansion coefficients and the thickness of the actual coating might mean that sapphire is the better choice.
There is a theoretical possibility of negative temperatures (states where you see a higher population in more energetic states, despite their multiplicity). In this specific context, it should be noted that infinite positive and infinite negative temperature will be asymptotically identical, i.e. uniform distributions. It's all about Beta being a more natural metric than T.
How is that possible under the original Intel Core CPUs? Or do you mean PAE mode? (which is far from actual 64-bit page tables)
Are you sure that you're not simply comparing apples against oranges? (Any app running under Aero, x64 or otherwise, will report a really huge VM size relative to XP.) I've no real problems with WOW64, not in XP x64, and not in Vista.
Other x86-specific assumptions inherent in code (like atomic writes of different sizes, context switches limited to instruction boundaries) means that a platform porting of seemingly good multithreaded code can cause very subtle bugs. It's even possible to write Java code that is almost impossible to turn into a race condition on x86, but where you might do it on other platforms. You might argue that it's rare or that the code is "bad" and incorrect in the first place, but it's still there.
I don't agree about mathematical proofs in wikibooks. Proofs for individual theorems only rarely require a book-sized volume of text. It also makes little sense to collect proofs of separate theorems into "books", or about as much sense as collecting articles on different subjects into an encyclopedia. Maybe there should be a separate wiki namespace equivalent to Mathworld, but proof of central math theorems certainly should be readily available from wikipedia.
500 contiguous lines or 500 lines in total? I would doubt your guesstimate for the former, while the latter seems far more believable. After all, it would be enough to have 50 ten-line snippets found in forums describing solutions to specific issues to get that number.
Now, I am a complete idiot here, but isn't there some quite high-profile open-source projects where the normal source distribution doesn't include artwork or other material that's needed to build a properly branded version?
The changes from the more cataclysmic cooling events, whether by giant volcano eruptions or impact events, can and would probably be far more rapid. Historically observed eruptions have only given significant effects (rather than just a small semi-permanent change in atmospheric content) the first year, but even for a larger one with decade-long effects, the most significant changes would come within a year.
The badass feature of displaying video tiled between monitors (and for that matter, accelerated video on the secondary monitor) properly!
There are several other viruses that are affected to some degree by drugs, e.g. Tamiflu and many others. The main problem is that one generally wants to hit early in the lifecycle, as the point is to stop the exponential growth. The other problem is that treatment by for example interferone can certainly help against several viral infections (but, again, you would generally need to administer it before you see any symptoms), but it would frequently also cause worse effects than the original disease.
The special advantages of Python are kind of similar to the special advantages of C or Java in this regard: you don't need a special interface to interact with a total wealth of existing code. If the core logic can be expressed with equal consistency and productivity in two languages, go for the one with the best toolset and highest acceptance.
Small-to-medium generally tends to go up to the range of low hundreds. The less-than-ten people businesses won't account for a that large percentage of the total employment in most economies.