> When I mentioned 'while upgrading the hard disk from 20MB to 40MB', these all freshers burst out with laughter. I never understood what's so funny about the fact that computers were less powerful years ago. Perhaps a false sense of superiorly, like as if you are using that old equipment right now.
The point is to speed up file sharing and to fit more tracks on portable players.
Reverse your question: unless you think you can hear the difference between FLAC and 192kbps mp3, what's the point of using lossless?
Meanwhile, mp3 offers the following advantages:
1.up and downloads go faster 2.Do I want 100 or 1000 tunes on my portable player? Hmmm tough decision. 3.no need to transcode 4.less space means quicker backups. 5.why waste space unnecessary? 'Because you can' is not a valid answer, it also does not compensate for small dick size.
I always found that (galaga) a frustrating game. On the Amiga I preferred POD (proof of destruction). Super fast mindless action and excellent graphics.
> My last comment is obviously wrong. > But my original meaning still stands. 1.post theory and proof 2.retract proof and state that the theory is still valid.
Well, since there were complains from the/. community about vaporware (if not an actual product) and slashvertizements (if an actual product) we thought it would be an improvement to avoid these and hence introduce the "umbrella concept".
>spell out exactly why you think there is no causative arrangement here What the hell are you talking about, no one said there is no causative arrangement. He said it's not the same as correlation.
From the article: The downside, however, was that the gamers reported more cases of depression and substance abuse than their compatriots. "They may be drawn to use the game to help deal with emotional distress,"
One/. user observes that the misuse of 'abuse' may result in exaggerated conclusions. Two conclusions are mentioned: "Games depress people and are a gateway to drug use!" "Drug use causes depression and can lead to gaming!"
gaming->depression->drug usage drug usage->depression->gaming
A second/. user points out that these conclusions are not necessary valid because correlation is not causation, another possible conclusion is: "Depressed people more likely to self medicate with drugs and computer games!"
depression->gaming+drug usage
I don't see what problem you have with that, even the article seems to support the last conclusion: emotional_distress->gaming
> It's full of exceptionally useful information and tips but no beginners can comprehend it. That's because nobody bothers to read the specs anymore. It's a completely backwards way of working, something like the movie Memento.
five... Unless you and your wife are very bright and plan to breed some smart scientists I thank you for advancing overpopulation and the depletion of oil.
Unless system-memory and bus become a order of magnitude faster than the CPU can handle, sharing system-memory with the GPU will slow down the CPU.
One solution I can envision is to have a second memory bank (like going from dual channel to quad channel). When you move all the memory for CPU to bank 1 and all the texture/geometry to bank 2 then the GPU and CPU do not have to wait for each other. Extra wait cycles are introduced when CPU data spills over into the GPU bank, and vica versa.
Each burger flipper goes through the process of inventing the concept of the burger, kill the cows themselves and go through the process of testing and improving the product until it is ready for mass distribution.
Doom marked the turning point but didn't kill the Amiga. What killed it was the fact that the OS and hardware were effectively frozen: Development of new models was simply too slow to compete with PC.
Anyway, where would further development lead to? Probably to a standard PC motherboard to reap the benefits of cheap PC hardware. The OS would be outdated very soon, so people would replace it by linux and maybe develop some sort of emulator to run the old stuff. No matter how you look at it, it was doomed.
> So why not write it in C in the first place? Then one could really optimize it.
1. C is for real programmers, not for web "programmers".;) 2. The browser still needs to compile the C code, so we might just as well stick with javascript. 3. Since javascript is a web language, I assume that it is easier to use when using it as such.
I very much doubt that GPU's predict and render ahead.
I think you mean that a number of frames are rendered into a FIFO queue, a delay-line. This is ofcourse rendering behind, not ahead. Often three buffers are used (on-screen, next-screen, rendering) because it reduces the time waiting for swapping the front and back buffer.
Having more than 3 buffers smooths the fps but increases lag and does not further reduce cpu idle time.
Slashdot Mirror
> When I mentioned 'while upgrading the hard disk from 20MB to 40MB', these all freshers burst out with laughter.
I never understood what's so funny about the fact that computers were less powerful years ago.
Perhaps a false sense of superiorly, like as if you are using that old equipment right now.
Also stay away from A and E, it appears to do more harm than good. http://well.blogs.nytimes.com/2008/11/20/news-keeps-getting-worse-for-vitamins/
The point is to speed up file sharing and to fit more tracks on portable players.
Reverse your question: unless you think you can hear the difference between FLAC and 192kbps mp3, what's the point of using lossless?
Meanwhile, mp3 offers the following advantages:
1.up and downloads go faster
2.Do I want 100 or 1000 tunes on my portable player? Hmmm tough decision.
3.no need to transcode
4.less space means quicker backups.
5.why waste space unnecessary? 'Because you can' is not a valid answer, it also does not compensate for small dick size.
I always found that (galaga) a frustrating game.
On the Amiga I preferred POD (proof of destruction). Super fast mindless action and excellent graphics.
next month: "sudden increase in sports injuries".
I expected at least a Seinfeld quote somewhere.
> My last comment is obviously wrong.
> But my original meaning still stands.
1.post theory and proof
2.retract proof and state that the theory is still valid.
Interesting concept you have there...
Well, since there were complains from the /. community about vaporware (if not an actual product) and slashvertizements (if an actual product) we thought it would be an improvement to avoid these and hence introduce the "umbrella concept".
>spell out exactly why you think there is no causative arrangement here
What the hell are you talking about, no one said there is no causative arrangement. He said it's not the same as correlation.
From the article:
The downside, however, was that the gamers reported more cases of depression and substance abuse than their compatriots. "They may be drawn to use the game to help deal with emotional distress,"
One /. user observes that the misuse of 'abuse' may result in exaggerated conclusions. Two conclusions are mentioned:
"Games depress people and are a gateway to drug use!"
"Drug use causes depression and can lead to gaming!"
gaming->depression->drug usage
drug usage->depression->gaming
A second /. user points out that these conclusions are not necessary valid because correlation is not causation, another possible conclusion is:
"Depressed people more likely to self medicate with drugs and computer games!"
depression->gaming+drug usage
I don't see what problem you have with that, even the article seems to support the last conclusion: emotional_distress->gaming
i+1 is perfectly valid and when used as a statement i+1; (note the semi column) it may be optimized away by the compiler.
So, from a performance perspective, i+1; is better.
> It's full of exceptionally useful information and tips but no beginners can comprehend it.
That's because nobody bothers to read the specs anymore.
It's a completely backwards way of working, something like the movie Memento.
I think it would be a good idea to limit moderators to one funny point. That will make them think twice before modding up the next lame joke.
five... Unless you and your wife are very bright and plan to breed some smart scientists I thank you for advancing overpopulation and the depletion of oil.
To hear what you're saying when you think no one is listening.
Unless system-memory and bus become a order of magnitude faster than the CPU can handle, sharing system-memory with the GPU will slow down the CPU.
One solution I can envision is to have a second memory bank (like going from dual channel to quad channel). When you move all the memory for CPU to bank 1 and all the texture/geometry to bank 2 then the GPU and CPU do not have to wait for each other. Extra wait cycles are introduced when CPU data spills over into the GPU bank, and vica versa.
Use SHIFT to move the cursor forward/backward.
Absolutely! Burger flippers are very creative.
Each burger flipper goes through the process of inventing the concept of the burger, kill the cows themselves and go through the process of testing and improving the product until it is ready for mass distribution.
Doom marked the turning point but didn't kill the Amiga. What killed it was the fact that the OS and hardware were effectively frozen: Development of new models was simply too slow to compete with PC.
Anyway, where would further development lead to? Probably to a standard PC motherboard to reap the benefits of cheap PC hardware. The OS would be outdated very soon, so people would replace it by linux and maybe develop some sort of emulator to run the old stuff. No matter how you look at it, it was doomed.
> So why not write it in C in the first place? Then one could really optimize it.
1. C is for real programmers, not for web "programmers". ;)
2. The browser still needs to compile the C code, so we might just as well stick with javascript.
3. Since javascript is a web language, I assume that it is easier to use when using it as such.
You don't need Acrobat at all. Use Foxit Reader 2.3. It's instantaneous and has other benefits as well.
I very much doubt that GPU's predict and render ahead.
I think you mean that a number of frames are rendered into a FIFO queue, a delay-line. This is ofcourse rendering behind, not ahead. Often three buffers are used (on-screen, next-screen, rendering) because it reduces the time waiting for swapping the front and back buffer.
Having more than 3 buffers smooths the fps but increases lag and does not further reduce cpu idle time.