[Qt-interest] Qt for the iPad?

[BRM]

----- Original Message ----

> From: nobodyhere <pem.accounts.spam at gmail.com>
> To: BRM <bm_witness at yahoo.com>
> > The other major difference is that Apple isn't trying to push Carbon/etc as  a Platform-neutral API and then only support it on their own native platforms, 
> > where as Microsoft pushes .Net/C# as a platform neutral API but only supports it on Windows and then gives pseudo-support to Novell/Mono for 
> > Linux/Mac/Unix/etc.
> There is a categorical distinction.  Apple is  *banning* Adobe Flash (and possibly Qt and/or Mono?) from their OS.  Is 
> Microsoft banning some API from Windows?  Has Microsoft banned any APIs from Windows 7 (or Windows Mobile 7)?

As I said - Microsoft doesn't control the hardware. Apple does.

This would be like arguing why Palm wouldn't allow .NET or Java or Qt or Flash on the Palm Pre, or Nokia not allowing wxWidgets on the N900.
There is a categorical difference between Apple not allowing Flash or .Net or Qt on the iPhone/iPod Touch/iPad and what you are claiming.

> > So yes - Apple isn't being  very friendly, but they're well within their rights to do so; and they are not interfering in the market place either.
> I didn't mean it as an argument  for government regulation.  Although Microsoft has been attacked by the 
> European Union over less (but then again, the EU is attacking all US technology companies - because who will stop them from stealing money from US 
> companies?).  I meant it as an argument for developers and tech-savy  consumers to consider Microsoft better than Apple - with respect to this 
> specific issue.

Don't even go there. It has only been very recently that the EU has started looking at a lot of US companies.
Interestingly enough, all those "looks" can be tracked back to Microsoft, who after having lost in the EU and US on anti-trust,
and lost several rounds in ISO/etc stated that their competitors will soon see anti-trust charges against them.
Coincidence? I think not.

> If you are a hardcore openness nut...  Then it is 
> fine if you want to say "Microsoft is the devil".  But if you do, then 
> please also say - "but Apple is worse than the devil".

Question:
- Does Microsoft have an Open Source version of Windows? (Mac OSX is built on Darwin/OpenDarwin. iPhoneOS is built on Mac OSX.)
- How many truly open source projects does Microsoft sponsor? How many of those originated outside Microsoft? (Apple supports quite a number, including the CUPS printing services.)

Yes, Apple protects their domain; but they also do a lot in the greater community - including supporting open source, Linux, BSD, and more.

Microsoft, OTOH, has done nothing but try to subvert the community. Whether through FUD (e.g. Get The Facts), standards destruction (e.g. ISO/OOXML),
clouding the market place (e.g. SCO vs. IBM, SCO vs. Novell, TurboHercules - yes, those can all be traced back to Microsoft), and various other tactics.
One thing they learned a few years ago was to get others to look like the front-runner of the issues they want to make - makes it a little harder to trace
back to Microsoft; but nonetheless it does; and I wouldn't be surprised if they got a RICO violation for it - or more Anti-trust charges for it too.

> Oh, and you might want to add on top of that, that "Google is watching you" O:-)


> > Microsoft provides the OS, but not the hardware 
> That is exactly right - Microsoft's Operating System strategy is noticeably more open (and supportive of 
> an open market, for both hardware and software) than Apple's system.  As a 
> general rule, I think it's great that both strategies to exist - and I am glad 
> to use plenty of hardware and software from both Microsoft and Apple.

If by Open you mean only targeted at Windows, frequent security issues, and more - yes.
If by Open you mean that you & I could fix problems, etc. then no.

The only truly open systems are the BSD and Linux distributions out there.
Mac is closer to Open than Microsoft as it is based on Darwin/OpenDarwin.

Microsoft only ever opens up enough to try to keep their market share, and exclude anyone that might try to take it away.
Do they really have the communities best interest in mind with CoApp? No - it's all about keeping people on a closed-source, proprietary, broken operating system made by Microsoft.
Sure, it'll help make things like KDE on Windows or GNU Win32 function better, and be easier to distribute; but it's not about the community - that's something Microsoft will never truly understand or grasp.


 
> But two things I complain about.  One, I think Mac x86 limitation of hardware 
> choices goes too far in terms of being closed.  Their choices are very 
> limited.  Most of them use the same chipsets, they are all the same Intel 
> processors (mostly Core 2 Duo), and only Mac Pro and iMac have a decent 
> (discrete) GPU option (Mac Pro and iMac are both oversized).


> Two, if they ban an API that follows whatever Cocoa Touch UI guidelines (like MonoTouch, or 
> Qt?) - then I think they may have gone too far...  Or, at least, I think 
> it's viable for people to notice that Google and Microsoft aren't doing 
> that.  And if I had actually written a MonoTouch app, and then seen 
> MonoTouch get retroactively banned - well that would be really horrible!  
> In fact, Apple has done such retroactive banning, such as retroactively making 
> approved apps remove access to the DCIM central folder.

When you are talking about devices like the iPhone, every little bit of disk space and performance matter very much.
Apple is and always has been about the experience of their devices and software, and they will always do what it takes
to ensure what they deem provides the best experience. That's their business; that's their target audience.

Yes, the Qt guys do a great job at providing platform independent access to native interfaces, and integrating into the native interfaces.
But, as Thiago has pointed out, that comes at cost - time, money, testing, etc - and it's not cheap.

> It's really horrible to think that you could spend all this time writing something, and then 
> they retroactively ban it.  Even if they just block it the first time you 
> submit it, for some unexpected reason that is impossible to fix - then you could 
> really have gotten screwed.

I'll agree there b/c you've spent time and money developing the application.
But honestly, it's their choice.

Don't like it? Sue 'em. Try to make a class action out of it.
But you probably won't get far.


Ben