People often forget too that downloading at that speed is dependant on hard disk throughput

Only if you're intending to save it to disk. Streaming multiple HD video streams (one for you, one or two for your kids) etc. etc. will use gobs of bandwidth with zero disk activity - and is only going to get larger (3D, 4K-resolution, etc).

Granted, you'd still have plenty of room left over in your gigabit, but I'm sure we'll find something useful to use it for. (Astronomers working from home? :)

True "duct-tape programming" would bind an existing date datatype in (either YYYY-MM-DD HH:MM:SS, or seconds-since-1970).

Duct-tape is not used to build new things, when there are existing things nearby that will do the job. It's used to hold existing things together! :)

I ran both the site and the ad-server used at my last job, so I cared.

Turns out iframes are the solution that works best (I think) - needs things set up slightly more restricted than normal (eg. ad href's must have a target of _top/_parent/_blank, not missing), but otherwise it works great.

Fit-PC2 (Intel Atom) uses only 6W at idle, 8W full load.

Another thumbs-up for the Fit-PC2 here.

2009 called. They want THEIR SUBMARINE back :)

In WP, if you un-italicized a sentence that had been italicized, it wouldn't necessarily remove the old codes, instead inserting extra codes so that you got on's followed immediately by off's. Word would just delete the object.

I've seen huge waste out of Word that says otherwise - objects or streams, Word is just as capable of keeping waste around. Just look at its HTML export as proof. (I haven't looked at it recently, but you're talking about a day-one difference here so I think I'm still justified :)

Sure, except using OpenDNS is opt-in in the first place.

Fully agree. Some of my most-used apps are competitors for built-in ones (Canola and MPlayer top the list, MaemoMapper, I also used Modest in competition with its built-in email some time ago).

...and the existing pool of Gtk+ developers get frustrated after Yet Another API Change, and leave.

There's never going to be the glut of third-party apps that the iPhone enjoys, when the API isn't stable - and you'd have much better luck again if you could keep the ABI stable for more than a year or two...

I really love my N810 in some ways - but in others, it's fallen flat. Can't play full-res video, GPS is slow to lock, the built-in-browser is slow and painful, finger-scrolling doesn't always trigger properly (and text highlights instead), there's inconsistent use of finger-sized vs. stylus-sized controls, the touchpanel needs entirely too much pressure to be comfortable for extended use... my replacement for it will come when I (eventually) buy an Android phone.

Fantastic. Except:
* "Errors put the browser in "dumb rendering" mode" is a non-backwards-compatible change, so can't happen
* Relatedly, you'll still need to accept HTML4 and prior, including non-DOCTYPE'd pages
* Thanks to the above, almost nobody will ever invest the time needed to move from '">' as a method of writing pages. Generating dynamic pages via DOM is (IMHO) a PITA compared to just spitting it out, and I'd wager a good number of web developers agree.

I'd love it, except it simply isn't feasible. You're talking about rewriting a huge percentage of dynamic content on the web - it just won't happen. (IMHO :)

Well... are they African or European ants?

What do you mean "it turns out they're the same thing"?!?

Indeed - as someone who used to run some reasonably-sized forums and ad server to match, I spent some time making sure that the ads didn't slow the loading of the page, and didn't kill the page when the ad server decided to go loopy.

The solution? IFRAMEs. Simple, basic, but entirely effective at both of the above. 99.9% of the time, it didn't matter - but the other 0.1%, it saved the site. (We learnt the downsides of all of the other methods the hard way :).

The biggest problem with IFRAMEs was that we had to have greater control over the ads - we ended up having to patch SWFs from some advertisers to load in _blank, the ones we were supplied would often try to load inside the IFRAME only.

Did you write to your _local_ Member?

If not, try that. Your local Member is more likley to care what you think. (I wrote to Conroy and my local MP, and received a reply from my local MP only).

Keep in mind please that no filter has yet come to pass... if you're in Australia, write to your MP. If not... wish us luck :)

(Note: I work at an ISP, but I speak for myself, not my employer)