News for hackers. Stuff that matters.
Re:Ballmer to announce VS 2010 will compile native Mac/iPhon... by statictype on Thursday May 27, 2010 @11:44AM (#1383955)
At first blush, I dismissed it for violating 3.3.1, but now that I think of it, you're allowed to use Objective-C, C or C++. Visual Studio already has a C/C++ compiler so they don't even need to introduce a new language into the mix.

And since it looks like Apple is betting the company on the iPhone/iPad (as opposed to Mac OS X) there's no real downside to letting developers on non-OSX platforms build iPhone apps.

You would still need the $99 Developer License to load apps onto the device. And Apple gives Xcode away for free so they're not losing money on allowing competing development tools.

I still don't think this announcement is going to happen, but it's not the most outrageous thing that could happen.

If anything its more likely that Microsoft would reject such an idea than Apple.

Re:Ballmer to announce VS 2010 will compile native Mac/iPhon... by rbanffy on Thursday May 27, 2010 @12:55PM (#1384226)
> there's no real downside to letting developers on non-OSX platforms build iPhone apps.

To fully enjoy network effects you need to control the whole stack. This is the problem with this rumor: Jobs may be anything but he's not suicidal.

Allowing iTunes to run on Windows helped increase sales of iPods and music and preventing those who already had PCs running Windows to considering the competition.

Allowing VS2010 to target iPhone/iPod/iPad would increase the number of developers who could develop for the platform, something that I don't think Apple really needs.

If nothing else, Apple could raise the bar on apps a bit. This would only lower it.

Re:Ballmer to announce VS 2010 will compile native Mac/iPhon... by stcredzero on Thursday May 27, 2010 @03:05PM (#1384626)
If nothing else, Apple could raise the bar on apps a bit. This would only lower it.

On the contrary, if Apple had more apps to choose from, then it could afford to be more selective. The only thing is that they're already in a position to be more selective, and they're clearly not! (Perhaps too much work.)

Re:Ballmer to announce VS 2010 will compile native Mac/iPhon... by rbanffy on Thursday May 27, 2010 @04:22PM (#1384842)
You haven't seen many WinMo apps lately, have you?
Re:Ballmer to announce VS 2010 will compile native Mac/iPhon... by stcredzero on Thursday May 27, 2010 @05:01PM (#1384939)
To borrow a phrase from the Borg: WinMo is irrelevant.
Re:Ballmer to announce VS 2010 will compile native Mac/iPhon... by rbanffy on Thursday May 27, 2010 @06:26PM (#1385120)
That's the point. Apple doesn't need WinMo developers porting their apps to iPhone because a) they are terrible, b) there are not many of them and c) the important/interesting ones are already ported
Re:Ballmer to announce VS 2010 will compile native Mac/iPhon... by stcredzero on Thursday May 27, 2010 @10:07PM (#1385481)
Who said anything about WinMo apps? Mindshare is the valuable thing!
Re:Ballmer to announce VS 2010 will compile native Mac/iPhon... by randombit on Thursday May 27, 2010 @01:06PM (#1384266)
> At first blush, I dismissed it for violating 3.3.1

Even if it it did violate the clause: Apple changed it once, they can change it again...

Re:Ballmer to announce VS 2010 will compile native Mac/iPhon... by alextgordon on Thursday May 27, 2010 @01:00PM (#1384237)
At first blush, I dismissed it for violating 3.3.1, but now that I think of it, you're allowed to use Objective-C, C or C++. Visual Studio already has a C/C++ compiler so they don't even need to introduce a new language into the mix.

Section 3.3.1 also disallows using "compatibility layers" to access documented APIs. Since the Cocoa APIs are Objective-C, you wouldn't be able to write an app using only C++ without violating it (except perhaps in the case of an OpenGL game).

Re:Ballmer to announce VS 2010 will compile native Mac/iPhon... by alextgordon on Thursday May 27, 2010 @03:20PM (#1384658)
I'm a little puzzled why this is being downvoted. If I've made an error, could you please point it out?