Isn't it likely that if the phone calls were spread out over time, they would be more likely to be forgotten and underestimated? If the previous phone call about an issue was a few days ago, you might not really link the two in your mind and figure out the strong support for an issue. If they all come at once, it's relatively easy to notice that there is strong support for an issue - you've been dealing with people who care about it all day.
Yeah, in retrospect, having more than one maskable interrupt level would be nice, but that would have meant more pins into the CPU and a redo of the bus controller. The 8086 (and later, probably) had a daisy-chainable interrupt controller, with 8 interrupts per chip, with a possibility of 8 chips - for a possibility of 249 hardware interrupts (each additional chip needs an interrupt line to itself). That wasn't Microsoft's fault either, but it seems that we could have had a much easier time with just one or two more interrupt controllers.
Target Alert sounds like an utter bullshit extension to me, it's trivial to achieve this with a user style sheet, I wouldn't be surprised if this is exactly what it does. Trivial, maybe, but it saves time for most users who would want to do this, including the users who otherwise wouldn't know how. It's not like it's costing anybody money.
Polish definitely helps, but other factors can override it. Most people would agree that OS X has more polish than Windows, but Windows has done better.
Re:Yet another library for an obsolete language
on
APR 1.0.0 Goes Gold
·
· Score: 2, Interesting
Unfortunately, a problem with g++ is (for Linux developers) a problem with c++. There aren't many alternatives, so while g++ may not be a shining example of how c++ can be, it's a good example of how it is. It makes sense to consider the available compilers when deciding whether to use the language (and also partially when bashing the language - if it's impossible to write a good compiler for, it's likely to be hard to write code in - due to complexity).
Of course they answered "Windows." Microsoft said that windows is the browser, and the browser is Windows, and they can't be separated. If Microsoft can't distinguish between them, can you expect the average computer user to?
I don't know if the firmware would be the same on the exported players. The firmware might be modular, and by removing VP6 support they could triple their profits ($1 -> $3). It's be unlikely that VP6 will be used extensively outside of China, I think.
a flood of DVD players in the USA that also support VP6
Ahh, but they would still have to license MPEG-2, or those wouldn't be DVD players and would be useless for playing normal DVD's. It does make sense to license VP6 rather than H.264 (HD-DVD) because H.264 would probably cost more to license (unless H.264 licenses would somehow be bundled (for only $1 extra) with MPEG-2 licenses).
Yeah, I heard that when the finally disconnected the Service Module (for re-entry) and saw how big the hole was, they were pretty much praying that their heat shield hadn't been broken.
Microsoft has been headed by Billy G. (generally) for the last 29 years. Linux has been headed by Linus (generally) for the last 13 years. That's the relevance: within one organization you would expect to see continuity of character and action. The organizations have their own cultures that give them continuity.
Linux's culture does not exactly date back to the beginning of Unix - many people that were involved in early Unix (Ritchie, Thompson) are not involved in Linux. Many (though not all) of the people who were involved in the beginning of Microsoft are still involved.
XP was put out by the same people that put out NT, 95/98 and DOS. Remember that we weren't comparing DOS and XP patch strategies, we were comparing XP and NT 4.0 patch strategies. Are you willing to claim that Microsoft has changed completely since the days of that NT patch, and that their past actions are completely unrelated to and have no bearing upon their current actions? With Linux, that's plausible - it's had a lot more time, relatively, to develop, whereas Microsoft has had relatively less. Microsoft was already getting fixed in its ways; Linux has been more dynamic.
Are you willing to say that Linux 0.0.1 (terminal emulator/os) is as similar in design, concept, and completeness to Linux 2.6.7 (full-fledged Unix work-alike, server and possibly desktop kernel) as Windows 3.0 (GUI system running on DOS) is to Windows XP (GUI system replacing DOS)?
I find it to be imposing values about how to best visually present grouping that I might not always agree with, and thus I just can't get behind it.
I'm curious - how often do you see good code where the indentation is not connected to control-flow? Much of the (C, etc.) code I've looked at, you could use whitespace-based flow control, and the program would act the exact same way as with braces.
Looks like you'd need differently-polarized LCD monitors-one horizontally, and one vertically. You could place the monitors themselves differently - horizontally and vertically - but that would reduce the usable screen space.
Quite true - IIRC the Sojurner probe ran VxWorks. From what I heard, VxWorks was even part of the reason for a computer problem they had (not sure of the details). Not as bad as the Spirit problem, though.
There's the link tag for html headers, which specifies the next page, previous page, and things like that. It's not prioritized, but if it's used, it can give a good idea of what the user will do.
In retrospect, I realize that you might be talking about the kids referred to in the story, and not those that your post's grandparent metioned.
The really interesting part is that these were children with no language at all, and they've invented one on their own.
So you're saying that these kids didn't speak with their parent(s) at home, and just grunted and pointed until they worked out this language?
Or unmanned/automated flights.
Isn't it likely that if the phone calls were spread out over time, they would be more likely to be forgotten and underestimated? If the previous phone call about an issue was a few days ago, you might not really link the two in your mind and figure out the strong support for an issue. If they all come at once, it's relatively easy to notice that there is strong support for an issue - you've been dealing with people who care about it all day.
oxygenated water
Hydrogen peroxide (H2O2, with more oxygen than water, H2O), I expect.
That would make it even easier to block spammers, with less worry about collateral damage.
Yeah, in retrospect, having more than one maskable interrupt level would be nice, but that would have meant more pins into the CPU and a redo of the bus controller.
The 8086 (and later, probably) had a daisy-chainable interrupt controller, with 8 interrupts per chip, with a possibility of 8 chips - for a possibility of 249 hardware interrupts (each additional chip needs an interrupt line to itself). That wasn't Microsoft's fault either, but it seems that we could have had a much easier time with just one or two more interrupt controllers.
Target Alert sounds like an utter bullshit extension to me, it's trivial to achieve this with a user style sheet, I wouldn't be surprised if this is exactly what it does.
Trivial, maybe, but it saves time for most users who would want to do this, including the users who otherwise wouldn't know how. It's not like it's costing anybody money.
Polish definitely helps, but other factors can override it. Most people would agree that OS X has more polish than Windows, but Windows has done better.
Unfortunately, a problem with g++ is (for Linux developers) a problem with c++. There aren't many alternatives, so while g++ may not be a shining example of how c++ can be, it's a good example of how it is. It makes sense to consider the available compilers when deciding whether to use the language (and also partially when bashing the language - if it's impossible to write a good compiler for, it's likely to be hard to write code in - due to complexity).
Of course they answered "Windows." Microsoft said that windows is the browser, and the browser is Windows, and they can't be separated. If Microsoft can't distinguish between them, can you expect the average computer user to?
But then you lose the advantage of jpegs, i.e. lossy, space-saving compression.
Did you know that you would have to take 1,000,000 pictures a day to fill up a 100 terabyte disk in one lifetime?
What about with my spiffy 1 terapixel camera?
I don't know if the firmware would be the same on the exported players. The firmware might be modular, and by removing VP6 support they could triple their profits ($1 -> $3). It's be unlikely that VP6 will be used extensively outside of China, I think.
a flood of DVD players in the USA that also support VP6
Ahh, but they would still have to license MPEG-2, or those wouldn't be DVD players and would be useless for playing normal DVD's. It does make sense to license VP6 rather than H.264 (HD-DVD) because H.264 would probably cost more to license (unless H.264 licenses would somehow be bundled (for only $1 extra) with MPEG-2 licenses).
Yeah, I heard that when the finally disconnected the Service Module (for re-entry) and saw how big the hole was, they were pretty much praying that their heat shield hadn't been broken.
Microsoft has been headed by Billy G. (generally) for the last 29 years. Linux has been headed by Linus (generally) for the last 13 years. That's the relevance: within one organization you would expect to see continuity of character and action. The organizations have their own cultures that give them continuity.
Linux's culture does not exactly date back to the beginning of Unix - many people that were involved in early Unix (Ritchie, Thompson) are not involved in Linux. Many (though not all) of the people who were involved in the beginning of Microsoft are still involved.
XP was put out by the same people that put out NT, 95/98 and DOS. Remember that we weren't comparing DOS and XP patch strategies, we were comparing XP and NT 4.0 patch strategies. Are you willing to claim that Microsoft has changed completely since the days of that NT patch, and that their past actions are completely unrelated to and have no bearing upon their current actions? With Linux, that's plausible - it's had a lot more time, relatively, to develop, whereas Microsoft has had relatively less. Microsoft was already getting fixed in its ways; Linux has been more dynamic.
Are you willing to say that Linux 0.0.1 (terminal emulator/os) is as similar in design, concept, and completeness to Linux 2.6.7 (full-fledged Unix work-alike, server and possibly desktop kernel) as Windows 3.0 (GUI system running on DOS) is to Windows XP (GUI system replacing DOS)?
I find it to be imposing values about how to best visually present grouping that I might not always agree with, and thus I just can't get behind it.
I'm curious - how often do you see good code where the indentation is not connected to control-flow? Much of the (C, etc.) code I've looked at, you could use whitespace-based flow control, and the program would act the exact same way as with braces.
Age of Microsoft: 29 years
7 years as a percentage of Microsoft's age: 24%
Age of Linux: 13 years
7 years as a percentage of Linux's age: 54%
Looks like you'd need differently-polarized LCD monitors-one horizontally, and one vertically. You could place the monitors themselves differently - horizontally and vertically - but that would reduce the usable screen space.
There are mods for UT that have vehicles, so the original engine worked with vehicles.
Quite true - IIRC the Sojurner probe ran VxWorks. From what I heard, VxWorks was even part of the reason for a computer problem they had (not sure of the details). Not as bad as the Spirit problem, though.
Price discrimination is good for the people who couldn't afford to buy something if the company set one price for everyone.
There's the link tag for html headers, which specifies the next page, previous page, and things like that. It's not prioritized, but if it's used, it can give a good idea of what the user will do.
Who knows, maybe they'll come with preinstalled cut-through-flesh buttons for emergencies like this.