Only if they just like to overclock for the sake of overclocking. Even when you overclock the part to its highest (those who went to Tahoe played with AMD hand-picked chips that could overclock to 3GHz, everyone else had problems with stability at even 2.8GHz), it's still outperformed by a non-overclocked mid-ranged Intel part. So, even if some fanboi starts crowing about overclocking their Phenom(inal failure), almost anybody can say "Yeah, but my stock mid-range Intel part is still faster than your OC'd rig".
There's also the issue where you need to explicitly remove your event listeners when you no longer need the object. The listener keeps a reference to the object (via the interface) so even if it goes out of scope or what-have-you, YOU may think you don't have any references to the object but it implicitly does, through the listener you handed to the system. So... if you're using event listeners, make sure you explicitly remove them in your object's destructure... or else you'll end up with a memory 'leak'.
You played inefficiently and in a boring way. You should have jumped in a frigate and flew around in lowsec space (0.4-0.1) for a while.
Eve combat is the only game where I *still* get so hyped on adrenaline that I shake so hard I can't control the mouse. Combat is far more fun when you really got something to lose (or win) rather than just respawning to zerg it again.
As much as it sucks to admit it;), CISC is even interesting in that it is sort of a 'code compression' built-in sometimes. Sometimes, you can load one CISC instruction that does the work of several RISC instructions. The CISC instruction will take up less memory. This means that not only does it take less memory, it takes less cache space, leaving more for other things (more code, more data) and cache space (particularly L1) is still at a premium. Not only that, a fetch of such a CISC instruction is like several fetches that make up the same sequence of RISC instructions.
There's a big gap between the CPU and main memory... taking up less memory for instructions and, in effect, fetching more instructions per fetch cycle can have some benefits.
That being said, there's nothing to prevent you from programming a modern x86 processor in a RISC-like way. It even sometimes has performance benefits. (Some compilers do this already.)
THAT being said... I haven't programmed in assembly in years... I let compilers do that work for me.
I read it that way too... and was wondering if we finally found out why Sony had become a bunch of evil bastards over the past few years and now they might turn around and be good guys.
"Forward looking" is, IMO, kind of silly. By the time your "forward looking" becomes "standard" (or even close to standard), there will be much better devices, for much cheaper prices. "Forward looking" is just ego-saving, elitist version of "early adopter". I'm very glad for many early adopters like yourself, actually. You guys get to experience the bumps, hiccups, and various other issues and iron them out for folks like me who, will eventually spend 1/10 what you paid and have a much better system than what you bought AND you'll end up buying the same system that we bought just so you can be current and have a reasonable working system in the process while early adopting the next big thing to prepare it for us.
Here's to you, Mr. Early Adopter. (Real Men of Genius) You take the early systems with their bugs, incompatibilities, and problems and live with them and deal with them just so you can 'have it' before anyone else. (Yeah, I got it and you don't!) All the while, petting your ego and inflating your self esteme so you can feel better about yourself and elevating yourself above the unwashed masses. (This new device makes me a better person!) After all, you know that directing someone's attention to your new shiny gadget is easy, and it distracts them from finding out about your secret about your junk size. (Awwww... don't look there!) So, here's to you... Mr. Early Adopter. (Real Men of Geniusssssss)
Due to bandwidth limitations of broadcast frequencies, the ATSC and DVB have standardized only the frame rates of 24, 25, and 30 frames per second (1080p24, 1080p25, 1080p30). Higher frame rates, such as 1080p50 and 1080p60, could only be sent over normal-bandwidth channels if a more advanced codec (such as H.264/MPEG-4 AVC) were used. Higher frame rates such as 1080p50 and 1080p60 are foreseen as the future broadcasting standard for production.[3]
Toshiba/Walmart *are* clearing stock, no doubt about it. Rumor has it that Toshiba has another (new) HD-DVD model being released before Black Friday and they want to clear the current stock of the A2s from the shelves/warehouses to make way for the new models. And it is today (11/2) and, yes, I did go get one for $98.
If nothing else, it will certainly put a few thousand more HD-DVD players out in homes in quick order. Every Walmart in the area, from what I hear, has been the same. Long lines and sold out of the HD-DVD players in less than 30 minutes.
Same here. I have one right now that I got for $98. I showed up early (6:50am) and no one was there and they were going on sale at 8am so I went to IHOP and got some breakfast. Showed back up at 7:40 and I was 15th in line:(. At 8am, there were about 50 or so folks in line when they wheeled out a pallet of them (and those cheap laptops) and started handing them out. They didn't have enough to cover the number of people that were in line at the Walmart I was in. Every Walmart around here that I've heard about has been the same (there are at least 5 Super-Walmarts in easy driving range of me).
Yup... we've had code that ran for 7+ days on 1024+ processors to produce one dataset before. What sucks is when on the 6th day of running, you get a segmentation fault or something:(
I think that one run used up a gamer's quota of CPU power for at least 14 days of game play;)
Would this be fun just to see a bunch of people who don't know anything about science trying to answer questions about science? or actually, they'll most likely sidestep the questions. Either that, or they'll explain their policies towards the science in question, which would surely only make all of us angry or something. I don't see much good coming out of this except potentially to expose the candidates' ignorance.
It's not new, except for Intel actually giving it a name and using the name and the procedure for marketing purposes. The DEC Alpha team did it this way, for example.
Produce something like music that appeals to millions of people and you will find it easier to get royalties. And it has to be under 3m30s and contain no difficult words, harmonies or rhythms.
Sounds like most of the music we complain about as sucking today.... contains no difficult words, harmonies, or rhythms. I'm pretty sure I don't want to listen to that kind of music.
Personally, I think some of these RSIs attributed to "typing" are only telling 1/2 the story... I think typing may cause it but it's really "typing with poor form". Do you rest your wrists on the tabletop/desktop while you type? That's poor form... it binds things that need to slide around inside your hand/arm between your bones/muscles and the desktop. Do you wiggle the mouse around resting your wrist on the desktop? That's bad, too, for the same reason.
Similarly, are your wrists flat or does your hand form an angle with your forearm? An angle (particularly with resting your wrists on the tabletop) means that the sliding around bits has to go around corners. Normally, this probably isn't so bad (as long as your wrists aren't on the tabletop) for 'normal' use because your hand/forearms may change angles and such a lot but if you do it while typing, you may spend hours with your wrists bend and binding your sliding bits against the tabletop.
I've been typing (both programming and writing) for nearly 30 years now and have never had an RSI that I know of.
Possibly, but also likely to be 'greed' in that they don't want to deal with the support issues of third-party tools screwing up iPhones and Apple having to foot the bill to replace/fix them.
Besides, they are working on some technology to make web based apps cachable a la GoogleGears or whatever, in which case the apps will run in a sandbox and the main security/protection focus can be on the browser sandbox and the interaction between that sandbox and the system instead of the whole system for third-party stuff.
Your statement is only true IF Apple sold iPhones in those countries, which they don't. So, no... Apple is not currently under any legal obligation to produce unlocked iPhones and, in fact, are legally obligated to NOT release unlocked iPhones.
You don't spend 30+ hours a week staring at the cartoon picture of a guy's ass.
Why are you staring at *any* cartoon picture of any ass instead of looking at what's going on around you? I rarely care what my avatar looks like because I spend almost no time looking at myself in the game because... well... I'm playing the game... not staring at my toon's ass.
I don't see the point. Every problems needs a specific solution and there's enough room for both solutions.
The implication is there that this row amongst the kernel developers may fracture the kernel (and the developers themselves) enough to cause the whole thing to fall apart... not based necessarily on technical issues but on political issues.
Even if there are people around who would pick up the pieces, would any of them gain enough of a following to stabilize the kernel enough to keep the thing together? As soon as the kernel is fractured, you'll not only have different distributions, but have different forks of the kernel, each sapping away a portion of the developer base and will assuredly evolve apart which would cause all kinds of nightmares not only in user land but in kernel land as kernel developers wouldn't be able to spend time on every kernel fork to keep stuff working.
One of Linux's strongest features is that the kernel is somewhat controlled and is the base on which all the other is built. It's a standard and it's one of the main reasons (if not THE main reason) why OSS has gained so much traction in the past decade or so, IMO. As soon as that is fractured and forked, every fork will evolve its own way and cause it's own brand of confusion and sap away resources that used to be used to support a unified front (THE Linux kernel).
Two outcomes... Linux gets better or Linux dies. Either outcome is acceptible and should be to any other OSS "believer" as well. Survival of the fittest and all... even if the fittest isn't Linux.
Actually, it's because people who desire to perform such activities as write malware, write virus software, and write spyware are working. You got your cause-n-effect stuff mixed up there.
Slashdot Mirror
Only if they just like to overclock for the sake of overclocking. Even when you overclock the part to its highest (those who went to Tahoe played with AMD hand-picked chips that could overclock to 3GHz, everyone else had problems with stability at even 2.8GHz), it's still outperformed by a non-overclocked mid-ranged Intel part. So, even if some fanboi starts crowing about overclocking their Phenom(inal failure), almost anybody can say "Yeah, but my stock mid-range Intel part is still faster than your OC'd rig".
Imageon, apply directly to your smartphone.
Imageon, apply directly to your smartphone.
Imageon, apply directly to your smartphone.
There's also the issue where you need to explicitly remove your event listeners when you no longer need the object. The listener keeps a reference to the object (via the interface) so even if it goes out of scope or what-have-you, YOU may think you don't have any references to the object but it implicitly does, through the listener you handed to the system. So... if you're using event listeners, make sure you explicitly remove them in your object's destructure... or else you'll end up with a memory 'leak'.
You played inefficiently and in a boring way. You should have jumped in a frigate and flew around in lowsec space (0.4-0.1) for a while.
Eve combat is the only game where I *still* get so hyped on adrenaline that I shake so hard I can't control the mouse. Combat is far more fun when you really got something to lose (or win) rather than just respawning to zerg it again.
As much as it sucks to admit it ;), CISC is even interesting in that it is sort of a 'code compression' built-in sometimes. Sometimes, you can load one CISC instruction that does the work of several RISC instructions. The CISC instruction will take up less memory. This means that not only does it take less memory, it takes less cache space, leaving more for other things (more code, more data) and cache space (particularly L1) is still at a premium. Not only that, a fetch of such a CISC instruction is like several fetches that make up the same sequence of RISC instructions.
There's a big gap between the CPU and main memory... taking up less memory for instructions and, in effect, fetching more instructions per fetch cycle can have some benefits.
That being said, there's nothing to prevent you from programming a modern x86 processor in a RISC-like way. It even sometimes has performance benefits. (Some compilers do this already.)
THAT being said... I haven't programmed in assembly in years... I let compilers do that work for me.
I read it that way too... and was wondering if we finally found out why Sony had become a bunch of evil bastards over the past few years and now they might turn around and be good guys.
"Forward looking" is, IMO, kind of silly. By the time your "forward looking" becomes "standard" (or even close to standard), there will be much better devices, for much cheaper prices. "Forward looking" is just ego-saving, elitist version of "early adopter". I'm very glad for many early adopters like yourself, actually. You guys get to experience the bumps, hiccups, and various other issues and iron them out for folks like me who, will eventually spend 1/10 what you paid and have a much better system than what you bought AND you'll end up buying the same system that we bought just so you can be current and have a reasonable working system in the process while early adopting the next big thing to prepare it for us.
Here's to you, Mr. Early Adopter. (Real Men of Genius)
You take the early systems with their bugs, incompatibilities, and problems and live with them and deal with them just so you can 'have it' before anyone else. (Yeah, I got it and you don't!)
All the while, petting your ego and inflating your self esteme so you can feel better about yourself and elevating yourself above the unwashed masses. (This new device makes me a better person!)
After all, you know that directing someone's attention to your new shiny gadget is easy, and it distracts them from finding out about your secret about your junk size. (Awwww... don't look there!)
So, here's to you... Mr. Early Adopter. (Real Men of Geniusssssss)
Sorry, 5 from 15, not 5 from 25.
No... it's any 5 from a list of about 25. Here is the link to the form you have to fill out to get them:
Five free HD-DVDs
No, it isn't. You must not have seen the terms 1080p30 and 1080p60 before. 1080p30 is "standard".
From here:
Toshiba/Walmart *are* clearing stock, no doubt about it. Rumor has it that Toshiba has another (new) HD-DVD model being released before Black Friday and they want to clear the current stock of the A2s from the shelves/warehouses to make way for the new models. And it is today (11/2) and, yes, I did go get one for $98.
If nothing else, it will certainly put a few thousand more HD-DVD players out in homes in quick order. Every Walmart in the area, from what I hear, has been the same. Long lines and sold out of the HD-DVD players in less than 30 minutes.
Same here. I have one right now that I got for $98. I showed up early (6:50am) and no one was there and they were going on sale at 8am so I went to IHOP and got some breakfast. Showed back up at 7:40 and I was 15th in line :(. At 8am, there were about 50 or so folks in line when they wheeled out a pallet of them (and those cheap laptops) and started handing them out. They didn't have enough to cover the number of people that were in line at the Walmart I was in. Every Walmart around here that I've heard about has been the same (there are at least 5 Super-Walmarts in easy driving range of me).
Yup... we've had code that ran for 7+ days on 1024+ processors to produce one dataset before. What sucks is when on the 6th day of running, you get a segmentation fault or something :(
;)
I think that one run used up a gamer's quota of CPU power for at least 14 days of game play
Would this be fun just to see a bunch of people who don't know anything about science trying to answer questions about science? or actually, they'll most likely sidestep the questions. Either that, or they'll explain their policies towards the science in question, which would surely only make all of us angry or something. I don't see much good coming out of this except potentially to expose the candidates' ignorance.
It's not new, except for Intel actually giving it a name and using the name and the procedure for marketing purposes. The DEC Alpha team did it this way, for example.
Sounds like most of the music we complain about as sucking today.... contains no difficult words, harmonies, or rhythms. I'm pretty sure I don't want to listen to that kind of music.
Proof of this statement?
They'll be looking at their communities in the eye all the way to the bank.
Personally, I think some of these RSIs attributed to "typing" are only telling 1/2 the story... I think typing may cause it but it's really "typing with poor form". Do you rest your wrists on the tabletop/desktop while you type? That's poor form... it binds things that need to slide around inside your hand/arm between your bones/muscles and the desktop. Do you wiggle the mouse around resting your wrist on the desktop? That's bad, too, for the same reason.
Similarly, are your wrists flat or does your hand form an angle with your forearm? An angle (particularly with resting your wrists on the tabletop) means that the sliding around bits has to go around corners. Normally, this probably isn't so bad (as long as your wrists aren't on the tabletop) for 'normal' use because your hand/forearms may change angles and such a lot but if you do it while typing, you may spend hours with your wrists bend and binding your sliding bits against the tabletop.
I've been typing (both programming and writing) for nearly 30 years now and have never had an RSI that I know of.
Possibly, but also likely to be 'greed' in that they don't want to deal with the support issues of third-party tools screwing up iPhones and Apple having to foot the bill to replace/fix them.
Besides, they are working on some technology to make web based apps cachable a la GoogleGears or whatever, in which case the apps will run in a sandbox and the main security/protection focus can be on the browser sandbox and the interaction between that sandbox and the system instead of the whole system for third-party stuff.
Your statement is only true IF Apple sold iPhones in those countries, which they don't. So, no... Apple is not currently under any legal obligation to produce unlocked iPhones and, in fact, are legally obligated to NOT release unlocked iPhones.
Why are you staring at *any* cartoon picture of any ass instead of looking at what's going on around you? I rarely care what my avatar looks like because I spend almost no time looking at myself in the game because... well... I'm playing the game... not staring at my toon's ass.
The implication is there that this row amongst the kernel developers may fracture the kernel (and the developers themselves) enough to cause the whole thing to fall apart... not based necessarily on technical issues but on political issues.
Even if there are people around who would pick up the pieces, would any of them gain enough of a following to stabilize the kernel enough to keep the thing together? As soon as the kernel is fractured, you'll not only have different distributions, but have different forks of the kernel, each sapping away a portion of the developer base and will assuredly evolve apart which would cause all kinds of nightmares not only in user land but in kernel land as kernel developers wouldn't be able to spend time on every kernel fork to keep stuff working.
One of Linux's strongest features is that the kernel is somewhat controlled and is the base on which all the other is built. It's a standard and it's one of the main reasons (if not THE main reason) why OSS has gained so much traction in the past decade or so, IMO. As soon as that is fractured and forked, every fork will evolve its own way and cause it's own brand of confusion and sap away resources that used to be used to support a unified front (THE Linux kernel).
Two outcomes... Linux gets better or Linux dies. Either outcome is acceptible and should be to any other OSS "believer" as well. Survival of the fittest and all... even if the fittest isn't Linux.
Actually, it's because people who desire to perform such activities as write malware, write virus software, and write spyware are working. You got your cause-n-effect stuff mixed up there.