It's not the Eee that sucks, it's the web pages you browse. No self-respecting website should be failing at 800 or 640 or 400 or on a cellphone or iPhone or lynx or...
They could be both 'wary' and 'weary'. Imagine you are the crew. Some dope down In R&D keeps sending you idiotic new devices to test (not unlike Q from James Bond). They often fail catastrophically, so you are wary of any particular one. And you get a new batch every damn week, so you are weary of the whole 'being a guinea pig for science' part of your job.
Slashdot Mirror
It's not the Eee that sucks, it's the web pages you browse. No self-respecting website should be failing at 800 or 640 or 400 or on a cellphone or iPhone or lynx or ...
Actually, I'd like to see a patch that hangs MS IE; then the ball would be in their court. Isn't the rule:
A) If the page looks like crap, its the website's fault
B) If the browser crashes, its the browser's fault
Inspecting my internal ruleset, that's what I'm finding.
They could be both 'wary' and 'weary'. Imagine you are the crew. Some dope down In R&D keeps sending you idiotic new devices to test (not unlike Q from James Bond). They often fail catastrophically, so you are wary of any particular one. And you get a new batch every damn week, so you are weary of the whole 'being a guinea pig for science' part of your job.
> 'Bug' as 'Insect'
So you would say "Excuse me a moment, I have to hunt down an insect in my programme"? You don't really?
"Renee is really starting to insect me with her incessant cheeriness."
Nope, I'm not believing in you.