I always thought that the longest sheduled flight was QF1 - QANTAS' flight from Sydney to London, via HK. Could be wrong, though, and probbably am! I think it was the first really long haul route.
Interestingly, though the cost for a ticket was enoromous, when compared to paying someone wages during a 3 month sea voyage, it was quite cost-effective!
The reason that it didn't happen is that their incredible fuel consumption meant that they couldn't fly a straight trans-pacific route. Having to land and refuel at Hawaii drastically increased both costs and time. The sound issue probably meant that peacefull Hawaii banned them from regular flights anyway. If the Japs can fix both problems, then they may have a economic model. Anyway, who cares: This planet should have a supersonic passenger aircraft, whatever the costs. It's a hollow place without one!
I don't know what country you are from, but I have often thought that the New Zealand-style phone jacks that are often sent with some systems _do_ look faintly like USB plugs....
As you [should] be aware, moderators are just users like you or me. Every now and then a user with a positive karma will get mod points. You can also help by meta moderating, which allows you to review the mod decisions made by others. Then you will also be more likely to get mod points.
So if you don't like how things are moderated, Get on board and help!
I'd say the editors were a little over brief, not incorrect, or illiterate. Although, I cannot pick the difference between the two statements.
CRTs light up a phosphor dots for a very small time (persistance makes this more complex.) That's the idea that the LCD makers are working with.
..the time it takes to respond.
Response times are generally the time taken to go from 100% to 0% - and this is generally the best case. Moving from 20% to 80% is a lot slower (source: arstechnica's ~recent lcd rundown)
0-100 rarely, if ever, occours in nature. (unless you're a cheetah!) The tennis ball problem, from green to yellow, is fairly small - 0dff0f to fdff28 was my guesses: big shift in red, green unchanged, slight blue. Even that big redshift would be reduced in real life.
So, yes, it's a problem. Whether giveing us 50/60hz flicker back is a good idea is, of course, another matter entirely.
It seems obvious that this can affect any OS, and is due to the poor design of USB- If a device posts a number, then the system assumes it's such-and-such, and loads the driver. Which probably has bugs. So, how do We (that is Open Source system developers) deal with this? Of course 1. is to make sure that all drivers in our trees have no overflow bugs. Or any others, or course. This takes work, but we now know that it is needed. You cannot trust any info that a USB device gives us. Shoulda known. Of course, some painful hardware vendors will _insist_ on providing only binary drivers. Am I alone in thinking that running these as root, melding thrse with no less than the system kernel, is unacceptable? So a fast, secure universal usb interface is needed. I know I have ugen in FreeBSD, and I hope it's secure, but is it fast enough for pedantic hardware vendors? What's the linux situation look like? As you are the ones that have been provided with binary USB drivers, what do these look like? And, no, i do not like the idea of running any binary only code. But at least we need to sandbox it off, and reduce it's permissions.
Slashdot Mirror
I always thought that the longest sheduled flight was QF1 - QANTAS' flight from Sydney to London, via HK. Could be wrong, though, and probbably am! I think it was the first really long haul route. Interestingly, though the cost for a ticket was enoromous, when compared to paying someone wages during a 3 month sea voyage, it was quite cost-effective!
The reason that it didn't happen is that their incredible fuel consumption meant that they couldn't fly a straight trans-pacific route. Having to land and refuel at Hawaii drastically increased both costs and time.
The sound issue probably meant that peacefull Hawaii banned them from regular flights anyway.
If the Japs can fix both problems, then they may have a economic model. Anyway, who cares: This planet should have a supersonic passenger aircraft, whatever the costs. It's a hollow place without one!
I don't know what country you are from, but I have often thought that the New Zealand-style phone jacks that are often sent with some systems _do_ look faintly like USB plugs....
As you [should] be aware, moderators are just users like you or me. Every now and then a user with a positive karma will get mod points.
You can also help by meta moderating, which allows you to review the mod decisions made by others. Then you will also be more likely to get mod points.
So if you don't like how things are moderated, Get on board and help!
Should I be worried?
Only if you keep the access point on your head.
Repaet after me : "Inverse square law."
I'd say the editors were a little over brief, not incorrect, or illiterate. Although, I cannot pick the difference between the two statements. CRTs light up a phosphor dots for a very small time (persistance makes this more complex.) That's the idea that the LCD makers are working with.
..the time it takes to respond.
Response times are generally the time taken to go from 100% to 0% - and this is generally the best case. Moving from 20% to 80% is a lot slower (source: arstechnica's ~recent lcd rundown)
0-100 rarely, if ever, occours in nature. (unless you're a cheetah!) The tennis ball problem, from green to yellow, is fairly small - 0dff0f to fdff28 was my guesses: big shift in red, green unchanged, slight blue. Even that big redshift would be reduced in real life.
So, yes, it's a problem. Whether giveing us 50/60hz flicker back is a good idea is, of course, another matter entirely.
It seems obvious that this can affect any OS, and is due to the poor design of USB- If a device posts a number, then the system assumes it's such-and-such, and loads the driver. Which probably has bugs. So, how do We (that is Open Source system developers) deal with this?
Of course 1. is to make sure that all drivers in our trees have no overflow bugs. Or any others, or course. This takes work, but we now know that it is needed. You cannot trust any info that a USB device gives us. Shoulda known.
Of course, some painful hardware vendors will _insist_ on providing only binary drivers. Am I alone in thinking that running these as root, melding thrse with no less than the system kernel, is unacceptable? So a fast, secure universal usb interface is needed. I know I have ugen in FreeBSD, and I hope it's secure, but is it fast enough for pedantic hardware vendors? What's the linux situation look like? As you are the ones that have been provided with binary USB drivers, what do these look like?
And, no, i do not like the idea of running any binary only code. But at least we need to sandbox it off, and reduce it's permissions.
So, what does everyone think can be done?