Re: Tizen?
 

Well, I think it is a good example. I.e. because Visual Studio do not natively use the Windows APIs, but you have to import them if especially interested. Also because software like OpenOffice is made in something completely different, and in addition to Java, there is or has been wide usage of other IDEs like Delphi.

On Windows you have a lot of choices. That's the main point.

Re: Tizen?
 

That is patently false. There's a metric buttload of Qt software running on Windows, and for most of it you wouldn't even have a clue that it uses Qt.

There are probably more Qt applications running on Windows than there are applications that use Microsoft's own toolkits.

Re: Tizen?
 

Isn't RPM still inferior?

Re: Tizen?
 

Both formats/tools have areas where they excel and areas where they are less than great. As a trivial example, rpm -qf beats dpkg -S hands down. Oh, and delta-rpms, when deployed properly, rock :-)

IMHO it's a stalemate that will never be resolved unless/until someone comes up with a better alternative and blows both out of the water.

Re: Tizen?
 

Nowadays I think it is superior. I use both "weekly/daily".

rpm (at least in Fedora) uses transactions to make sure the system stays consistent even if something nasty like battery goes empty middle of upgrading.

Also secure wise it is more secure policy to have GPG singatures embedded (like in rpm) in each software package than have all packages unsigned and then just whole distribution GPG-signed (like in deb). The deb policy leaves practically nasty MITM vulnerability which has often seen also in t.m.o.

Re: Tizen?
 

You don't know what you are talking about with VS. Everything is built on top of the Windows API. As for Delphi, that is also built on the Windows API.

Except that we aren't talking about a desktop OS. We are talking about a handheld OS, which is much more limited in screen resources, storage and battery power. What makes sense for a desktop system doesn't necessarily make sense for a mobile device. It also doesn't make sense to support many SDKs, particularly since it would be a custom job to adapt the SDK to a mobile interface.

Re: Tizen?
 

You are stretching the realm of believability with that comment.

Also, Qt on Windows does use the Windows API to acheve some of the native look.

Re: Tizen?
 

Sure, but iOS, android, webOS and Qt are different SDKs that all already have a mobile interface. Not saying that supporting them is easy (especially the platform dedicated ones), but we're not talking about supporting many desktop SDKs but rather many already mobile SDKs.

Re: Tizen?
 

So, now we are just waiting for announcement, about prototype tizen device "lend" program, for talented developers etc... And some naive dev guys just following another twist ;)

Re: Tizen?
 

ITYM Linux with one toolkit is better than Linux with several. I beg to differ (eg I believe Maemo to have been much superior to Qtopia, precisely because of this freedom of choice), but in any case Tizen's native toolkit appears to be EFL.