A couple of benchmarks have been done over the past 2 decades. Though it's a shame they're not mentioned in the article.
The reference paper on the topic is Keith Packard's and Jim Getty's USENIX 2003 paper on LBX (Low Bandwidth X), a compression proxy for the X protocol. This paper compares LBX against the standard X protocol (both with and without a compressed SSH tunnel). A couple of key findings from the article:
- SSH compression is almost as good as LBX (which is probably why nobody bothers with it)
- X11 is pretty efficient on bandwidth for everything except raw image data
- X11 is very sensitive to latency
Now some of those issues have been (somewhat) mitigated in various libraries such as xcb, Qt and Gtk+, X11 can only be used comfortably over low-latency links.
While searching for that first article, I came across a more recent presentation which compares X11 against VNC and NX. Again, the author(s) conclude that X11's performance suffer greatly whenever latency increases. As for my own daily experience working company X terminals, remote X even on speedy gigabit networks is a major PITA and I'm planning to work on comparing alternatives (VNC, RDP, SPICE,
X still has value, it's the lingua franca of GUI protocols on UNIX and I don't think anyone expects it to disappear anytime soon. But it is an antiquated protocol, both for local operations and for remote displays.
The core network of Minitel was owned and operated by the company now known as Orange. However, the device itself is a really dumb text terminal based on ITU-approved standards: V.23, ASCII, videotex, etc. Most Minitel terminals even have a serial port and thus can be hooked to recent computers.
Even back when the core network was still being operated, nothing prevented people from operating their own Minitel server/service. You could directly dial any standard number (not just the short 36xx ones).
Quite a mess.
You can support almost all browsers out there with only two codecs: H.264 + your choice of ogg/theora or webm/vp8. And the H.264 will of course still work with Flash. This URL http://caniuse.com/#feat=webm is very handy if you want to see for yourself.
At least that's the situation for static streaming / VOD. Live broadcast is where the mess is with Apple's HLS, Microsoft's HSS, Adobe's RTMP, MPEG's DASH along with IETF-standard RTSP (15 years old but still somewhat alive) and various less-known protocols. AFAICT, none of the recent protocols (that support adaptive bandwidth and work over HTTP) support open audio/video codecs. If Google/Mozilla/etc want patent-free codecs to get traction, they should work on a version of DASH that works with theora/VP8.
My 0.02€ as a former employee of a large video-streaming-oriented CDN.
Ok, I'll bite this one for a change.
I don't expect any slashdotter to actually even care for the original article (yes, the one in French) but just the summary
Here's basically what this fellow French dude says : Google, an american company, is trying to digitalize books, let's team up as europeans to continue to bring our own litterature on the web as well.
Of course his first few lines sound very anti american, just as the first few posts talked about frogs and all
This is not as much towards google as it is towards the French government and other EU countries.