Calling the cones in your eye "red" "green" and "blue" is a gross approximation.
Each covers a range of wavelengths, and it's the difference between them as interpreted by your brain that makes "color".
The "green" cone is stimualted mostly by yellow and green wavelengths (with a peak at a yellow-green color around 540nm)
That same wavelength stimuates the red cone.
If both cones are stimuated about equal, you get yellow, if the green cone is more stimuated than the red cone, green.
Green, at 510 or 510nm, stimuates both cones a lot less than 540nm, but the dropoff for the "red" cone is dramatic, so we interpret this as "green".
Yellow light is the "brightest" satuturated light, because it stimulates R and G cones, so is brighter than saturated colors that stimuate only one cone a lot.
The Green sensor cones in your eye are actually most sensitive around yellow (slightly green of yellow), and yellow also stimuates the Red sensor cones, so yellow looks brighter to us than other saturated colors.
If something is truely Green, it stimulates the Green cone slightly less, and the Red cone a LOT less, so was see it as green.
You say "For example, assume each R-G-B pixel emits light matching the eyes R-G-B sensors peak sensitivity", but the truth is that the sRGB gamut values are not at the points where our cones peak in sensitivity.
the sRGB values are not even close to being saturated.
The are all pulled in (whiter) than the saturated values (pure R, pure G, and pure B from the gamut all excite all three of our cones to some extent). So you can't represent MANY colors in RGB: Anything fully saturated can't be shown correctly. This is most obvious with green colors, where the eyes can see saturated greens very well, but RGB can't encode them (this was intentional... Back in the days of CRT monitors and phosphors, using a very saturated green color phosphor made for very dim TV displays... Using a "brighter" phosphor that was less saturated made TVs looks better to the public.
You are wrong when you say "Clearly, the information isn't lost". It is. You cannot infer the original wavelength(s) of the source from the RGB (or Y-Cb-Cr) encoded values, because it isn't likely to be a single saturated color.
For example, the picture may be of something that was originally yellow (saturated, single wavelength, yellow, let's say). Once converted to RGB, you can't tell the difference between that, and a picture of something that was reflecting/generating Green and Red at the right mixture to give the same RGB value.
Worse, the R, G, and B points from the standard RGB (sRGB, which is what HDTV uses, or it's exactly equivalent Y-Cb-Cr encoding) are not saturated at all.
Each is a mix of multiple colors, matched to what TV phosphors glow at. Each is somewhat more "white" than saturated, especially the green value.
So there is no way to encode a green that is more saturated than R = 0, G = 255, B = 0, even though that isn't a saturated green.
And you can't encode anything that has a higher wavelength than the B of the gamut, or anything lower wavelength than the R of the gamut.
So for example, a photo of a violet (the flower, which actually is the color violet, shorter in wavelength than blue) ends up looking blue.
Very funny... No, I don't feel that way. If I go out in the sun, I use sunblock.
I'm sure some tech geeks never see enough sun to own any, but for the rest of us, it works.
I'm sure some people prefer living in the dark, but most of those don't get enough exersize, and so are worse-off health wise.
So, I just tell me boss that I will be working an hour earlier and leaving an hour earlier, even though other employees that I need to work with will stick to their usual hours? And the customers I need to deal with, I'll just tell them I'll be ending my support an hour earlier each day?
The problem with totally voluntary systems is they only work right if everybody (or the majority) agree, at least when it comes to business.
Daylight savings maximizes the "after-work" daylight time, which is useful for many of us.
Parallel DBMS systems like Teradata, Greenplum, Netezza, etc. have already solved this in the relational DBMS world.
Teradata was doing 10's of Terabytes across many computers 15 years ago, and there are Teradata and Greenplum systems that have many hundreds of terabytes.
There is a large amount of truth in this, even if it does outrage open source proponents.
If you look at the most successful open source projects, they are re-implementations of things originally built closed-source. Examples:
UNIX - a closed-source OS, reimplemented as Linux and BSD.
Web Servers - started closed source, now we have Apache et al.
Development IDEs - started closed source (Borland, Microsoft vstudio, etc), now we have Eclipse etc.
Photoshop - closed source Photo editing, reimplmented in Gimp.
Media players - Started closed-source, now have many open source reimplementations
Databases - System R, DB2, Oracle, all closed-source, inspired MySQL and PostgreSQL open source
Java - started close-source, later became open-source
Mono - reimplementation of.NET close source software
Office Software - (Word, excel, Lotus etc) all closed source, reimplemented as Open Office etc.
Where are the brand-new software ideas that never had closed-source inspiration?
http://www.nema.org/lamprecycle/epafactsheet-cfl.p df
Also, from the lightbulbs that I buy:
All fluorescent bulbs contain small amounts of mercury that is energized by the lamp and in turn causes the phosphors inside the lamp to glow and create visible light. The amount of mercury in a CFL's glass tubing is very small and would fit on the tip of a ball point pen or about 1/750th of that found in an older household thermostat. Inexpensive CFL bulbs, like those found in home improvement and discount stores, contain mercury in elemental form or as mercury vapor which pose a risk of the mercury being released if the bulb is broken. All BlueMax(TM) CFLs are made with special amalgam technology where the mercury content is held within the amalgam fill of the bulb and will not "spill out". This amalgam fill/alloy structure is the same as is used in dentistry for tooth fillings.
BlueMax(TM) CFLs actually present an opportunity to prevent mercury from entering our air, where it most affects our health. The largest source of mercury in our air comes from the burning of coal to produce electricity. A CFL uses 75% less energy than an incandescent light bulb and lasts up to 10 times longer. A power plant will emit 10mg of mercury to produce the electricity to run an incandescent bulb compared to only 2.4mg of mercury to run a CFL over a period of 5 years.
Duh.... That is a diaeresis, not an umlaut.
Diaeresis mark that the vowel in question is a separate syllable from the previous vowel.
Umlauts change the pronunciation of the vowel, and work quite different (but look the same)
One reason COBOL works well is that it supports decimal numbers and decimal arithemetic. No sane financial guy is going to let you use floating point (i.e. Approximate numerics) in financial calculations.
This makes it very difficult to migrate any of the work the COBOL code is doing into other laguages.
What are you trying to teach? VI? Emacs? or are you trying to teach the programming languages? Why make it harder than necessary? Just to slow them down by doing things the 20 year old way? Or just trying to preserve the tradition of doing things the hard way?
If you want to teach the languages, worry about that. They can learn vi and/or emacs if and when they need it.
What stops me from making a fake ID card, that says I'm somebody else, but with MY fingerprints encoded in the card.
So, when I go to use the card, they look at the fingerprint data on the card, compare to my actual fingerprints, and suddenly I've "proved" I'm the right guy.
Windows Media Center looks attractive, but it's missing a must-have for me:
I watch HDTV, and I get it though my cable company.
I can't find any Media Center PCs that will hook up to the cable, and record and play HDTV.
Well, it's just a reasonable to call Aluminum oxide "transparent aluminum" as it is to call Aliminum Oxy-Nitride "transparent aluminum".
Neither are pure aluminum, neither are metals.
Slashdot Mirror
Calling the cones in your eye "red" "green" and "blue" is a gross approximation. Each covers a range of wavelengths, and it's the difference between them as interpreted by your brain that makes "color". The "green" cone is stimualted mostly by yellow and green wavelengths (with a peak at a yellow-green color around 540nm) That same wavelength stimuates the red cone. If both cones are stimuated about equal, you get yellow, if the green cone is more stimuated than the red cone, green. Green, at 510 or 510nm, stimuates both cones a lot less than 540nm, but the dropoff for the "red" cone is dramatic, so we interpret this as "green". Yellow light is the "brightest" satuturated light, because it stimulates R and G cones, so is brighter than saturated colors that stimuate only one cone a lot.
The Green sensor cones in your eye are actually most sensitive around yellow (slightly green of yellow), and yellow also stimuates the Red sensor cones, so yellow looks brighter to us than other saturated colors. If something is truely Green, it stimulates the Green cone slightly less, and the Red cone a LOT less, so was see it as green.
You say "For example, assume each R-G-B pixel emits light matching the eyes R-G-B sensors peak sensitivity", but the truth is that the sRGB gamut values are not at the points where our cones peak in sensitivity. the sRGB values are not even close to being saturated. The are all pulled in (whiter) than the saturated values (pure R, pure G, and pure B from the gamut all excite all three of our cones to some extent). So you can't represent MANY colors in RGB: Anything fully saturated can't be shown correctly. This is most obvious with green colors, where the eyes can see saturated greens very well, but RGB can't encode them (this was intentional... Back in the days of CRT monitors and phosphors, using a very saturated green color phosphor made for very dim TV displays... Using a "brighter" phosphor that was less saturated made TVs looks better to the public.
You are wrong when you say "Clearly, the information isn't lost". It is. You cannot infer the original wavelength(s) of the source from the RGB (or Y-Cb-Cr) encoded values, because it isn't likely to be a single saturated color. For example, the picture may be of something that was originally yellow (saturated, single wavelength, yellow, let's say). Once converted to RGB, you can't tell the difference between that, and a picture of something that was reflecting/generating Green and Red at the right mixture to give the same RGB value. Worse, the R, G, and B points from the standard RGB (sRGB, which is what HDTV uses, or it's exactly equivalent Y-Cb-Cr encoding) are not saturated at all. Each is a mix of multiple colors, matched to what TV phosphors glow at. Each is somewhat more "white" than saturated, especially the green value. So there is no way to encode a green that is more saturated than R = 0, G = 255, B = 0, even though that isn't a saturated green. And you can't encode anything that has a higher wavelength than the B of the gamut, or anything lower wavelength than the R of the gamut. So for example, a photo of a violet (the flower, which actually is the color violet, shorter in wavelength than blue) ends up looking blue.
The Y-Cb-Cr values encoded in HDTV all directly map to RGB values in the standard gamut (sRGB). They can't represent colors outside that gamut.
What would be the point, when the HDTV signal only has RGB? (or Y-Cb-Cr values that map directly to sRGB values, if you prefer)
It doesn't work due to aziotropism. For example, if you have ethanol and water mixed, no amount of distilation can ever completely separate them.
Diesel fuel in the USA is not as clean as in Europe, and the super-high efficiency diesel engines need the cleaner fuel.
MAC is supported as well as Windows... See the website
You seriously think that would be cheaper? Or more pratical?
I'm sure some people prefer living in the dark, but most of those don't get enough exersize, and so are worse-off health wise.
I agree. After work daylight is a boon to all tech workers who rarely get to see the sun otherwise.
http://www.sciencedaily.com/releases/2005/09/050922014720.htm
http://www.foxnews.com/story/0,2933,257921,00.html
http://en.wikipedia.org/wiki/Daylight_saving_time
So, I just tell me boss that I will be working an hour earlier and leaving an hour earlier, even though other employees that I need to work with will stick to their usual hours? And the customers I need to deal with, I'll just tell them I'll be ending my support an hour earlier each day? The problem with totally voluntary systems is they only work right if everybody (or the majority) agree, at least when it comes to business. Daylight savings maximizes the "after-work" daylight time, which is useful for many of us.
Parallel DBMS systems like Teradata, Greenplum, Netezza, etc. have already solved this in the relational DBMS world. Teradata was doing 10's of Terabytes across many computers 15 years ago, and there are Teradata and Greenplum systems that have many hundreds of terabytes.
UNIX - a closed-source OS, reimplemented as Linux and BSD.
Web Servers - started closed source, now we have Apache et al.
Development IDEs - started closed source (Borland, Microsoft vstudio, etc), now we have Eclipse etc.
Photoshop - closed source Photo editing, reimplmented in Gimp.
Media players - Started closed-source, now have many open source reimplementations
Databases - System R, DB2, Oracle, all closed-source, inspired MySQL and PostgreSQL open source
Java - started close-source, later became open-source
Mono - reimplementation of .NET close source software
Office Software - (Word, excel, Lotus etc) all closed source, reimplemented as Open Office etc.
Where are the brand-new software ideas that never had closed-source inspiration?
http://www.nema.org/lamprecycle/epafactsheet-cfl.p df
Also, from the lightbulbs that I buy:
All fluorescent bulbs contain small amounts of mercury that is energized by the lamp and in turn causes the phosphors inside the lamp to glow and create visible light. The amount of mercury in a CFL's glass tubing is very small and would fit on the tip of a ball point pen or about 1/750th of that found in an older household thermostat. Inexpensive CFL bulbs, like those found in home improvement and discount stores, contain mercury in elemental form or as mercury vapor which pose a risk of the mercury being released if the bulb is broken. All BlueMax(TM) CFLs are made with special amalgam technology where the mercury content is held within the amalgam fill of the bulb and will not "spill out". This amalgam fill/alloy structure is the same as is used in dentistry for tooth fillings.
BlueMax(TM) CFLs actually present an opportunity to prevent mercury from entering our air, where it most affects our health. The largest source of mercury in our air comes from the burning of coal to produce electricity. A CFL uses 75% less energy than an incandescent light bulb and lasts up to 10 times longer. A power plant will emit 10mg of mercury to produce the electricity to run an incandescent bulb compared to only 2.4mg of mercury to run a CFL over a period of 5 years.
Duh.... That is a diaeresis, not an umlaut. Diaeresis mark that the vowel in question is a separate syllable from the previous vowel. Umlauts change the pronunciation of the vowel, and work quite different (but look the same)
One reason COBOL works well is that it supports decimal numbers and decimal arithemetic. No sane financial guy is going to let you use floating point (i.e. Approximate numerics) in financial calculations. This makes it very difficult to migrate any of the work the COBOL code is doing into other laguages.
What are you trying to teach? VI? Emacs? or are you trying to teach the programming languages?
Why make it harder than necessary? Just to slow them down by doing things the 20 year old way?
Or just trying to preserve the tradition of doing things the hard way?
If you want to teach the languages, worry about that. They can learn vi and/or emacs if and when they need it.
What stops me from making a fake ID card, that says I'm somebody else, but with MY fingerprints encoded in the card. So, when I go to use the card, they look at the fingerprint data on the card, compare to my actual fingerprints, and suddenly I've "proved" I'm the right guy.
Yes, you are misunderstanding. IA-32 is Itanium native, but 32-bit, code. Not x86 code.
Windows Media Center looks attractive, but it's missing a must-have for me: I watch HDTV, and I get it though my cable company. I can't find any Media Center PCs that will hook up to the cable, and record and play HDTV.
Well, it's just a reasonable to call Aluminum oxide "transparent aluminum" as it is to call Aliminum Oxy-Nitride "transparent aluminum". Neither are pure aluminum, neither are metals.
Transparent Aliminum has been around for all our lifetimes: Sapphire = Aluminum Oxide. My watch has a sapphire crystal... Yours might too.