That's right, more or less. Jet planes do just under 1000kph ground speed, propeller planes are usually closer to 500 or 600.

It's a little bit misleading to be comparing the vehicle's speed: what people really care about is how fast *they* travel, and how comfortable it is.

For short haul distances, once you take into account all the constraints that trains don't have: check-in and dealing with luggage (at both ends), boarding through a single door (or two), limited cabin space, refuelling, taxiing and waiting for a slot (for both take off and landing), take off and approach vectors at reduced speed, and as was pointed out in the article: the fact that the train station will be in the city centre, whereas you'll often still need to find your way to the city from the airport. Fast trains rule.

Really, that's interesting and I stand corrected. Thanks.
I still fail to see the benefit of generating the key on the kernel.org system and sending it PGP encrypted. Why not just generate yourself and send it to the kernel.org administrators PGP encrypted instead? (as per the reply below, using 3rd party private keys is bad practice)

The user is not issued a key, he generates one and gives it to the repository administrator to get ssh access. This process is called *generating* a key, and you can publish the public key to anyone, including the repository administrator which will then use it to grant you access. The private key however.. should remain private.

The point is that only *you* should ever have access to the private key, having someone else generate it (as is suggested by the wording in this article) would be very unusual, as you would not want to use this key for anything else, and someone else would have your private key for no good reason. Someone could even potentially use this key to fake your identity in commits.

The problematic wording is here: "Each is issued their own ssh private key".

You claim that both are run by real people who go the extra distance find the best links to their sources, and blatantly they're not.
It is well known in climate circles for being written by a former TV weatherman, and regularly "falls" for basic mistakes like muddying weather and climate, shifting the goalposts, referring to "climategate" despite the fact that the results have been vindicated again and again. And politics, don't forget money and politics: if the statistics don't go your way, cherry pick the data, prey on people's fear of taxation, the UN, Al Gore and what not. That way, they won't bother listening to the actual scientists and their data (which is all too complicated - let me simplify that for you: conspiracy!).
You make it sound like this is valid source of information on climate science, when the vast majority of climate scientists have moved on from the false "debate" they claim to be having. Like, 10 years ago or more.

Just how slow am I talking about? As per the link, often about 50 times slower than x264.
This may be OK for google, which encodes a video once and then sends it to many many customers (youtube), the bandwidth savings pay for the increased CPU cost.
But for most users, that's just not acceptable. Until they get the speed up to a reasonable, we'll keep using what works: x264 or vp8

It's good enough for valve to base its console on (and not wayland), it's also good enough for me (FWIW) in that it works and at this point wayland does not as it is nowhere near feature parity with X11.
And when comparing X11 vs wayland for a simple desktop: wayland loses every single benchmark.

Sourceforge was meant to help open-source software, not hinder its use! What happened?

I like to post detailed instructions on how to do things that include cut&pasteable commands (if anything, for my own sake), and since sourceforge removed direct download links to source files I have had to mirror them on my own servers just so that the instructions can be used. Sad. How many projects are now wasting their valuable time working around sourceforge's decisions?

As an open-source project, what do we need to do to get the same amount of publicity as those for-profit companies? Do I need to pay slashdot or something?
All this talk about remote desktop, and xpra is not mentioned once, despite having better performance than all the solutions mentioned thanks to hardware acceleration. It is also seamless, which a browser window is not. etc.. sigh.

Not at all, it is. I am saying that designing a network protocol for forwarding desktop pixels from OSX or win32 desktops and using X11 semantics would be a mind boggingly stupid idea, which is why they have not done it.
This is also why directing criticism towards X11 is very much misguided, it may have its flaws but this is certainly not what drove them to make the decision to switch.

Which technology was their creation and which one wasn't is not really the issue for me, taking an open-source product and making it closed-source is what I am talking about.
And I don't like it one bit. I think potential customers should be very wary of such business practices.

Using hardware is key, you can halve the latency and keep bandwidth usage lower (and this is one trick NX does not have AFAIK).
And VNC (in all the incarnations that I know of - of which there are many..) just doesn't do video at all.

Apologies if this came across as slander. One man's "badmouth" is another man's fact, a question of perspective I guess?
(ie: availibility of features and latency/performance numbers don't lie)

There is just no other way of providing native OSX or win32 servers! It wasn't a great act of foresight. (using an X11 proxying protocol for OSX and win32 servers would be a very dumb thing to do, a complete nightmare and a waste of development effort)

The reason why I did not consider NX v4 to be included in my statement is that it is approximately 6 weeks old... It is closed source and the "free" version is a bit crippled (maybe not so crippled as to make it unsuitable for the OP though?). v3 (abandonware) is the only version that one can install on a Linux box using open-source repositories.
More importantly for me: with their history of closing source (even where the delta compression algorithm wasn't even theirs to begin with...), I wouldn't go near it.

It is a bit (though the encoding technology is the same - I'll give you that): what makes OnLive and Shield usable is the low-latency/high-quality video achieved through hardware assisted encoding (and xpra does this too), NX does not do that AFAICT.

I am still amazed at how people can recommend 1990s technologies like VNC and NX.
Things have moved on quite a bit since then, and those two technologies have not.

• * NX is now closed source (v4 onwards) and the old branch (v3) is no longer maintained.
• * Xpra absolutely kills everything else in terms of performance and features.

If you need a GUI on top of that (not sure you really do):

• * Xpra has a limited GUI session launcher (but only for connecting to existing sessions at the moment)
• * NX has a number of management tools - beware, most of them are abandoned or buggy and insecure..
• * winswitch handles both and more (VNC, RDP, ssh -X, ...)

Disclaimer: Xpra and winswitch maintainer.
You did do a google search first, right? Did you miss this answer?
AFAICT, most of the other posts talk about virtualizing and other irrelevant topics.

What has always bugged me about bitcoins is just how pointless those calculations are.

Why not use them for the good of humanity? Why not link with projects like seti, @folding or other?
Surely the technical hurdles aren't that high, and instead of causing localized heating (cpu) just to get a hash value, one would benefit society too?

xpra does this on Linux, Windows, OSX and Android (beta).
It's free and it's open-source.
It also does x264 encoding when needed and is available for all your machines now without any strings attached.

Seriously, using Xvnc to forward your ssh session just to deal with disconnections? That is so backwards.
xpra is way better than this, and even NX, despite being old and closed/abandoned is still better than this, and both are seamless.

I haven't tried splashtop, and it being closed source I doubt I will in a hurry, but I reckon xpra is probably on par with it when it comes to performance - we also use x264 encoding where appropriate - and this is the keyword: where appropriate (like video, fast moving animations, etc), in many other cases it's not..