I've said the same thing for years about both phones and laptops. Sooner or later they're of a size that is small enough, and continually making components smaller should simply give us more room for more battery capacity. Even if this iPhone 5 gives us similar, or one can hope for slightly better, battery performance compared to the previous model. But one can only imagine how much better it would be if it were still the same size, and all the shrunken components would give us a battery capacity twice that of the previous model.
And why do you care what you look like at that particular time? Same complaints about wearing 3D glasses at a 3D movie are just as senseless. Who cares what you look like? People are watching the movie, not you, weirdo.
Oh, please. That's such an obvious fake. Did you really not notice how the real phone's black background is not anywhere near as dark as the fake phone's black background once it is placed on the table and the overlaid video starts up? Not to mention the overlaid video's boundaries actually being past the fake phone's screen boundaries.
I don't recall ever reading on any PC hardware site anyone claiming that the CPU doesn't matter and all you need is a good graphics card. How on earth did anyone ever successfully submit that story?
I've got CDs I burned sometime in the mid-late 1990's that still work just fine, 1996-1998ish. I don't know why you'd be worried about them not working. They'd possibly degrade and become unreadable if they were in the sun all the time, but how much sun do you think they're going to get in your package?;)
Everything should just be produced/engineered/mastered with the Replaygain 89 dB target in mind. All albums should come out needing zero correction to meet that, leaving all the more dynamic range intact. All TV soundtracks should be that loud, too. Movies used to follow a similar standard, and should again.
Why not simply use a database to store the scan, and to compare the current scan, and replace with the current scan if it is considered a match? Then the issue is gone. Replaced by other IT issues, I suppose. But still...
How many things actually happened in the entire history of commercial flights before the TSA existed? And why do they still exist in light of that? Sheesh.
Wasn't dealing with wireless. The wired connections were being choked down to ~20 Mbps. The annoying thing is, the firmware the ISP provides on the Cisco DPC 3825 (or the device itself?) makes it so wireless connections cannot see any of the wired connections. So things like controlling an iTunes box via my iPhone and the wireless connection were impossible, because the devices couldn't see each other. This was the only reason I tried to keep my Linksys box connected as before. But now I've worked around that by connecting the Linksys to the Cisco via one of the regular connections, and ignoring the WAN connector on the Linksys, and now Linksys wireless clients can see the wired clients just fine, heh. Stupid ISP. "But can your wireless clients connect to the internet? They can? OK, that's all we care about. Any other issues I can help you with?" heh.
I used DD-WRT for years on an old Linksys WRT54GS (I think that's the model) router and it worked great for me. But after upgrading my internet to 100 Mbps I found out it pukes out at around 20.5 Mbps or something like that, haha. Almost wanted to swear at my ISP, and then decided to try plugging straight into the new Cisco modem/router they gave me, and found all the bandwidth I was paying for was there after all. Haha. But plug back into the Linksys and it chokes me back to just over 20 Mbps again. Couldn't believe it.
Firefox is still faster in at least one real-world web app that matters to me. A free GPS smartphone app called Waze lets you edit and make corrections to the map by signing in to your account on their website. Their editor at http://www.waze.com/cartouche/ is where you make these edits, and Firefox is amazingly responsive with this web app. Chrome, on the other hand, has been getting more and more aggravating to use with this app. User input responsiveness has been getting worse and worse ever since Google starting making huge gains in their javascript performance. If I click on a road segment in Firefox it pretty much instantly gets selected and highlighted. There is a very large delay in doing the same thing in Chrome. In Firefox, if I click on some point in the map and drag to move my view of the map, the map starts moving right away. If I do the same in Chrome I get the same glacial delay before it starts moving the map, and every time you drag the mouse before letting go of the mouse button there is the same delay before your movement translates to movement of the map. In fact, any and all user interactions with the app involves an awful lot of delay. And why, I don't know. How come it's perfectly fluid in Firefox, and in Chrome it's an exercise in patience? If Chrome is *that* much faster, why is it an insane amount slower to edit Waze maps with it?
Ever since a buddy of mine gave me his old Logitech Momo force feedback wheel and a 3-month subscription to iRacing last xmas it is the ONLY thing I play now. The most real racing simulator there is, and I can't get enough of it. Every single other game I have has not been loaded even once since, literally. I'm beyond addicted to it now, hehe.
Slashdot Mirror
I've said the same thing for years about both phones and laptops. Sooner or later they're of a size that is small enough, and continually making components smaller should simply give us more room for more battery capacity. Even if this iPhone 5 gives us similar, or one can hope for slightly better, battery performance compared to the previous model. But one can only imagine how much better it would be if it were still the same size, and all the shrunken components would give us a battery capacity twice that of the previous model.
Way to miss the point.
And why do you care what you look like at that particular time? Same complaints about wearing 3D glasses at a 3D movie are just as senseless. Who cares what you look like? People are watching the movie, not you, weirdo.
Oh, please. That's such an obvious fake. Did you really not notice how the real phone's black background is not anywhere near as dark as the fake phone's black background once it is placed on the table and the overlaid video starts up? Not to mention the overlaid video's boundaries actually being past the fake phone's screen boundaries.
I don't recall ever reading on any PC hardware site anyone claiming that the CPU doesn't matter and all you need is a good graphics card. How on earth did anyone ever successfully submit that story?
I've got CDs I burned sometime in the mid-late 1990's that still work just fine, 1996-1998ish. I don't know why you'd be worried about them not working. They'd possibly degrade and become unreadable if they were in the sun all the time, but how much sun do you think they're going to get in your package? ;)
ok, I suppose it's not quite a dupey as it could be. But still, heh.
http://it.slashdot.org/story/12/07/10/2122220/microsoft-revokes-trust-in-28-of-its-own-certificates
Everything should just be produced/engineered/mastered with the Replaygain 89 dB target in mind. All albums should come out needing zero correction to meet that, leaving all the more dynamic range intact. All TV soundtracks should be that loud, too. Movies used to follow a similar standard, and should again.
You mean besides the constant posing Kari Byron does?
Crazy.
If it matches me, it's me, no? So, all of them?
Why not simply use a database to store the scan, and to compare the current scan, and replace with the current scan if it is considered a match? Then the issue is gone. Replaced by other IT issues, I suppose. But still...
Five-year-plan, eh? Why not? Might make progress come even quicker.
How many things actually happened in the entire history of commercial flights before the TSA existed? And why do they still exist in light of that? Sheesh.
Doh! Wasn't logged in for some reason.
http://science.slashdot.org/story/09/10/26/1517242/2012-a-miscalculation-actual-calendar-ends-2220
Thanks for that link!
Yeah, this doesn't surprise me. It is pretty old consumer gear now.
Wasn't dealing with wireless. The wired connections were being choked down to ~20 Mbps. The annoying thing is, the firmware the ISP provides on the Cisco DPC 3825 (or the device itself?) makes it so wireless connections cannot see any of the wired connections. So things like controlling an iTunes box via my iPhone and the wireless connection were impossible, because the devices couldn't see each other. This was the only reason I tried to keep my Linksys box connected as before. But now I've worked around that by connecting the Linksys to the Cisco via one of the regular connections, and ignoring the WAN connector on the Linksys, and now Linksys wireless clients can see the wired clients just fine, heh. Stupid ISP. "But can your wireless clients connect to the internet? They can? OK, that's all we care about. Any other issues I can help you with?" heh.
I was only dealing with wired connections, but no.
I used DD-WRT for years on an old Linksys WRT54GS (I think that's the model) router and it worked great for me. But after upgrading my internet to 100 Mbps I found out it pukes out at around 20.5 Mbps or something like that, haha. Almost wanted to swear at my ISP, and then decided to try plugging straight into the new Cisco modem/router they gave me, and found all the bandwidth I was paying for was there after all. Haha. But plug back into the Linksys and it chokes me back to just over 20 Mbps again. Couldn't believe it.
Whoops, wasn't logged in for some reason.
ok, I did that. I don't know if I described it very well, but here it is anyway. http://code.google.com/p/chromium/issues/detail?id=75734
Firefox is still faster in at least one real-world web app that matters to me. A free GPS smartphone app called Waze lets you edit and make corrections to the map by signing in to your account on their website. Their editor at http://www.waze.com/cartouche/ is where you make these edits, and Firefox is amazingly responsive with this web app. Chrome, on the other hand, has been getting more and more aggravating to use with this app. User input responsiveness has been getting worse and worse ever since Google starting making huge gains in their javascript performance. If I click on a road segment in Firefox it pretty much instantly gets selected and highlighted. There is a very large delay in doing the same thing in Chrome. In Firefox, if I click on some point in the map and drag to move my view of the map, the map starts moving right away. If I do the same in Chrome I get the same glacial delay before it starts moving the map, and every time you drag the mouse before letting go of the mouse button there is the same delay before your movement translates to movement of the map. In fact, any and all user interactions with the app involves an awful lot of delay. And why, I don't know. How come it's perfectly fluid in Firefox, and in Chrome it's an exercise in patience? If Chrome is *that* much faster, why is it an insane amount slower to edit Waze maps with it?
Ever since a buddy of mine gave me his old Logitech Momo force feedback wheel and a 3-month subscription to iRacing last xmas it is the ONLY thing I play now. The most real racing simulator there is, and I can't get enough of it. Every single other game I have has not been loaded even once since, literally. I'm beyond addicted to it now, hehe.