A guess (but nothing else) is that it would also relate to the behavior when you have two interfaces providing theoretical routes to the target address, with different metrics, but one of them turns out to be unreliable. In that case, the strategy chosen by the local machine can clearly influence the result. (If your WLAN is actually more reliable than your cat5 that the cat toyed with yesterday...)
Yeah, therefore the point would be to establish a very detailed baseline for a specific system. That way, you can analyze the exact clock skew between the sound chip and the RTC, timings for specific instructions, etc. Then, it should be possible to detect whether you are suddenly in a VM jail. To detect the jail without ever having seen anything else, that's far harder...
Even though I thought along the same lines, where do you put the existing blue, that won't leave 1/3-pixel-wide black lines across a yellow screen? I can see the black grid around all pixels if I look closely on my TFTs (even the white ones), but I can't make out the black stripes. I can notice that red and blue vertical lines nominally in the same column doesn't line up right in the transition, though. Likewise, there is a slight black patch in between when I bring a large red rectangle next to a green one, but I still do not make out the black lines covering 2/3 of the area within each of them!
Apps are supposed to read and write user data. I can agree that this concept is flawed, it should be much more prevalent that an app defines a manifest or locks down its own token on load time to only be able to access things that really are relevant (possibly with some special breakout directly connected to the file chooser widget of choice). This is not common in any OS today. Most web browsers run with the full permissions of the user running them, enough to make it very hard for that user to create a botnet node or whatever. There are exceptions to this, but they are rare.
Permissions should always be a result of both the code that's running, and the user that runs it. Specific executables might get extra permissions relative to the baseline of the user (i.e. sudo access for a limited subset of binaries and scripts), but the other way round is far more important: defence in depth by making sure that programs that have no reason to access everything you have access to are indeed denied that access once they are compromised. IE in Vista is one example of this, but it's far from perfect. After all, we want the user to be able to download files, and once we've hijacked the browser process address space, we can start playing around with all the cues in the UI that the user is relying on to tell what's happening and what actions to really approve.
There is no reason that projected film should be superior to everything else. Projected film is still just that: projected, i.e. a negative mask hiding part of the light from the projector. The contrast ratio is completely depenendent on the light absorption of the actual film material. A diode with no voltage is very dark indeed, so the real issue is the quality of the driving electronics.
Now, what makes this irrelevant is of course the fact that because of the very nature of this display, the real issue for contrast is not the contrast ratio in a completely dark room, but the actual brightness related to ambient light. When you factor in the ambient light as the real source of light in the black parts, you'll get a different ratio, but this is the only technology where the ambient light, even in a really dark room, is close to the only source of light in the black parts of the picture.
I guess it's a stupid question, but you did have Speedstep enabled on the XP machine, right? The idle CPU usage will increase, with more aggressive frequency scaling (as you measure % of the current maximum). The Vista defaults are far more aggressive than XP defaults (i.e. turned on at all...).
Or he could be attempting to be infinitely insightful, alluding to NT originally being more of an idea of a radically modified OS/2 3.0, so NT 2.0 would be OS/2 2.0...
All formatting options seem affected, except date formatting, BTW (ok, but there you have the leap year thingy...). The date is presented as 2079-06-04, which is "correct". If you select scientific notation or whatever, everything still says 10^5.
I think that was just a joke. I would be highly surprised if it is indeed a compiler bug, but we should naturally not rule it out. From personal experience, I know of bugs in code generation fixed when using SSE intrinsics between 7.1 and 8.0 (I don't know if the latest updates to 2003 will fix these...).
How is that a bug? I often see dates without years mentioned in text. It's convenient to get auto-conversion. Even a user not aware of formatting at all should be able to Undo back to normal.
I agree that the heuristics suitable to English or Swedish date formats might cause trouble in German, but it's not really a bug. I would say it's generally a good thing that some auto-detection is going on, or you would have to specify by hand which cells are numbers, and which are text, even when it's bloody obvious to you as well as the program. Likewise, it probably should see that SOME dates are real dates. (And if you enter "April" alone in a cell, you might also want to do some computations that work on the date as a date.)
It's not obvious that anything will happen, just thanks to the mulitple-words interpretation. Some things actually have probability zero.
Now, I'm not well-versed enough to say anything substantial about spontaneous particle pairs appearing and fixing things, but I think you really need to consider the possibility that at some point (maybe when you were born, maybe yesterday, maybe tomorrow) life according to the path you've experienced so far will, inevitably, lead to your death. Not "almost surely" (limes p -> 0), but simply p(surviving beyond date X) = 0.
We also have the sad part (mentioned when this line of thinking has been presented on/. in earlier posts): there might be an infinite number of universes where you survive, but in a disastrous majority of those, it will be as a maimed and crippled individual in total pain. Somehow, it seems easier to imagine that just a human brain is moved out of harm's way by an (almost) infinitely small chance, than that this happens to the complete body without harm.
So, how do you handle the browser history? Moving to a new page the first time means that the previous page should still be in the history. When you get to the 1000th page, maybe you want to clean up, but strict adherence to your rule doesn't allow that.
Smart pointers are still a smart thing, for all those cases where it really is so simple that it's ok to deallocate when you leave the current scope. It won't stop you from fine-grained control in all the cases where "real" memory management is needed, rather than some simple scratch space that you don't want to allocate on the stack.
Welcome to the world of over-subscription. Exactly how is this different from most DSL providers? (Maybe a tad extreme, but I would bet that the service is good enough most of the time, and most importantly: possibly significantly better latency than dial-up.)
WiMax is slower, generally even slower than 802.11g in good conditions. (But with far greater range.) The range is also related to the issues of what licenses will be required (in different territories). WiMax is no replacement for FastEthernet, 802.11n is closer to be that.
No, although I think my negative total "experience" with my MacBook is also related to the low resolution and cheap 16-bit screen. (That is: I might have appreciated MacOS X on a desktop machine comparable to the one where I normally run Vista.)
In burst (no seeking), not in sequential writing, unless you put multiple blocks in massively parallel configs, something that's generally not done in current consumer SSDs.
You conveniently forget/ignore the story of OpenGL extensions. True, a Rage128 and above will have all the core capabilities, but the game will instead request two different extensions (ATI and nVidia) for the same functionality. Mmmm... nice.
Well, what would stop them from keeping an older version if that's somehow beneficial to them (or make minor changes to a client to disturb the protocol)?
Slashdot Mirror
A guess (but nothing else) is that it would also relate to the behavior when you have two interfaces providing theoretical routes to the target address, with different metrics, but one of them turns out to be unreliable. In that case, the strategy chosen by the local machine can clearly influence the result. (If your WLAN is actually more reliable than your cat5 that the cat toyed with yesterday...)
Yeah, therefore the point would be to establish a very detailed baseline for a specific system. That way, you can analyze the exact clock skew between the sound chip and the RTC, timings for specific instructions, etc. Then, it should be possible to detect whether you are suddenly in a VM jail. To detect the jail without ever having seen anything else, that's far harder...
Even though I thought along the same lines, where do you put the existing blue, that won't leave 1/3-pixel-wide black lines across a yellow screen? I can see the black grid around all pixels if I look closely on my TFTs (even the white ones), but I can't make out the black stripes. I can notice that red and blue vertical lines nominally in the same column doesn't line up right in the transition, though. Likewise, there is a slight black patch in between when I bring a large red rectangle next to a green one, but I still do not make out the black lines covering 2/3 of the area within each of them!
Permissions should always be a result of both the code that's running, and the user that runs it. Specific executables might get extra permissions relative to the baseline of the user (i.e. sudo access for a limited subset of binaries and scripts), but the other way round is far more important: defence in depth by making sure that programs that have no reason to access everything you have access to are indeed denied that access once they are compromised. IE in Vista is one example of this, but it's far from perfect. After all, we want the user to be able to download files, and once we've hijacked the browser process address space, we can start playing around with all the cues in the UI that the user is relying on to tell what's happening and what actions to really approve.
Now, what makes this irrelevant is of course the fact that because of the very nature of this display, the real issue for contrast is not the contrast ratio in a completely dark room, but the actual brightness related to ambient light. When you factor in the ambient light as the real source of light in the black parts, you'll get a different ratio, but this is the only technology where the ambient light, even in a really dark room, is close to the only source of light in the black parts of the picture.
I guess it's a stupid question, but you did have Speedstep enabled on the XP machine, right? The idle CPU usage will increase, with more aggressive frequency scaling (as you measure % of the current maximum). The Vista defaults are far more aggressive than XP defaults (i.e. turned on at all...).
When the cost of the secondary storage unit is larger than the cost of the rest of the machine, it's something of a novelty item.
Or he could be attempting to be infinitely insightful, alluding to NT originally being more of an idea of a radically modified OS/2 3.0, so NT 2.0 would be OS/2 2.0...
As one of the stated intents of GPLv3 is to close several loopholes, I think you should fork if you find the new license important.
All formatting options seem affected, except date formatting, BTW (ok, but there you have the leap year thingy...). The date is presented as 2079-06-04, which is "correct". If you select scientific notation or whatever, everything still says 10^5.
I think that was just a joke. I would be highly surprised if it is indeed a compiler bug, but we should naturally not rule it out. From personal experience, I know of bugs in code generation fixed when using SSE intrinsics between 7.1 and 8.0 (I don't know if the latest updates to 2003 will fix these...).
I agree that the heuristics suitable to English or Swedish date formats might cause trouble in German, but it's not really a bug. I would say it's generally a good thing that some auto-detection is going on, or you would have to specify by hand which cells are numbers, and which are text, even when it's bloody obvious to you as well as the program. Likewise, it probably should see that SOME dates are real dates. (And if you enter "April" alone in a cell, you might also want to do some computations that work on the date as a date.)
Mr. Adams, is that you?
Now, I'm not well-versed enough to say anything substantial about spontaneous particle pairs appearing and fixing things, but I think you really need to consider the possibility that at some point (maybe when you were born, maybe yesterday, maybe tomorrow) life according to the path you've experienced so far will, inevitably, lead to your death. Not "almost surely" (limes p -> 0), but simply p(surviving beyond date X) = 0.
We also have the sad part (mentioned when this line of thinking has been presented on /. in earlier posts): there might be an infinite number of universes where you survive, but in a disastrous majority of those, it will be as a maimed and crippled individual in total pain. Somehow, it seems easier to imagine that just a human brain is moved out of harm's way by an (almost) infinitely small chance, than that this happens to the complete body without harm.
So, how do you handle the browser history? Moving to a new page the first time means that the previous page should still be in the history. When you get to the 1000th page, maybe you want to clean up, but strict adherence to your rule doesn't allow that.
Smart pointers are still a smart thing, for all those cases where it really is so simple that it's ok to deallocate when you leave the current scope. It won't stop you from fine-grained control in all the cases where "real" memory management is needed, rather than some simple scratch space that you don't want to allocate on the stack.
Translation captchas!
Welcome to the world of over-subscription. Exactly how is this different from most DSL providers? (Maybe a tad extreme, but I would bet that the service is good enough most of the time, and most importantly: possibly significantly better latency than dial-up.)
WiMax is slower, generally even slower than 802.11g in good conditions. (But with far greater range.) The range is also related to the issues of what licenses will be required (in different territories). WiMax is no replacement for FastEthernet, 802.11n is closer to be that.
In burst (no seeking), not in sequential writing, unless you put multiple blocks in massively parallel configs, something that's generally not done in current consumer SSDs.
Yeah, but what's the GNU userspace worth on a proprietary kernel?
You conveniently forget/ignore the story of OpenGL extensions. True, a Rage128 and above will have all the core capabilities, but the game will instead request two different extensions (ATI and nVidia) for the same functionality. Mmmm... nice.
Ah, yep, realized that a bit after posting....
Well, what would stop them from keeping an older version if that's somehow beneficial to them (or make minor changes to a client to disturb the protocol)?