Is to avoid corrosion, not for any sound quality. It works well, and gold plating is cheap, so having gold plated HDMI cables (well, connectors) isn't necessarily a bad thing, as long as the cables are still low-cost.
From one of the russo-finnish epics, where a "sampo" (?!) has to be created. A wizard makes some, bizarre, golden, moose-headed boat-like thing, and it bursts out of the forge...
(Tom Servo) "There's a flaming moose on I95..."
(Crow, I think, in Bullwinkle voice) "Rocky! Help me! I appear to be on fire!"
The NetKernel doc says code required is "10x to 100x less than other approaches" which, along with the complete technobabble in the early part of the doc, tells me this is Yet Another Piece O' Nonsense.
I'll start believing when you have a complete working example of an application (not the NetKernel framework) that you can share, in full, with the world, that compares directly with another known piece of software. In the meantime, read Don't let architecture astronauhts scare you.
Except Flash Gordon (the film) KNOWS it's being incredibly silly with those lines, so it's not a bad film, it's camp.
My favorite bit is right at the beginning, after Ming asks for something new and Klytus says something to the effect of "the inhabitants call this, 'Earth'", moments later Ming presses a button that says... Earthquake!
Says "It has been estimated that humans can distinguish roughly 10 million different colors" which is more like what I recall about the average person's color perception. There are also (VERY rare) folks who have the ability to see even more colors than that... 100 million colors or so
The fact that you feel the need to say documentation and code are not two different things is ALSO one of the roots of all evils in IT. While comments like "a = a + 1 # increment a" are less than useless, a document that says "here's what the code is meant to do, it uses the following algorithms to do it, we tried these others but had problems X and Y, and the database tables it uses are A, B, and C" makes life considerably easier. Especially for the folks who come next. For the folks who end up looking at a database with 600 tables and don't know which ones are used by this application and which are used by others. For the folks who decide to work on improving the code and would have gone and done some of the same experimentation you did, wasting their time... or maybe, because you said "we had problems X and Y" they STILL go and do something similar but slightly different.
Documentation helps on almost every level. Code comments may or may not help depending on language and style, but documenting the code from a programmer's perspective is always useful.
I'm as pretentious as the next guy, but, given how few people ever dealt with a commercial cassette, with Dolby C, or had a $1,000 deck, he IS talking about the gear people owned, and you're talking about the gear people DIDN'T.
I've looked at the AppleTV at the Apple store in Chicago, and yeah, it's 640/480 regular iTunes video, highly compressed. On a 40" screen, like a few were, it looks pretty bad. Standard definition looks pretty hideous to me, too, but at least it doesn't usually have obvious compression artifacts, and iTunes video sure does.
And really, you've seen HD and your SD set still looks fine? I wouldn't have an SD in the house, now, as it's positively blurry compared to even basic HD (1280/720). But then, you know, a lot of folks would have heard your $1,000 cassette deck and said "that sound just like my walkman!" (No, really, really really, they would have. I mean, a LOT of folks would have. They might have done better after getting used to the better sound, but at first?)
You're a little off, here. People can most certainly see the difference between 24 frames per second and, say, a 60 frame per second film (i.e., something actually filmed at 60 FPS). (Showscan: How it works talks about an actual application of 60 FPS filming.)
You really should do a little more research than whatever site said "18 fps is all you need!" because that's really, really wrong. Start with http://www.100fps.com/how_many_frames_can_humans_s ee.htm but for real fun, go get AVISynth, VirtualDub, and the MVTools plugin and convert a 24 FPS film to 48 FPS. There'll be some frames that break apart because any such conversion can't be perfect, but even going to 48 FPS for, say, the water running part of "100 Mile Dash" in "The Incredibles" looks much, much smoother, like you're right there watching it... er, if you were a cartoon character anyhow.:) (The jungle scenes become almost abstract as MVTools tries to figure out the interstitial frames, but the parts not in the jungle look gorgeous).
That the regular devices out there update the DISPLAY at 60 hz, that's nothing to do with how many frames of different video are being displayed. 60 Hz display of 24 or 30 FPS film or video, is just flashing the image in front of you twice as fast. Even theaters actually show 24 FPS films at 48 or 72 hz to reduce flicker, but the frame rate is still 24.
That doesn't change the fact that they're releasing code under the license. Not that most folks would care anyway, really, to ever look at the list of contributors. Look, everyone wants credit for their good work, but if the Compiz folks are jealous about Beryl adding 5% work and getting all the glory, think of how the GCC crew must feel about the whole OSS/free software universe.:)
My reply to your father is "only someone actually very old and out of touch would think a phone today is 'just a phone' and only someone relatively poor in today's society would think that $500 is 'a lot' of money. It's not cheap, but compared to a phone and an ipod and a wireless PDA? Please'"
But then, I can't stand my parents, so I'm usually biased when these things come up. Also, of course, I couldn't BE more pretentious...
I don't much care for That's Lobstertainment! at all, but I do love Zoidberg. During one of the Santa Claus episodes, "...and it's his good friend, Jesus!" nearly made me spit out my pancreas. Now that's good humor!
His delivery of "Gracias" in the Single Female Lawyer episode is priceless, as is John DiMaggio's laugh at the line in the commentary. Honestly, he and Billy West should just have a weekly show where try drink a lot, talk about the news, and get blind stinking drunk. I'd pay to see, and hear, that.
Bender: You may have to metaphorically make a deal with the devil. And by "devil," I mean "Robot Devil," and by "metaphorically," I mean "get your coat."
If you come up with a theory of giant winged horses eating your squirrels being the cause of epilepsy, you may be the best person to write about it... but you're also the ONLY person to write about it. It's not wikipedia's job to be the platform for every fringe view in the world.
Slashdot Mirror
Is to avoid corrosion, not for any sound quality. It works well, and gold plating is cheap, so having gold plated HDMI cables (well, connectors) isn't necessarily a bad thing, as long as the cables are still low-cost.
With a few other lawyers and accountants.
So... you're generally playing as Lawful Evil, then?
So... have you seen "The Number 23" by any chance?
From one of the russo-finnish epics, where a "sampo" (?!) has to be created. A wizard makes some, bizarre, golden, moose-headed boat-like thing, and it bursts out of the forge...
(Tom Servo) "There's a flaming moose on I95..."
(Crow, I think, in Bullwinkle voice) "Rocky! Help me! I appear to be on fire!"
I can't begin to tell you how disturbing that is, either way.
The NetKernel doc says code required is "10x to 100x less than other approaches" which, along with the complete technobabble in the early part of the doc, tells me this is Yet Another Piece O' Nonsense.
I'll start believing when you have a complete working example of an application (not the NetKernel framework) that you can share, in full, with the world, that compares directly with another known piece of software. In the meantime, read Don't let architecture astronauhts scare you.
Perhaps you don't like people saying you're being rude, when you don't want to change the behavior.
And that's "you're" you were trying to use when you said "your." "ur" would be acceptable, of course, if we were instant messaging. :)
Except Flash Gordon (the film) KNOWS it's being incredibly silly with those lines, so it's not a bad film, it's camp.
My favorite bit is right at the beginning, after Ming asks for something new and Klytus says something to the effect of "the inhabitants call this, 'Earth'", moments later Ming presses a button that says... Earthquake!
Wikipedia's color article
Says "It has been estimated that humans can distinguish roughly 10 million different colors" which is more like what I recall about the average person's color perception. There are also (VERY rare) folks who have the ability to see even more colors than that... 100 million colors or so
The fact that you feel the need to say documentation and code are not two different things is ALSO one of the roots of all evils in IT. While comments like "a = a + 1 # increment a" are less than useless, a document that says "here's what the code is meant to do, it uses the following algorithms to do it, we tried these others but had problems X and Y, and the database tables it uses are A, B, and C" makes life considerably easier. Especially for the folks who come next. For the folks who end up looking at a database with 600 tables and don't know which ones are used by this application and which are used by others. For the folks who decide to work on improving the code and would have gone and done some of the same experimentation you did, wasting their time... or maybe, because you said "we had problems X and Y" they STILL go and do something similar but slightly different.
Documentation helps on almost every level. Code comments may or may not help depending on language and style, but documenting the code from a programmer's perspective is always useful.
I only wish I could afford the drugs you're obviously taking.
It's already pretty cool. HAHAHAHA I slay me.
I'm as pretentious as the next guy, but, given how few people ever dealt with a commercial cassette, with Dolby C, or had a $1,000 deck, he IS talking about the gear people owned, and you're talking about the gear people DIDN'T.
I've looked at the AppleTV at the Apple store in Chicago, and yeah, it's 640/480 regular iTunes video, highly compressed. On a 40" screen, like a few were, it looks pretty bad. Standard definition looks pretty hideous to me, too, but at least it doesn't usually have obvious compression artifacts, and iTunes video sure does.
And really, you've seen HD and your SD set still looks fine? I wouldn't have an SD in the house, now, as it's positively blurry compared to even basic HD (1280/720). But then, you know, a lot of folks would have heard your $1,000 cassette deck and said "that sound just like my walkman!" (No, really, really really, they would have. I mean, a LOT of folks would have. They might have done better after getting used to the better sound, but at first?)
You're a little off, here. People can most certainly see the difference between 24 frames per second and, say, a 60 frame per second film (i.e., something actually filmed at 60 FPS). (Showscan: How it works talks about an actual application of 60 FPS filming.) You really should do a little more research than whatever site said "18 fps is all you need!" because that's really, really wrong. Start with http://www.100fps.com/how_many_frames_can_humans_s ee.htm but for real fun, go get AVISynth, VirtualDub, and the MVTools plugin and convert a 24 FPS film to 48 FPS. There'll be some frames that break apart because any such conversion can't be perfect, but even going to 48 FPS for, say, the water running part of "100 Mile Dash" in "The Incredibles" looks much, much smoother, like you're right there watching it... er, if you were a cartoon character anyhow. :) (The jungle scenes become almost abstract as MVTools tries to figure out the interstitial frames, but the parts not in the jungle look gorgeous).
That the regular devices out there update the DISPLAY at 60 hz, that's nothing to do with how many frames of different video are being displayed. 60 Hz display of 24 or 30 FPS film or video, is just flashing the image in front of you twice as fast. Even theaters actually show 24 FPS films at 48 or 72 hz to reduce flicker, but the frame rate is still 24.
That doesn't change the fact that they're releasing code under the license. Not that most folks would care anyway, really, to ever look at the list of contributors. Look, everyone wants credit for their good work, but if the Compiz folks are jealous about Beryl adding 5% work and getting all the glory, think of how the GCC crew must feel about the whole OSS/free software universe. :)
My reply to your father is "only someone actually very old and out of touch would think a phone today is 'just a phone' and only someone relatively poor in today's society would think that $500 is 'a lot' of money. It's not cheap, but compared to a phone and an ipod and a wireless PDA? Please'" But then, I can't stand my parents, so I'm usually biased when these things come up. Also, of course, I couldn't BE more pretentious...
I don't much care for That's Lobstertainment! at all, but I do love Zoidberg. During one of the Santa Claus episodes, "...and it's his good friend, Jesus!" nearly made me spit out my pancreas. Now that's good humor!
His delivery of "Gracias" in the Single Female Lawyer episode is priceless, as is John DiMaggio's laugh at the line in the commentary. Honestly, he and Billy West should just have a weekly show where try drink a lot, talk about the news, and get blind stinking drunk. I'd pay to see, and hear, that.
Bender: You may have to metaphorically make a deal with the devil. And by "devil," I mean "Robot Devil," and by "metaphorically," I mean "get your coat."
If you come up with a theory of giant winged horses eating your squirrels being the cause of epilepsy, you may be the best person to write about it... but you're also the ONLY person to write about it. It's not wikipedia's job to be the platform for every fringe view in the world.