They're doing the same thing on Fire Island. From what I heard, they were planning to run FiOS before Sandy, so I imagine this is just a stop-gap.

Which would be fine, save for one problem: their coverage *sucks* out there. When the summer season hits in less than a month, we're screwed.

This is what happens when the greatest city in the world lets a jackal co-opt a third term.

Here's something you can do in your own home, or in some lucky offices:

1) Go to the refrigerator.
2) Open it and look inside.
3) Wow! You can see everything in the refrigerator in 3D! Do you care?
(Um, no... )
4) Okay, don't run away just yet. Notice the tasty beverages inside. Don't you think you deserve one?
(Um, sure...)
5) Reach in, grab one, and enjoy a beverage!
(Cool!)
6) You did that with your ability to view the world in 3D! Cool?
(Um, yeah, I guess...)

See, 3D matters a lot for humans because we need it quite a bit to interact with the world: to drive, to walk down stairs, to grab tasty beverages without spilling them.

But we don't need it to just watch things happen. It doesn't really matter then. If you think it would be cool to watch sports in 3D, just do this:

1) Attend a baseball game live
2) Wait for a someone to hit a long fly ball
3) Watch as half the stadium, who are watching it in 3D, jump up like that ball "is out of here".
4) Watch as outfielder catches it eight feet in front of the warning track. Whoops, silly us.

Even watching sports in 3D doesn't really enhance much; it only matters to the people who *actually have to interact with the ball*.
 

For me it means a website constantly under load and a pager just waiting to bounce off of the desk. Where's that option?

As it turns out, we has rolled out Symantec Endpoint Protection to a few boxes, which causes this response.

Is anybody getting any responses like this: Error running NetPathCanonicalize an if so, how would you interpret it?

Can we not lose sight of the issue? (Insert obligatory slashdot culture joke here).

Whether or not the site is busted or Opera is busted, while obviously quite relevant, is secondary. What's sticking in this guy's craw is that this Mac Daniel troll didn't even have a clue where the problem was, he just went into his go-get-a-real-browser routine right out of the box.

Believe me, "It's your browser's fault, not ours" is a perfectly valid answer once you can back it up.

Someone points out that just because you code to standard doesn't mean it'll work in all browsers. True. But that's why you code to standards. So when this happens, you take a frigging second to trace down the problem, and if it's because Opera isn't executing the standard properly, you can assert that with confidence and tell them to take it up with the browser dev team.

If everytime someone breaks a standard we just stop coding to it all together, we may as well get rid of standards, becuase someone is always going to break them. At least until we nuke Redmond from space.

But again, I doubt that's even the primary issue here, because I seriously doubt by his tone that Mac Daniels even thought about this. He simply heard Opera and reacted like your standard forum jackhole, and this guy smacked that garbage off the playground. Good for him.