That is exactly what they just did! The way Qt extends C++ gives you a fast and powerful development environment, surpassing plain C++ big time.

The owner then has 90 days to claim the property. Id. 2080.2. If the true owner fails to do so and the property is worth more than $250, then the police publish a notice, and 7 days after that ownership of the property vests in the person who found it,

Funny thing is, that if he had done that and delivered the phone to a local police station. It would more likely than not have been tossed into a lost and found bin, and become legally his after those 90 days. The phone was already disabled and contained no owner name, and barring the police officer receiving it being a hardcore Apple fan identifying it as a prototype, there was no obvious way to identify the owner. It would be handled like any other found phone, the police registering it and logging the name of the person turning it in. They would not care or bother with any further investigation as they have much more important task to handle. Combined with Apples taste for secrecy, it's not likely they would send people to surrounding police stations asking for the phone.

Seriously, how does this further harm the guy who lost it

Depend on Apples reaction on him loosing the device in the first place, but it's fairly likely he does not work there anymore. Then it's rather harmful.

Not too cool trying to get a new job known as the guy who lost a secret prototype of his former employers in a bar. Not exactly something to highlight on your resume.

You don't have to interact with Plasma all the time. You can have a old fashioned desktop and a taskbar/panel, and not be bothered with widgets and Plasma stuff.(Technically both the desktop and taskbar/panel are Plasma widgets, but that's really only a implementation detail you don't have to bother with).

First set your desktop containment(activity) to be a FolderView rather than Desktop(Desktop Settings->Appearance). Then select lock widgets.

You now have a plain regular desktop where you can put documents, no decoration pop up around widgets and the configuration button in the lower right corner is gone laving the space free for you and fits law.

Or open System Settings and select Default Applications. Choose file manager and select Konqueror, then press Apply.

The weight is not a problem, it's not really something you are going to carry around like a phone. As you say, it weight slightly less than your netbook which is a device with some of the same use cases. A pad like this will be a more stationary device, used for leisure net-surfing and light reading. The people behind the Crunch-pad had the right idea, coach computing. The main use for such a device will be in living room chairs or sofas, flipping trough web pages. For such use the keyboard and mouse/trackpad solutions on laptops/netbooks are just in the way, a good sized touch device will be much more usable. The biggest problem on this device will be the screen, it's on the small side with it's 10". A 11-12" would be a better fit. And it does not have a very good resolution either.

Of course, building/prototyping hardware CAN be more expensive, but thinking of software development as "cheap" just because you can get a PC for ~$200 - yeah, well, no... not really.

You got it, building and prototyping hardware is more expensive period. Software development will always be cheaper on matching complexity levels. Even disregarding the ~$200 PC, going for a ~$1000 and adding a ~$50000 for development tools, you will still always come out ahead with SW development. Decent tools for hardware development does not come cheap, and considering the free tools for sw development its easier to cut cost there.

And after the initial investment, you only burn man hours with sw development. The compile-debug-compile cycles only cost time, where in hardware development each successive round of prototypes add the cost of parts and production. Not to mention the delay after the prototype design is finished until you get the produced part. If you think a 20min compile time is bad, try waiting one to eight weeks for your prototype before you can start testing and debugging it.

The "finally" is a bit strong, since it has been there for a while.

Using zypper dup worked flawlessly upgrading my 11.0 installs to 11.1. So I'll say you are at least one release to late with that one.

Privacy issues and other consideration does not matter, it boils down to one simple rule, never trust a insurance company!

As CentOS is a repackage of RHEL, you should have at least one RHEL license if you are doing anything close to mission critical. If you get a problem on one of your CentOS servers, you can recreate it on your RHEL server, and get support from RedHat. Subsequently when the bug gets fixed, also get the fix for your CentOS servers.

For anything mission critical it's insane not to do that, otherwise you are gambling that not only some random RedHat customer get the same problem as you, but also that they report it so it has a chance to get fixed.

And in case you get a problem on CentOS that do not exist on RHEL, I'm betting the CentOS developers are quick to help fix the issues.

For simulation, you can get Spice versions for all platforms.

For the CAD part, there is the EAGLE Light Edition from CadSoft http://www.cadsoftusa.com/freeware.htm It runs on Linux, Windows and Mac.

What about the PyGTK and GTK websites. According to the download links the latest stable and updated PyGTK are for GTK 2.14, and GTK 2.16 has been out since the middle of March. For PyQt you don't find many minor releases of Qt that has not been followed by a updated PyQt release inside a week or two, for the last 5 years or so.

As for being comprehensive, the Qt bindings(at least PyQt) has a close to full coverage of the Qt classes. Last I checked PyGTK did not offer the same. And since Qt are not only a GUI library, the difference gets even larger as the bindings provide so much more.

My main issue is that Qt is pretty strongly tied to C++ This is repeated over and over again and even if people believe it, it' still not true. That is pure FUD. Whereas GTK in C may be horrible, but the bindings to Python, Ruby and C# are all excellent Fact is, the Qt bindings for those languages are more comprehensive and more up to date than the GTK counterparts. The Qt bindings all have powerful automatic tools for generating bindings for those languages, making it easy to keep up to date.