Actually, this is what kdenlive does: it is a GUI frontend for the CLI MltMelt tool (http://www.mltframework.org/bin/view/MLT/MltMelt). Given, it is one command which does everything instead of multiple small commands, but there is still a separation between the program doing the work and the program providing the GUI.
Pity they didn't use the Hackfest to design something innovative to energize their base and make working with Gnome cutting edge.
Like what, vala?
Unless you add chainsaws.
[...] and yet those small 1-2 man teams are each now probably millionaires.[...]
They are not. Most indie developers have very fluctuating income and usually it is barely enough to make a living. There are some exceptions though; the creators of more popular indie games do have a reasonable income, but when subtracting the costs most will not be millionaires. I expect the number of millionaires from indie games to be 1, and that person is Markus Persson.
In my experience the prices in EUR and in USD are roughly the same. Partly because we do pay more, but mostly because we include VAT in the price. At the current 21% VAT (in the Netherlands), the remaining difference in price is only relatively small (~5%).
The actually acknowledged that they had that problem a few years ago, and since they have been moving back towards generic pieces instead of these specific pieces. It might still be worse than back in the day, but things are certainly improving.
I used to run btrfs roughly a year ago for half a year and had no issues with data integrety etc whatsoever. The downside at that time was that performance for working with loads of small files was noticably worse than with ext4. The result of this was that a dist-upgrade took more than 4 hours instead of the expected 1.5 to 2 hours it takes with ext4. Apart from that I had no issues whatsoever; performance on other loads was decent.
I occasionaly look for benchmarks showing that the small files performance is up to par, but so far I have been unable to find them.
So you say that it is best to solve this problem in each application inidividually instead of, say, running one process on each system which makes sure that the clocks stay in sync for all applications?
The other key advantage that X11 has: if the application is mis-behaving the application's window can still be controlled by the window manager. Ever seen windows on a Windows desktop that cannot be minimized? Wayland is bringing that to Linux.
It is still possible to support server-side window decorations. The Wayland compositor will be the unification of what currently are a separate compositor and window manager and should support all old functionality. For example, KWin will use server-side decorations by default.
Samsung managed to solve the orientation-issue: their connector is assymetric, with the wire not being in the middle but at the right side if the connector is facing up ( http://www.world-of-accessories.co.uk/images/medium/120411130643.jpg ). I have no problem at all with getting it the right way: i just have to see (or feel) the connector.
It is inherentily impossible to build something into an OS which cannot be controller by that OS itself. If you want these really secure firewalls, they should be on a separate appliance and all your traffic should be routed through them.
Most developers seem to be running this from a WeTab, so that would probably the tablet of choice. There is about a dozen devices which are able to run Plasma Active quite decently though; they can be found by a small search through their website.
The whole idea of this system is that it can be slowly phased in. The system looks at other cars with the system nearby and looks at their behavior. If a car somewhat in front of you is breaking, a signal is sent to the driver that something is about to happen. It is not really autonomous right now, but supporting the driver.
Most mobile phones are, as far as i know, IPv6-ready. Symbian supports it, Android supports it (although i'm not sure if it's enabled), iOS supports it. I'm not sure about WinPhone 7 and BlackBerry.
I find that neither emacs nor vi qualifies to be a proper editor; that simplifies discussions very much. More serious contestants for the title include nano and mcedit, but roughly any GUI editor wins from CLI editors if you ask me.