Well, they'd have to invent some kind of world-wide web of connected computers first in order for it to be of any value, and that sounds like a lot of work.
That's what we do for SQL Server Reporting Services around here. We don't have an official "required browser" policy - we try to make sure internal stuff works in whatever is popular, primarily IE and Firefox - and quite a lot of us use Firefox. And of course, as nice as Reporting Services is overall, it's an MS product, so it really only works properly with IE*. So those of us that run Firefox typically have IE Tab installed with a rule to automatically switch to IE for our Reporting Services URL. It's a reasonable compromise that's certainly much nicer than loading up IE every time somebody needs to run a report.
*I hear the 2008 R2 release is much better with non-MS browsers, but I haven't had a chance to try this out yet.
I don't know, my iPhone is pretty stinking productive with Jump Desktop, Wyse PocketCloud, iSSH, Junos Pulse, Citrix Receiver, all the Data Glass apps, and Documents To Go, all of which I use on a fairly regular basis. And none of them has ever offered me any Smurf berries, oddly enough.
Though... personally I would just give them a freshly wiped HDD and call it a day, and apologize to the judge and tell them it was b/c of the Sony root-kit on a CD he bought at a thrift store;)
And get thrown in jail for contempt of court and/or perjury. Though with all his asinine grandstanding regarding both iPhone and PS3 hacking, it's certainly not out of the realm of plausibility.
I wouldn't say netbooks are doomed outright - they're nice in the sense that when you need to have a proper laptop for something, you can have one that's smaller. When I do work on a client site, I bring a tiny MSI with me, and it does the job just fine without having to cart some 13"+ monster around town.
But with as much as I'm able to get done from my iPhone, I'm reminded of an old adage from when handhelds like the HP 200LX were at their apex: "A laptop is nice because you can take it with you. A palmtop is great because you will take it with you." Just replace 'palmtop' with 'smart-phone', and it's the same deal. Why worry about bringing my laptop or netbook when I'm already going to have highly functional web browsing, email, remote desktop, VNC, ssh, etc. with me anyway?
Smartphones are toys, and at their current cost, they're not compelling toys for more people. They either need to increase their functionality to match netbooks and laptops or they need to drop in price to be more commensurate with their actual usefulness before they become widely accepted as the norm.
I sure do an awful lot of remote server and database administration from the middle of nowhere using my "toy", then. I almost never bother bringing my laptop with me when I travel these days.
There's such a meter built right in, actually: Settings, General, Usage, Cellular Network Data. Hit Reset when your billing cycle rolls over, and check back in a month.
Or the better part of a day downloading updates, for people like me out in the sticks with coal-powered internet. It's to the point where I've resigned myself to just download the updates at work, throw 'em on a flash drive, and install when I get home, but you can't do that with the game-specific updates.
I want to like the PS3, but Sony makes it so damned hard sometimes. And I'm sure with all these massive security holes being exposed (which I'm not at all opposed to in principal, mind you), I'm sure the updates will just start coming even faster. Hooray.
Came here to say this. I'd probably disagree with him on a lot of points regarding business, and he doesn't seem like the kind of guy I'd hang out with, but as someone who's spent plenty of time in hospitals myself, I hope all goes well.
TCP has to be able to estimate how fast* it can send data, because there's no way it can know definitively the link speed, capacity, and reliability between your system and a remote system. It does this by progressively getting faster until it starts detecting transmission problems between the two systems, at which point it backs off and slows down. Ideally, you hit a nice equilibrium at some point.
On a proper network, if some router along the path is at capacity, either internally, or along one of its outgoing paths, it should drop the packets it can't handle in a timely fashion. This seems counterintuitive at first, but remember that TCP handles the guaranteed transmission already - it will retransmit packets that didn't arrive. If the router is holding these packets in a buffer, and sending them along once the links clear up, i.e. "when it gets around to it", the packets will reach their destination with hugely inflated latency. This in turn confuses TCP, as it can't get a reliable estimate of link capacity, and the whole speed negotiation falls apart. The latency becomes wild and unpredictable as packets are sometimes buffered, sometimes not, but they always reach their destination, so TCP thinks it's sending at an acceptable rate. So now you've got all the endpoints conversing through this router that's claiming, "No problem, I can handle it!" when it really can't, and the problem just compounds itself as the router gets slammed harder and harder.
By getting timely notification of dropped packets, TCP can say, "Oh, I'm transmitting too fast for this link, time to shrink the sliding window and slow down." This both smooths out latency, and minimizes further dropped packets, not just for the two hosts involved, but for everyone else transmitting through the affected routes as well. This is how it's supposed to work, but excessive buffering of packets within routers prevents it from happening.
Moral: Dropped packets are perfectly normal and in fact required for TCP to manage its own speed and latency. Stop trying to buffer and guarantee packet delivery - TCP is handling that already.
(Disclaimer: I'm a DBA, not a network engineer. Feel free to clarify or correct anything I've mucked up.)
* "Fast" in this case means "How many packets should I send at once before stopping to wait for acknowledgment of those packets getting where they're going". "Faseter" equates to "more of them".
I'm fine with that as long as the book opens with a brief preface serving as a linguistic history lesson, explaining specifically what's been changed, and why terms that used to be okay are now generally frowned upon. I think that would be more educational than simply republishing a book full of racial slurs that are widely considered inappropriate these days.
Yeah, but my smartphone can't take a thorough dunking in a river, and walk away completely unharmed. It also won't run for the better portion of a day on a pair of easily-replaceable AA cells. So I needs me a nice rugged GPS.
You know, I've had two Garmins (various eTrex models) and both of them have had issues with powering off under a small amount of G-forces, and the rubber gasket around the outside coming unglued and ruining both the waterproofing and aesthetics. Garmin wanted me to pay $60-80 to have the rubber replaced.
Slashdot Mirror
Yeah, and with all this 2.4 talk from Google, I keep thinking, dude, I've had that version of Lotus 1-2-3 on my HP 200LX for decades now!
I thought items get closer to them. Or is this a relativity thing?
It looks like the mole...
(sunglasses)
...got whacked.
YEEEAAAAAHHHHHHH!
Well, they'd have to invent some kind of world-wide web of connected computers first in order for it to be of any value, and that sounds like a lot of work.
That's what we do for SQL Server Reporting Services around here. We don't have an official "required browser" policy - we try to make sure internal stuff works in whatever is popular, primarily IE and Firefox - and quite a lot of us use Firefox. And of course, as nice as Reporting Services is overall, it's an MS product, so it really only works properly with IE*. So those of us that run Firefox typically have IE Tab installed with a rule to automatically switch to IE for our Reporting Services URL. It's a reasonable compromise that's certainly much nicer than loading up IE every time somebody needs to run a report.
*I hear the 2008 R2 release is much better with non-MS browsers, but I haven't had a chance to try this out yet.
I don't know, my iPhone is pretty stinking productive with Jump Desktop, Wyse PocketCloud, iSSH, Junos Pulse, Citrix Receiver, all the Data Glass apps, and Documents To Go, all of which I use on a fairly regular basis. And none of them has ever offered me any Smurf berries, oddly enough.
And we shall call it Radio Snack.
Personally, I think it's great that the hacking community has found such a reliably loud-mouthed fall guy.
And get thrown in jail for contempt of court and/or perjury. Though with all his asinine grandstanding regarding both iPhone and PS3 hacking, it's certainly not out of the realm of plausibility.
I wouldn't say netbooks are doomed outright - they're nice in the sense that when you need to have a proper laptop for something, you can have one that's smaller. When I do work on a client site, I bring a tiny MSI with me, and it does the job just fine without having to cart some 13"+ monster around town.
But with as much as I'm able to get done from my iPhone, I'm reminded of an old adage from when handhelds like the HP 200LX were at their apex: "A laptop is nice because you can take it with you. A palmtop is great because you will take it with you." Just replace 'palmtop' with 'smart-phone', and it's the same deal. Why worry about bringing my laptop or netbook when I'm already going to have highly functional web browsing, email, remote desktop, VNC, ssh, etc. with me anyway?
I sure do an awful lot of remote server and database administration from the middle of nowhere using my "toy", then. I almost never bother bringing my laptop with me when I travel these days.
Only a Carpathian would come back to life now, and choose Knox City, Texas!
Tasty pick... bonehead!
There's such a meter built right in, actually: Settings, General, Usage, Cellular Network Data. Hit Reset when your billing cycle rolls over, and check back in a month.
Another day, another guy thinking CSRF is something new.
Or the better part of a day downloading updates, for people like me out in the sticks with coal-powered internet. It's to the point where I've resigned myself to just download the updates at work, throw 'em on a flash drive, and install when I get home, but you can't do that with the game-specific updates.
I want to like the PS3, but Sony makes it so damned hard sometimes. And I'm sure with all these massive security holes being exposed (which I'm not at all opposed to in principal, mind you), I'm sure the updates will just start coming even faster. Hooray.
Came here to say this. I'd probably disagree with him on a lot of points regarding business, and he doesn't seem like the kind of guy I'd hang out with, but as someone who's spent plenty of time in hospitals myself, I hope all goes well.
How do I mod something +1 Deeply Horrifying?
I'll attempt to translate.
TCP has to be able to estimate how fast* it can send data, because there's no way it can know definitively the link speed, capacity, and reliability between your system and a remote system. It does this by progressively getting faster until it starts detecting transmission problems between the two systems, at which point it backs off and slows down. Ideally, you hit a nice equilibrium at some point.
On a proper network, if some router along the path is at capacity, either internally, or along one of its outgoing paths, it should drop the packets it can't handle in a timely fashion. This seems counterintuitive at first, but remember that TCP handles the guaranteed transmission already - it will retransmit packets that didn't arrive. If the router is holding these packets in a buffer, and sending them along once the links clear up, i.e. "when it gets around to it", the packets will reach their destination with hugely inflated latency. This in turn confuses TCP, as it can't get a reliable estimate of link capacity, and the whole speed negotiation falls apart. The latency becomes wild and unpredictable as packets are sometimes buffered, sometimes not, but they always reach their destination, so TCP thinks it's sending at an acceptable rate. So now you've got all the endpoints conversing through this router that's claiming, "No problem, I can handle it!" when it really can't, and the problem just compounds itself as the router gets slammed harder and harder.
By getting timely notification of dropped packets, TCP can say, "Oh, I'm transmitting too fast for this link, time to shrink the sliding window and slow down." This both smooths out latency, and minimizes further dropped packets, not just for the two hosts involved, but for everyone else transmitting through the affected routes as well. This is how it's supposed to work, but excessive buffering of packets within routers prevents it from happening.
Moral: Dropped packets are perfectly normal and in fact required for TCP to manage its own speed and latency. Stop trying to buffer and guarantee packet delivery - TCP is handling that already.
(Disclaimer: I'm a DBA, not a network engineer. Feel free to clarify or correct anything I've mucked up.)
* "Fast" in this case means "How many packets should I send at once before stopping to wait for acknowledgment of those packets getting where they're going". "Faseter" equates to "more of them".
I'm fine with that as long as the book opens with a brief preface serving as a linguistic history lesson, explaining specifically what's been changed, and why terms that used to be okay are now generally frowned upon. I think that would be more educational than simply republishing a book full of racial slurs that are widely considered inappropriate these days.
And an idiot workman pounds nails with a pile driver.
Like why are there 4,000-5,000 SR-71 Blackbirds in operation over Arkansas? What do they know that we don't?
(#34685912)
Boom, right outta the park.
Wait, where do I upload the reaction image on this thing?
Yeah, but my smartphone can't take a thorough dunking in a river, and walk away completely unharmed. It also won't run for the better portion of a day on a pair of easily-replaceable AA cells. So I needs me a nice rugged GPS.
You know, I've had two Garmins (various eTrex models) and both of them have had issues with powering off under a small amount of G-forces, and the rubber gasket around the outside coming unglued and ruining both the waterproofing and aesthetics. Garmin wanted me to pay $60-80 to have the rubber replaced.
Maybe it's time to try a Magellan.
Then I'd wager customers will skip the bother and just order online or go somewhere else first. Talk about cutting off one's nose to spite one's face.