Slashdot Mirror


Developers: MS Hopes To Lure iOS Apps With API Mapping Tool

Microsoft isn't standing idly by while Appple's app store fills with software; fysdt writes "A newly-announced service called the iOS to Windows Phone 7 API mapping tool acts as an interchange for developers to take applications they've already written for Apple's platform, and figure out ways to get the code work with Microsoft's standards."

191 comments

  1. The first step to meeting Microsoft's standards... by Samantha+Wright · · Score: 5, Funny

    ...is lowering your own.

    (Click here for more information)

    --
    Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
  2. More of a headache by Anonymous Coward · · Score: 1

    It might be useful as a reference, but in practice this will probably be more of a headache than just building the app from scratch.

  3. With this... by zppln · · Score: 2

    ... Microsoft will be unstopppable.

    1. Re:With this... by SquirrelDeth · · Score: 1, Offtopic

      And if I eat Taco Bell my diarrhea will be UNSTOPPABLE!!!

  4. The First step to fixing a problem... by Anonymous Coward · · Score: 0

    is admitting you have a problem.

    Isn't it time to get a new leader at MS?
    MS needs an engineer, not a marketing suit who understands where things could go.

    1. Re:The First step to fixing a problem... by VGPowerlord · · Score: 1

      Isn't it time to get a new leader at MS?
      MS needs an engineer, not a marketing suit who understands where things could go.

      Funny, having a marketing suit seems to be working for Apple. However, Microsoft's marketing suit doesn't seem to have the charisma that Apple's marketing turtleneck...er... suit does.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    2. Re:The First step to fixing a problem... by Kyusaku+Natsume · · Score: 1

      More than marketing, Steve Jobs have long term vision, something that is missing from every CEO today and almost all politicians. Who in his "right" mind in 1976 could have thought that "personal" computers that came prebuilt and output to a TV set instead to 7 segment LED display in hex code could have an use for common people, aside Jobs? About a really easy to use MP3 player, with a fast interface to a PC? About a new all in one computer, tailored to the huge masses that never had a personal computer before? Marketing is a very small part of Apple's huge success.

      For all his drawbacks, Bill Gates has an almost sick desire to win, something that seriously lacks Steve Ballmer.

      --
      Mexico: 100% conservative's America now!
    3. Re:The First step to fixing a problem... by walshy007 · · Score: 2

      Who in his "right" mind in 1976 could have thought that "personal" computers that came prebuilt and output to a TV set instead to 7 segment LED display in hex code could have an use for common people, aside Jobs?

      Steve wozniak.

      Steve jobs has always been a business man, not an engineer, the engineers are the ones who make the nice gadgets, the businessmen do marketing, make requests of the engineers like marketing do, and take care of finances.

    4. Re:The First step to fixing a problem... by Hognoxious · · Score: 1

      Who in his "right" mind in 1976 could have thought that "personal" computers that came prebuilt and output to a TV set instead to 7 segment LED display in hex code could have an use for common people, aside Jobs?

      Anyone who could remember Douglas Englebart's lecture from eight years before?

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    5. Re:The First step to fixing a problem... by Anonymous Coward · · Score: 0

      Well thanks for that, captain obvious!

    6. Re:The First step to fixing a problem... by CheerfulMacFanboy · · Score: 1

      Who in his "right" mind in 1976 could have thought that "personal" computers that came prebuilt and output to a TV set instead to 7 segment LED display in hex code could have an use for common people, aside Jobs?

      Steve wozniak.

      Steve jobs has always been a business man, not an engineer, the engineers are the ones who make the nice gadgets, the businessmen do marketing, make requests of the engineers like marketing do, and take care of finances.

      That's assuming Woz hadn't been perfectly happy with an Altair, instead of Job's edging him to make something easier to use.

      Jobs strong point is not marketing (else he wouldn't have called in sugar water salesman Sculley, not to mention that all his products would have been hits then), it's convincing people to do what he wants done, even if they thing that it can't be done.

      --
      Fandroids hate facts.
  5. I remember before Jobs was all about lock-in... by Hazel+Bergeron · · Score: 1

    ...and the NeXTSTEP API was something allowing portability across systems.

    1. Re:I remember before Jobs was all about lock-in... by Samantha+Wright · · Score: 1

      You're thinking of OpenStep. When it was clear to Steve that NeXT wasn't about to win on its own, he started opening things up, in a desperate bid to retain relevance—the design was beautiful (although I can't say I care much for the exhaustive use of NS prefixes) and it seemed like a smart move at the time. Then Apple came running back to him, he became super-duper-successful again, and suddenly playing nice with the rest of the industry became a bad dream for Steve, excepting occasional concessions to the Mac Office team. Of course, since OpenStep was pretty much doomed (it was the mid-nineties and Windows NT had already won), it's not like we can say he's turned his back on any principles.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    2. Re:I remember before Jobs was all about lock-in... by catchblue22 · · Score: 1

      Of course, since OpenStep was pretty much doomed

      I believe that OpenStep and/or its progeny are integrated into OSX and iOS, which is one of the reasons that Apple can swap around it OS's onto various CPU designs so easily. Think of the transition from PowerPC to Intel, or the other chips that run the iPhone/iPod Touch/iPad. This is a huge competitive strength, and is likely a key reason for the success of Apple.

      --
      This and no other is the root from which a tyrant springs; when first he appears as a protector - Plato (423 to 327 BC)
    3. Re:I remember before Jobs was all about lock-in... by Samantha+Wright · · Score: 3, Interesting

      The answer you're looking for is "its progeny", which is the much-loved Cocoa toolkit. I was speaking of the OpenStep initiative itself, which consisted of a rebranded NextStep (which was also ported to x86) and API compatibility layers for NT and Solaris, neither of which exactly passed into legend.

      One thing that's not often remembered is that the OS X kernel and APIs ran on x86 since Steve brought NeXT back to Apple with him. (Rhapsody and later OpenDarwin.) The rush for the big switch wasn't nearly as large as is often assumed, as Apple was quite prepared for it.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    4. Re:I remember before Jobs was all about lock-in... by Anonymous Coward · · Score: 0

      ...and the NeXTSTEP API was something allowing portability across systems.

      Yes. One wonders why he would move from such a successful and profitable open platform to the closed, money sink of a platform that iOS is now.

      Oh wait. Nobody bought OpenStep; it was a total flop.

    5. Re:I remember before Jobs was all about lock-in... by gig · · Score: 1

      The NeXTSTEP API was about running on NeXT. It was used to create the World Wide Web. OpenStep was about portability across systems. But nobody used it, they just copied it into their own proprietary systems. So now the technology enables Apple to do things like jump OS X from PowerPC to Intel to ARM within the space of 2 years.

      Today, Apple's WebKit browser engine, which is the most popular mobile open source project, brings the Web and the open HTML5 API to all mobiles except Microsoft's, plus to Chrome and AIR and various set-top boxes. So Apple is doing more for open application development than anyone else.

      So your consternation is totally misplaced.

    6. Re:I remember before Jobs was all about lock-in... by gig · · Score: 1

      Every instance of the word "win" in your post is wrong. Windows NT never won anything. It is terrible, an embarrassment. The World Wide Web was built on NeXT, and so was the modern Mac, iPhone, and iPad. If current trends hold, OS X systems will outsell Windows systems in 2014 or 2015.

    7. Re:I remember before Jobs was all about lock-in... by gig · · Score: 1

      It's often remembered that OS X ran on Intel the whole time. Jobs pointed that out when introducing the Intel Mac in 2005. He showed the overhead view of the building where they had been running Mac OS X on Intel since the Mac OS X launch. But people had suspected for years.

    8. Re:I remember before Jobs was all about lock-in... by Kalriath · · Score: 1

      The NeXTSTEP API was about running on NeXT. It was used to create the World Wide Web.

      Pretty sure that POSIX was used to create the World Wide Web.

      Today, Apple's WebKit browser engine, which is the most popular mobile open source project, brings the Web and the open HTML5 API to all mobiles except Microsoft's, plus to Chrome and AIR and various set-top boxes. So Apple is doing more for open application development than anyone else.

      So your consternation is totally misplaced.

      Apple's WebKit? I think you mean KDE's KHTML.

      Nice history revision though.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    9. Re:I remember before Jobs was all about lock-in... by Samantha+Wright · · Score: 1

      You're amusingly upset. Let me clarify, then:

      "NeXT wasn't about to win on its own" = "in 1996/7, NeXT Software, Inc. was going down the tubes and had no future as a viable commercial entity in its present form"
      "Windows NT had already won" = "in 1996/7, Microsoft had already obtained a huge market share in business computing through largely illegal tactics that didn't leave any room left on the market for competitors like NeXT Computer, Inc.'s hardware offerings, the last of which were 68k-based and shipped in 1993."

      You were aware that "NeXT" means "NeXT Computer Inc." and not "the combined sum of the NeXTstep operating system and OpenStep API platform", right?

      You did know that there was a company that produced NeXTstep, surely? And that it was called "NeXT"? Founded by Steve Jobs? In 1985? After John Scully ousted him for being a liability? Yes?

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    10. Re:I remember before Jobs was all about lock-in... by Samantha+Wright · · Score: 3, Interesting

      It is, of course, also one of the most epic displays of grassroots community bait-and-switch in history: let volunteers spend years fixing and perfecting the port of OpenDarwin to x86, then kill the community when its code starts facilitating Hackintoshes. Classic Jobsian ill will: "if you haven't paid me in the last eighteen to twenty-four months, I owe you nothing."

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    11. Re:I remember before Jobs was all about lock-in... by UnknowingFool · · Score: 1

      Apple's WebKit? I think you mean KDE's KHTML.

      That's some revisionist history too. If you think KHTML = WebKit then you must think BSD = SystemV = AIX

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    12. Re:I remember before Jobs was all about lock-in... by Kalriath · · Score: 1

      Not really. Ultimately, WebKit is KHTML. It has been drastically altered over the years, but at its core it still contains KHTML code. It's certainly closer nowadays to being a whole new beast, but frankly that's because Apple doesn't release patches upstream.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  6. Cool! by moorster · · Score: 0

    MS has some of the best dev tools. I wonder how that app works. Does it actually spit out the C#/Silverlight code for your or is it more of a reference tool?

    1. Re:Cool! by Anonymous Coward · · Score: 0

      I gather you search for an iOS class, and this tool will tell you how to achieve a similar result with WP7.

    2. Re:Cool! by Anonymous Coward · · Score: 0

      Quite similar to dipping your phone in the sink then.

    3. Re:Cool! by Anonymous Coward · · Score: 0, Insightful

      well it's better than the using fucking EMACS or VI

    4. Re:Cool! by sockman · · Score: 1

      Come on, now. Emacs has a shortcut to generate your program for you.

      http://www.xkcd.com/378/

    5. Re:Cool! by jbplou · · Score: 1

      MS has good dev tools butthere upgrade wizards for .net 1.1 to 4.0 suck so why would I trust one for another platform.

    6. Re:Cool! by coolgeek · · Score: 1

      Dipping your phone in the sink results in a much smaller, and greatly shorter-lived headache.

      --

      cat /dev/null >sig
    7. Re:Cool! by wjsteele · · Score: 1

      Yes, because that .NET 4.0 runtime came up on you so quickly. I mean seriously... it seems like only yesterday that 2.0 (2005), 3.0 (2006) and 3.5 (2007) were released and now the're dropping 4.0 (2010) on us and forcing us to upgrade.

      I just wish you had a little more notice that this was going to happen.

      Seriously, their tools for upgrading managed code are great. They even document for you APIs that have been deprecated and suggest the new API to use. You're complaining about an upgrade wizard that is trying to figure out what you did 8 years ago and how it relates to Today. Really? What other platforms do that?

      Bill

      --
      It's my Sig and you can't have it. Mine! All Mine!
  7. Biggest problem with iOS development by Rik+Sweeney · · Score: 4, Interesting

    is that you have to (AFAIK) buy a Mac to develop for it. I can't really fault Apple on this as it's a great business strategy, but I simply can't be bothered so I'll only make apps for Android, which doesn't require me to buy hardware.

    If Microsoft wants their phone to succeed, they need to make sure that their SDK is available on as many platforms as possible.

    1. Re:Biggest problem with iOS development by Tibor+the+Hun · · Score: 1, Flamebait

      Android development doesn't require you to buy hardware?

      Awesome, do they recommend you use punch cards, or do you compile your code in the public library?

      Purchasing a used Mac mini for $500 to get access to world's largest mobile app store really is an unsurmountable barrier, that only the mightiest of giants can overcome.

      --
      If you don't know what AltaVista is (was), get off my lawn.
    2. Re:Biggest problem with iOS development by tepples · · Score: 3

      you have to (AFAIK) buy a Mac to develop for it

      As I understand it, you have to buy a PC with Windows to develop for Windows Phone 7. Or you have to buy a retail copy of Windows to run in dual-boot or virtualization, which is as expensive as just buying an entry-level PC due to deep OEM discounts. (Once in Best Buy, I've seen a retail copy of Windows Home Premium for $200 and an ION nettop PC with included Windows Home Premium for $200.)

    3. Re:Biggest problem with iOS development by 99BottlesOfBeerInMyF · · Score: 4, Insightful

      Biggest problem with iOS development is that you have to (AFAIK) buy a Mac to develop for it. I can't really fault Apple on this as it's a great business strategy...

      How is that a great business strategy? The number of iOS developers buying Macs contributes basically nothing to Apple's bottom line compared to iPhone sales driven by their large number of iPhone apps. The great business decision is keeping the dev environment under their control and making it Mac only is just easier and cheaper than maintaining it on Windows as well. This leads to apps that conform to UI guidelines and leverage all the built in functionality of iOS and are updated in a timely manner to take advantage of new additions to iOS. Apple doesn't have to wait for third party tool developers to add features to support what Apple puts in iOS in a new release. They build it into the tools and in many cases the next recompile of the app takes advantage of the new function. That is what is smart about Apple's dev tools, not some barely noticeable increase in Mac sales from selling to developers that want to target iOS. It's about promoting iPhone sales because that is where the money is.

    4. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      Android development doesn't require you to buy hardware?

      Not really, no. Google provide an Android emulator as part of the Android SDK. It's the standard way to develop for Android.

    5. Re:Biggest problem with iOS development by UnknowingFool · · Score: 1

      You always need hardware to do development. The majority of people have a PC so this is not an obstacle; however, some people have Macs or no computer at all so they will need to purchase something to start development work.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    6. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      ... and my biggest problem with Windows development is that you need to buy a Windows license to develop for it. You don't *need* a Mac to develop for iOS, but you do need OS X, which only runs on Macs or in VMWare (hint). Also, unless you're conjuring software out of thin air, you do need hardware to develop for Android. Your problem is that you purchased hardware that can only run Linux and Windows, rather than hardware that can run OS X, Linux, and Windows. That's like buying a Smart and complaining that it's Ferrari's fault your car can't go 200 MPH.

    7. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0, Insightful

      Where do you propose you run the emulator, fucknugget?

    8. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      On whatever computer i already own.

    9. Re:Biggest problem with iOS development by zach_the_lizard · · Score: 1

      If you're broke, it is.

      --
      SSC
    10. Re:Biggest problem with iOS development by sideslash · · Score: 0

      I think you are purposely missing GP's point. A nice thing about Android development is that you can install the SDK and develop and test your apps in the emulator on any of the major operating systems out there -- use the computer you like best instead of the computer somebody else tells you to use.

      Microsoft comes in second here, because you can at least dual boot any Mac or Linux machine to a Windows installation in order to run the Windows Phone emulator (sadly, due to technical limitations the emulator doesn't work in a VM; though all the rest of the MSFT OS and dev tools do).

      And finally, coming in at pathetic last place we have Apple's dev tools and emulator, which legally can only be run on Apple's hardware (and no legal VM use, either).

    11. Re:Biggest problem with iOS development by fermion · · Score: 1
      Of course if one is happy with a development environment that "lack the full breadth of features found in higher-end Visual Studio and SQL Server Editions" and all one wants to be is a "hobbyist, student, and novice developer" then one can develop for MS Windows Phone 7. Otherwise it costs $1300 with a $800 yearly upgrade.

      OTOH, the mac mini is $700 plus 4.99 for Xcode or $100 a year for Xcode and full documentation. Over three years, for a professional developer, not someone who is just knocking off fart applications, this is $1000 for the iPhone vesus $2900 for the MS WIndows Phone 7.

      Of course all this, and android, can pretty much done on shoestring using Eclipse which costs nothing. Which is why even with this lame escuse for a cross compiler I can't see people leaving in droves from iPhone, much less Android, to write for MS Windows Phone 7.

      MS has to decide what it's core mission is. Is it selling development tools and enabling the use of the code, in which case other software, especially the OS, should be much cheaper. Is it selling an OS and supporting apps, in which the development tools should be much cheaper. Is it hardware, in which case the software should not be forefront. It is this lack of focus that has allowed Apple to surpass MS in terms of revenue and profit.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    12. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      Actually, if you want to develop *commercially* for iOS you *do* need to buy a Mac as running OSX on VMWare is considered illegal by Apple's EULA and since you're going to need their blessing to get your wares to their phones you're going to need to go about it in a legal fashion.

      You're just going out of your way to make it sound like there is no premium for developing for the platform and there most certainly is.

    13. Re:Biggest problem with iOS development by shmlco · · Score: 4, Insightful

      "Not really, no. Google provide an Android emulator as part of the Android SDK. It's the standard way to develop for Android."

      I know Android developers who have bought a dozen or more different Android phones on which to test their software.

      If buying a used Mac to do iOS development is too much of an investment, and you believe that you can use the Android emulator to get by without testing across the myriad Android devices and platforms...

      Then all I can say is that I'm very, very, VERY happy you're developing for the Android platform...

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    14. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      It's funny that you think running on the emulator means it will run on actual devices.

    15. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      Oh wait I can't run OS X in an emulator so I have to buy hardware to run it.

    16. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      is that you have to (AFAIK) buy a Mac to develop for it.

      I didn't (and absolutely won't) buy a mac, and I'm developing quite happily for iOS. Just grab yourself a hackintosh CD and you're good to go. Oh, and a large bottle of aspirin, cause getting it installed is a headache. Once it's up and runnning, it's quite nice though

    17. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      On some piece of shit machine you got free out of a dumpster/GumTree/Craigslist

    18. Re:Biggest problem with iOS development by markdavis · · Score: 1

      Indeed. But with Android development, it doesn't MATTER which platform you have because it will work with Linux, MS-Windows, and MacOS. So let's review:

      Android development: Most any platform. So you don't have to buy anything, what you already have will very likely work.

      Windows development: MS-Windows machine only

      iOS development: MacOS machine only

    19. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      A bigger problem than the Apple hardware requirement is the requirement that developers use xcode. iOS development should be avoided unless you like being foced to use development tools that have been shoe-horned into some bug-ridden, monolithic pile of shit.

    20. Re:Biggest problem with iOS development by VortexCortex · · Score: 1

      you have to (AFAIK) buy a Mac to develop for it

      As I understand it, you have to buy a PC with Windows to develop for Windows Phone 7. Or you have to buy a retail copy of Windows to run in dual-boot or virtualization, which is as expensive as just buying an entry-level PC due to deep OEM discounts. (Once in Best Buy, I've seen a retail copy of Windows Home Premium for $200 and an ION nettop PC with included Windows Home Premium for $200.)

      ::Sigh:: Or, you can build a faster machine for cheaper yourself... Avoid the OEM all together. You still have to purchase Windows to develop WP7 (& Windows apps, but I use Linux + Wine to cross compile some of my Win apps sans VM or dual-boot), but at least YOU CAN.

      The problem for me is that I have hardware that is faster than anything that Apple sells right now, and I purchased it for less than 2/3rds the price of Apple's most comparable systems... I saw that I can purchase the Mac Box Set with Snow Leopard for $169.00, but IT REFUSES TO RUN ON MY HARDWARE.

      That, my friend, is why I don't develop for iOS or other Apple OSs.

      You may attempt a rebuttal claiming that Apple doesn't want to support any unsanctioned hardware, and go on about "complete experience", but I'll shoot you down immediately because I install ALL of my O.S.s in a virtual machine -- there is no "hardware differences" that Apple's software would have to support except the lack of a hardware DRM system that Apple uses to prevent me from installing their inferior OS on my superior hardware. Besides, OSX runs on the same Intel brand CPU that I purchased... and, in fact, I have an illegal VM image (Hackintosh) that runs just fine, so OSX Can and Does run under this environment -- But I refuse to use it to develop software since it's illegal.

      The problem isn't that I can't afford to purchase Apple hardware, it's that I have to have a special build environment just for their over priced hardware and software DRM solution to operate legally... That, and I've already purchased better hardware than they sell...

      When people ask why my apps run on Windows and Linux but not Mac I always reply: Because Apple's DRM makes it illegal to use OSX on my hardware, neither Linux or Windows does. Apple would rather lock things down than let me compile my code on my hardware with their OS.

    21. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      $600 bucks. XCode is free. Many smartphones cost that much without a contract.

    22. Re:Biggest problem with iOS development by murphtall · · Score: 1

      what if that computer is a mac g5?

    23. Re:Biggest problem with iOS development by moonbender · · Score: 1

      Professional devs, sure, people who're interested in making money from it. Who cares about them? This is Slashdot, we like tinkering with computers, the lower the entry barrier the better. Your final sentence says it all: you're interested in a polished end product, to the point that your happy that hobbists are excluded from the platform. Nothing wrong with thinking that per se, but it's a consumer's perspective; it might be better served by, I don't know, Gizmodo or something.

      --
      Switch back to Slashdot's D1 system.
    24. Re:Biggest problem with iOS development by Karlt1 · · Score: 4, Funny

      is that you have to (AFAIK) buy a Mac to develop for it. I can't really fault Apple on this as it's a great business strategy, but I simply can't be bothered so I'll only make apps for Android, which doesn't require me to buy hardware.

      All you have to buy is a dozen different phones to make sure your app is compatible and then enjoy on average 5% of the sales of the Apple app store....

    25. Re:Biggest problem with iOS development by phantomfive · · Score: 1

      Programming for Windows Phone requires either Vista or Windows 7. But I don't forsee Microsoft changing that at all.

      --
      "First they came for the slanderers and i said nothing."
    26. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      "installing their inferior OS on my superior hardware."

      That's where you lost me. I stopped reading once the bias became that obvious.

    27. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      I have hardware that is faster than anything that Apple sells right now

      You have over 12 cores and more that 64GB of RAM? Lucky...

    28. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      More of a reply to all of your other replies...

      From a professional developer point of view, I can just write for WP7 at no extra cost. I can do the same for Android. Being honest, if the Appstore was depending on iOS developers, it'd have died a death years ago. As a result, I sold my iPhone as I'm never going to shell out for a computer just for one task (OK, I did for xbmc but that's different).

      For the amateurs, once again, WP7 is free using express and Android is always going to be free. Not true of iOS. You're unlikely to own a Mac, so you have to pay for that, at very least.

      WP7 is still sorely lacking in lots of places. Crappy camera API, crappy bluetooth, slighly half assed components, poorly documented and spread over all the place. But it'll improve and it won't have the basic crippling restriction.

    29. Re:Biggest problem with iOS development by tepples · · Score: 1

      I use Linux + Wine to cross compile some of my Win apps

      And what to test them? If you're using Wine other than as a toolkit for making Linux apps, you need to test on Windows.

      I have hardware that is faster than anything that Apple sells right now

      Which hardware might that be, may I ask?

      I install ALL of my O.S.s in a virtual machine

      Recent VirtualBox can run Mac OS X. Which host OS do you use to run your virtual machine?

      it's that I have to have a special build environment just for their over priced hardware and software DRM solution to operate legally

      A Mac mini costs $600. Is that more overpriced than what, say, Sony and Nintendo charge for their development equipment?

    30. Re:Biggest problem with iOS development by jo_ham · · Score: 2

      So buy a cheap second hand Intel Mac from ebay or something, or buy a broken one and fix it up, since tinkering is what we do. You can get some serious deals on cheap Macs with busted screens or damaged bits and it's cheap to repair them - no more expensive than a PC.

      Thinking that "low barrier to entry" means "new" is ok, nothing wrong with that per se, but it's a non-hobbyist's perspective. Might be better served by, I don't know, Dell.com or something.

    31. Re:Biggest problem with iOS development by makomk · · Score: 1

      And what to test them? If you're using Wine other than as a toolkit for making Linux apps, you need to test on Windows.

      You're assuming that all builds are actually tested. It's not uncommon to have regular builds - even automated ones - that aren't necessarily tested on all platforms, at least for open source projects. Being able to compile Windows applications under Linux can make that a lot easier, whereas the fact that Mac applications can only be compiled on Macs is a huge pain...

    32. Re:Biggest problem with iOS development by jo_ham · · Score: 4, Insightful

      Right, you're ditching the most profitable market because... why? The dev tools only run on the OS the phone's OS is based on? The app store paid developers a combined 2 billion dollars in revenue (after Apple's cut). Nothing else is even close right now.

      Hilarious.

      I believe the phrase is "cutting off your nose to spite your face". If you're talking "as a professional developer" (ie, if you are making your living from this).

      For the casual developer just messing about, sure you need a Mac, but you can pick one up cheaply on eBay that will do the job just fine. Alternatively you can just build a hackintosh and see what's what before committing to buying new or used hardware.

    33. Re:Biggest problem with iOS development by moonbender · · Score: 1

      Oddly enough, there are hobbyists who like tinkering with software but not with hardware... There's nothing wrong with a high barrier to entry, but there's something wrong with arbitrarily raising it -- unless you're doing it because of the high barrier to entry, as in Brainfuck or Intercal coding.

      --
      Switch back to Slashdot's D1 system.
    34. Re:Biggest problem with iOS development by coolgeek · · Score: 1

      I'd rather buy one computer than 20 smartphones.

      --

      cat /dev/null >sig
    35. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      you forgot something regarding android, the dozen of so phones you need to buy to test on actual hardware.

    36. Re:Biggest problem with iOS development by MightyYar · · Score: 1

      Being able to compile Windows applications under Linux can make that a lot easier, whereas the fact that Mac applications can only be compiled on Macs is a huge pain...

      You are clearly open to tools like Wine. Can't you use a tool like GnuStep to cross-compile to OSX from Linux? It sounds like a huge pain in the ass vs. just having an old headless Mac to run a compiler on, but you could put it together if you wanted to stay purely open source.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    37. Re:Biggest problem with iOS development by Coward+Anonymous · · Score: 1

      This claim is a red herring for a serious developer. The upfront cost of the Apple HW required for development is minuscule. It is tiny compared to the hours of work you'll spend developing any app and, more importantly, it's tiny compared to the income you'll generate from your, obviously, block buster apps.

      If this is just a hobby and you have no intention or chance in hell of making money, the HW cost is a valid concern. However, your scenario is not important in the real world. It's the professional developers that matter and from that point of view the HW cost is laughably small.

    38. Re:Biggest problem with iOS development by jo_ham · · Score: 1

      And you make my point for me. We're not all the same. Some of us don't want to mess around with getting hardware to work etc and just buy something that is turnkey. Some like to build everything by hand.

      I'm not sure it's arbitrarily raising the barrier - the toolchain for iOS development is based on the one that is used for OS X, given that the two OSes share the same core. It's not like Apple deliberately said "aha, what a great way to drive OS X adoption!". It's merely a side effect of OS X only running on Apple hardware, which has been done to death - they're simply not in the business of making an OS for generic boxes.

      It also depends where you start from - for me the barrier to entry to Windows Phone 7 development is "arbitrarily high" since you need to do it on Windows. It would be far easier if they ported the toolset to OS X for me!

    39. Re:Biggest problem with iOS development by am+2k · · Score: 1

      You may attempt a rebuttal claiming that Apple doesn't want to support any unsanctioned hardware, and go on about "complete experience", but I'll shoot you down immediately because I install ALL of my O.S.s in a virtual machine -- there is no "hardware differences" that Apple's software would have to support except the lack of a hardware DRM system that Apple uses to prevent me from installing their inferior OS on my superior hardware.

      And you know what? Apple doesn't care about your fringe desires. Just as Microsoft doesn't care, it's just that their solution happens to work on your machine. In business, you have to learn that you can't please everyone, and that you have to reduce your target customer base to whatever is most profitable, otherwise you'll never have a shipping product.

    40. Re:Biggest problem with iOS development by markdavis · · Score: 1

      Nonsense. If you follow the rules, the application will work on all phones running the same version of the OS and most phones running a close version. The emulator allows you to try the app on different resolutions, CPU speeds, etc.

    41. Re:Biggest problem with iOS development by caywen · · Score: 1

      That's not really the problem. Having a Mac toolkit isn't somehow going to magically bump them to 100,000 apps. If they want WP7 to succeed, they should focus on what they are supposedly currently focusing on: Selling as many WP7 devices as possible.

      If the market is there, developers will buy the hardware. I bought a new $2000 MBP just to develop for iPhone. If WP7 had the same market size, I wouldn't hesitate to drop $1000 on a Windows laptop. I certainly wouldn't hesitate to fork over $199 for a Windows license for use in Parallels.

    42. Re:Biggest problem with iOS development by DanielSmedegaardBuus · · Score: 1

      Then he'd use that.

    43. Re:Biggest problem with iOS development by DanielSmedegaardBuus · · Score: 1

      Having to buy the target device hardware you're developing for and having to buy new hardware to provide your development platform are two different things. The argument made was not whether or not you should buy a phone (both dev environments provide emulators anyway), but if you were forced to buy a new computer.

    44. Re:Biggest problem with iOS development by Moondevil · · Score: 1

      That is what many developers fail to see. At the end of the day, a PC + Visual Studio costs more than a Mac, which provides all the developer tools together with the operating system.

      It is true that you can get the Windows SDK + Visual Studio express versions for free, but those are the light versions, so to speak.

    45. Re:Biggest problem with iOS development by iampiti · · Score: 1

      If Apple requires a Mac computer for developing for iOS Microsoft requires a Windows OS for developing for Windows Phone. It seems very unlikely that this is going to change, since, as you probably know everything MS does is tied to Windows. So the only major phone OS that lets you develop on several platforms is Android (WebOS, Meego and others may be that way too but they're not mainstream)

    46. Re:Biggest problem with iOS development by gig · · Score: 1

      That is great news. If you don't use a Mac, then we don't want your app running on iOS. If you're used to using Windows or X-Windows then, yes, Android has the level of quality that you'll feel comfortable with, and iOS would seem much too demanding. You wouldn't understand why either Apple or the user base rejects your app.

      It's not some business strategy that iOS development requires a Mac. They simply did not port Xcode to Windows, because that would mean porting the whole of Mac OS. In the same way that programming Windows requires Windows, programming a Mac requires a Mac. And iOS is just a Mac with touch instead of mouse, so yes you need a Mac to program it. It's really basic.

    47. Re:Biggest problem with iOS development by gig · · Score: 1

      A MacBook Air costs $400 per year over 3 years, including AppleCare. It is easy to make that pay for itself by doing iOS app development. If that doesn't sound good to you, then you're not interested. That has nothing to do with Apple not participating in the generic PC industry.

    48. Re:Biggest problem with iOS development by gig · · Score: 1

      The majority of developers that I know have Macs. This thread started by talking about developing for Android because you don't want to buy a Mac. Well, Google is 75% Macs.

    49. Re:Biggest problem with iOS development by gig · · Score: 1

      Yeah, but Android apps are not native. You can develop for the Web on any platform, too. But if you want the power of a native app, you need a native toolkit.

      You get so much more with iOS development, and you make so much more money that the cost of the Mac is immaterial. Plus, once you get one, you find it is the best PC you ever owned and forget you were whining about it. I haven't heard a single iOS developer complain about having to use a Mac. You get free developer tools with it that are worth the purchase price all by themselves.

    50. Re:Biggest problem with iOS development by cyber-vandal · · Score: 1

      It's illegal to run Mac OS X on anything but a Mac and I have no idea where Sony and Nintendo come into an argument about why someone doesn't want to pay for a Mac when they already have an Intel machine. There is no good technical reason why Mac OS X can't run on any modern PC but that is restricted by Apple and requires you to break the law to get it to work. That's okay for an individual I suppose but anyone running a business should be very wary of using illegal software.

    51. Re:Biggest problem with iOS development by UnknowingFool · · Score: 1

      It's not illegal. It's merely unsupported by Apple. Legality comes into play when you sell the machine. That's why Apple went after Psystar whose entire business model was to modify and redistribute OS X without Apple's permission. People who build hackintoshes for a hobby and then get rid of them later on eBay are in a legal grey area but Apple has not pursued legal action against them.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    52. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      When people ask why my apps run on Windows and Linux but not Mac

      Another fantasy post. What's with you people? You know all that crap you just wrote is what you think you would do. And just what apps are those? More fantasy, or some two-day single-purpose utilities?

    53. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      Oh please, just is just a load a baloney. Allowing a OS to run on a virtual machine requires exactly 0 man-hours. But instead they spent thousands of man-hours developing an anti-feature DRM scheme to make sure their OS only ran on their hardware. And the EULA says that you can't even try, which is a hell of a lot different that saying, we know a few people might want this feature, but we are unable to provide any support because there aren't enough people who want it..

    54. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      What a Demi God! I dont think I am missing any of YOUR software on a Mac or Win!

    55. Re:Biggest problem with iOS development by Anonymous Coward · · Score: 0

      If you are broke you really don't have much of a chance of breaching any market.

    56. Re:Biggest problem with iOS development by exomondo · · Score: 1

      I know Android developers who have bought a dozen or more different Android phones on which to test their software.

      They needed to test on 12 or more devices? How many significantly different configurations are there?

    57. Re:Biggest problem with iOS development by cyber-vandal · · Score: 1

      The EULA says different but you keep telling yourself it's fine. Just before a BSA audit costs your company a fortune.

    58. Re:Biggest problem with iOS development by exomondo · · Score: 1

      And you know what? Apple doesn't care about your fringe desires.

      On the contrary they spend quite a lot of money on DRM 'solutions' to deliberately disallow his 'fringe desires'. For his 'fringe desires' to be fulfilled they don't have to do anything except stop spending time and money on DRM lockouts.

    59. Re:Biggest problem with iOS development by exomondo · · Score: 1

      That is what many developers fail to see. At the end of the day, a PC + Visual Studio costs more than a Mac, which provides all the developer tools together with the operating system.

      It is true that you can get the Windows SDK + Visual Studio express versions for free, but those are the light versions, so to speak.

      And what you fail to see is that there is no need to buy Visual Studio when developing for WP7, the version you use is the free Visual Studio 2010 Express for Windows Phone.

    60. Re:Biggest problem with iOS development by exomondo · · Score: 1

      Of course if one is happy with a development environment that "lack the full breadth of features found in higher-end Visual Studio and SQL Server Editions" and all one wants to be is a "hobbyist, student, and novice developer" then one can develop for MS Windows Phone 7. Otherwise it costs $1300 with a $800 yearly upgrade.

      And what exactly do you need in the higher end versions of Visual Studio that you don't get in the version explicitly for WP7 development?

      Over three years, for a professional developer, not someone who is just knocking off fart applications, this is $1000 for the iPhone vesus $2900 for the MS WIndows Phone 7.

      Don't project your inability to create anything beyond 'fart applications' with the WP version of VS2010 express onto other developers.

    61. Re:Biggest problem with iOS development by UnknowingFool · · Score: 1

      EULA cannot trump law. And what does my company have to do with anything that I do as a hobby?

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    62. Re:Biggest problem with iOS development by cyber-vandal · · Score: 1

      When people ask why my apps run on Windows and Linux but not Mac I always reply: Because Apple's DRM makes it illegal to use OSX on my hardware, neither Linux or Windows does. Apple would rather lock things down than let me compile my code on my hardware with their OS.

      Not talking about you am I. Read up. As for EULA not trumping law have a read of this: http://en.wikipedia.org/wiki/Software_license_agreement. Apart from anything else, even if the EULA isn't enforceable good luck taking on Apple in court.

    63. Re:Biggest problem with iOS development by VortexCortex · · Score: 1

      Being able to compile Windows applications under Linux can make that a lot easier, whereas the fact that Mac applications can only be compiled on Macs is a huge pain...

      You are clearly open to tools like Wine. Can't you use a tool like GnuStep to cross-compile to OSX from Linux? It sounds like a huge pain in the ass vs. just having an old headless Mac to run a compiler on, but you could put it together if you wanted to stay purely open source.

      Yes, I've got cross compilers -- The problem is testing. I can re-boot nearly all of my x86 and x64 machines into various flavors of either Linux or Windows, or fire up a different OS in a VM to do a quick test or compile. I don't care about having to purchase additional OS licenses to do debugging / testing with! The problem is that IT'S ILLEGAL for me to run Apple's OSX on my hardware.

      Therefore, the actual tests in a real working system that I consider essential to the release process, are impossible unless I purchase some inferior Apple hardware. Sorry -- I always tell people that if they want my code to run on Apple's OSX, then feel free to compile it (and resolve the implementation differences) yourself -- No one has done so yet, thus OSX is not an important target, or else my apps are not important for OSX users (why waste the time on a OS port if it's not important?).

      I can legally / easily test my Windows vs Linux branches & compare differences on the same hardware, and on a variety of different hardware (this is important esp. with floating point inconsistencies I've uncovered), the same can not be said of OSX (if I only had more expensive Apple machines my code would still have those FPU errors in it). Thus, I produce win and lin and bsd binaries -- If Apple had less OS DRM, I would produce binaries for their OS too.

      Note: By implementation differences, I mean things like file opening / locking issues, named pipes & networking issues, and window management -- totally different batches of code in the wrappers for lin vs win, and sometimes bsd vs lin... Without a full OS to test in, there is no feasible work-flow for me. Also note: I've tried Qt and other cross platform frameworks (Java, gtk) -- Same issues, unpredictable applications (added foreign code & complexity == increased surface for bugs to appear), and testing is still a must. "Write Once - Debug Everywhere" (I can't debug my code on a platform == I don't release code for that platform; Thus I do have AMD, Intel and ARM build/test machines). I see no reason to spend more money to get less power, perhaps someday someone will donate a decent Mac, until then, tough luck: Apple seems hostile to devs like me).

    64. Re:Biggest problem with iOS development by makomk · · Score: 1

      Can't you use a tool like GnuStep to cross-compile to OSX from Linux? It sounds like a huge pain in the ass vs. just having an old headless Mac to run a compiler on, but you could put it together if you wanted to stay purely open source.

      I don't think this is possible. While there does appear to to be a way to cross-compile for OSX from Linux, it's a really hairy set-up involving Apple's custom gcc fork and extracting proprietary libraries and headers from the Xcode .dmg. GnuStep isn't even targetting binary compatibility with Apple's libraries.

  8. Viable for small shops? by Tibor+the+Hun · · Score: 1

    This may be viable for shops with enough manpower to support multiple OSs and devices, but many one, two or three man shops may not have the resources to deal with support for some low-spec phone so far removed from the basics they can count on iOS.

    --
    If you don't know what AltaVista is (was), get off my lawn.
    1. Re:Viable for small shops? by cbhacking · · Score: 1

      Umm... way to comment with absolutley no <expletive deleted> clue what you're talking about. That argument may be valid for Android, which is avialb le on a wide range of hardware including some very low-end devices, but all WP7 phones have to meet a pretty high-end spec (1GHz proc, 800x480 resolution, 512MB of RAM, certain GPU requirements, 4-point multi-touch, and a suite of sensors). There are better phones available, of course, but only recently; that specification was finalized somewhere near a year ago. Additionally, it's a minimum, not an exact requirement. Presumably, the minimum spec will be updated over time.

      For the record, the iPhone 4 may meet the CPU spec (the iPad does, but only just; it's unknown whether the iPhone cloock speed is the same). I believe it meets the GPU spec, but I'm not sure about that. It meets the RAM spec. It exceeds the minimum resolution but has the minimum viewable screen area. It meets the sensor spec, including an optional feature (gyro) and adds a second camera. It exceeds the minimum storage. Sounds good, right?

      On the other hand, if you're writing apps for Apple you probably want to support the 3GS as well. The 3GS fails almost every portion of the WP7 spec except sensors. In particular, it's slower, has less RAM, and has a low-resolution display - overall, it's a much less powerful device. Given its age, that's completely reasonable, but it's still an argument against targeting iOS for development - you've either got to support old devices with much worse hardware, or you've got to exclude everybody who hasn't upgraded to the newest generation.

      --
      There's no place I could be, since I've found Serenity...
    2. Re:Viable for small shops? by Dog-Cow · · Score: 0

      If older hardware merely existing is a minus against iOS, it's a good thing you're not a developer. You're so incredibly stupid, it's almost unbelievable.

  9. No standard C++ on Windows Phone 7 by tepples · · Score: 4, Insightful

    WP7 is a charm for developers.

    Except those developers who already have a library of application logic code written in standard C++ or Objective-C. On Mac OS X and iOS, a front-end written in Objective-C can link to application logic written in standard C++, and Android provides NDK to allow using standard C++ application logic with a Java front end. (It might be possible to use ObjC on Android through GCC or Clang, but I haven't heard about it.) But WP7, like Xbox Live Indie Games, can use only verifiably type-safe code. Microsoft's C++/CLI is a language that includes both Standard C++ and a C++-like verifiably type-safe language as subsets, but Windows Phone 7 will reject any assembly that uses unverifiable operations, such as any use of the Standard C++ syntax for pointers or references. So how does one translate Standard C++ into the verifiably type-safe subset (/clr:safe) of C++/CLI, other than doing it manually line-by-line and then trying to maintain two versions in parallel?

    1. Re:No standard C++ on Windows Phone 7 by zach_the_lizard · · Score: 1

      C++/CLI is not allowed on WP7, because it can emit bytecode not supported there even in the simplest of operations. This was the case with Silverlight (which WP7 is based off of). Not sure if /clr:safe would fix that.

      --
      SSC
    2. Re:No standard C++ on Windows Phone 7 by tepples · · Score: 1

      Standard Objective-C?

      I don't see that.

      Oh and "standard C++" sucks compared to standard Java or standard C#.

      Was this true years ago when the application was first developed? Back then, Java still had a reputation for using far more RAM and CPU than C++. Besides, how does one port the logic of an application written in standard Java to Windows Phone 7 and iOS without a rewrite and parallel maintenance?

    3. Re:No standard C++ on Windows Phone 7 by Anonymous Coward · · Score: 0

      Why use Java when you can use a much better language with much better tools like C#? It does run on everything you know.

    4. Re:No standard C++ on Windows Phone 7 by tepples · · Score: 1

      Why use Java when you can use a much better language with much better tools like C#? It does run on everything you know.

      I hope that's sarcasm. The tools to run C# on iOS or Android devices are currently cost prohibitive for hobbyists. (As I understand it, hobbyist is the phase between college student and employed.)

    5. Re:No standard C++ on Windows Phone 7 by jo_ham · · Score: 1

      He very, very clearly states that "standard" refers to C++ (as he mentions it in full each time) and that the adjective does not apply to Objective C, where it is not used a prefix at all.

      Apple troll wilfully misinterprets anything with a slight positive spin on anything related to Apple! Film at 11.

    6. Re:No standard C++ on Windows Phone 7 by shutdown+-p+now · · Score: 1

      Actually, /clr:safe would work. The problem is that this gives you a very limited subset of the language. You can use all the basic operators, and you can define functions. But when it comes to types, you cannot even use "class" or "struct", or C arrays or pointers - only CLI "ref class" and "value class" and managed handles & refs, and arrays/strings. The result is more or less C# with C++ look and feel, RAII (since you still get destructors), and templates.

      It is possible to use macros that would expand into "ref class" etc for WP7, and standard "class" everywhere else, and write your entire code that way, such that it is portable between all platforms. The problem is that this only works when you start from scratch; when you already have an existing body of C++ code, there's no good solution.

    7. Re:No standard C++ on Windows Phone 7 by shutdown+-p+now · · Score: 1

      "standard C++" sucks compared to standard Java or standard C#.

      Ah, Slashdot - the place where intellectuals have polite disputes over arcane matters of importance, and arguments are well-founded and supported by numerous references!

  10. Microsoft's Developer Motel by Anonymous Coward · · Score: 1

    Developers check in ... but they don't check out!

  11. Re:Other way around! by Spaseboy · · Score: 3, Insightful

    Microsoft and Apple have switched positions. You have GOT to know how much this stings executives at Microsoft and pisses off MS shareholders. MS has already blown that chance at corporate with their phone OS by fucking over the 6.x using companies.

    Until 7, it was an easy migration path for corps and simple to upgrade phones for users. Now there is no upgrade path, so the door is open to choose another platform. No other platform than iOS offers businesses the control and abilities they need with a standard hardware interconnect for custom applications. Vertical markets are choosing iOS.

    Their only chance really was the consumer market and they fucked that opportunity with the Zune and Kin fiascos.

    --
    "I don't want more choice, I just want nicer things!"
    -Jennifer Saunders as Edina Monsoon
  12. Re:Other way around! by CODiNE · · Score: 1

    Now if only a tool to do the reverse existed.

    Perhaps you could sorta read that document .. in reverse?

    --
    Cwm, fjord-bank glyphs vext quiz
  13. "And figure out ways to get the code to work" by The+O+Rly+Factor · · Score: 5, Funny

    Sounds like Microsoft development in a nutshell.

    1. Re:"And figure out ways to get the code to work" by Anonymous Coward · · Score: 0

      plz can you email me teh codez? this is super urgent critical i have teh codez i gogled but found ntohings

  14. Re:Other way around! by Anonymous Coward · · Score: 0

    They go with blackberry. iOS lol.

  15. Re:Other way around! by shmlco · · Score: 2

    "On the other hand, having to deal with Objective-C to code for IOS is a pain."

    GC on iOS would be nice. OTOH, the NARC and autorelease rules are pretty straightforward, and in practice it's fairly hard to screw them up. OC isn't as simple as JavaScript, but then again, it's not the hell-on-earth that is C++ with STL and user-overloaded everything. Love the delegate system, and the dynamic selector mechanisms are pretty cool.

    The Cocoa Touch frameworks are powerful, much better than Android's, and there are a lot of frameworks like MFMailComposeViewController and MPMoviePlayerViewController that do a ton of work for you with a very few lines of code. Love the new UISwipeGestureRecognizers. As you can see, Cocoa is pretty verbose, but Xcode's autocompletion tools knock it down to a manageable level. Tight integration with the LLVM compiler.

    All in all, it's a pretty good language, especially considering that it was created about 30 years ago. Objective-C is based on SmallTalk, which is too bad, 'cause I think using a full-blown SmallTalk system for iOS development would have been a blast.

    Besides, learning a new language opens your mind a little, exposes you to knew ideas, stirs the creative juices, and all that... (grin)

    --
    Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
  16. Your figures are bogus. by Anonymous Coward · · Score: 0

    Bare minimum to develop - slow but it'll get the job done.

    New Mac Mini $600 no moinitor with OS

    New PC $300 no monitor with OS.

    Developing for anything Apple is more expensive than any other platform.

    And I wont get into all the added hoops that Apple development entails - like paying $99 to join the Developer Network just to be able to put your own app on your own device?!?

    1. Re:Your figures are bogus. by UnknowingFool · · Score: 3, Informative

      And I wont get into all the added hoops that Apple development entails - like paying $99 to join the Developer Network just to be able to put your own app on your own device?!?

      No, $99 is if you wish to publish your apps to iTunes. It costs you nothing to develop on your own device. I think to publish to Windows Marketplace is about the same price.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    2. Re:Your figures are bogus. by tepples · · Score: 1

      $99 is if you wish to publish your apps to iTunes. It costs you nothing to develop on your own device.

      When was this changed? Or are you referring to jailbreaking?

    3. Re:Your figures are bogus. by davester666 · · Score: 2

      Um, I believe you still need to fork over the $99 to be able to get the executables onto your iDevice [as it still have to be signed by Apple to run] unless you jailbreak your iDevice.

      You only get to run your app in an emulator on your Mac for free.

      --
      Sleep your way to a whiter smile...date a dentist!
    4. Re:Your figures are bogus. by _xeno_ · · Score: 1

      You only get to run your app in an emulator on your Mac for free.

      Not any more. XCode is now $5 on the Mac App Store.

      And I'm not sure how many updates to XCode that $5 covers.

      --
      You are in a maze of twisty little relative jumps, all alike.
    5. Re:Your figures are bogus. by davester666 · · Score: 2

      You can still download v3.x for free [after signing up for a free developers account], which includes the emulator.

      As well as just installing XCode from the DVD included with your Mac (and/or Snow Leopard Installer DVD). I'm not sure if it is still being included with the most recently released Mac's, but it's been included on the DVD's for years.

      --
      Sleep your way to a whiter smile...date a dentist!
    6. Re:Your figures are bogus. by toriver · · Score: 1

      Yes, the $99/year gives access to the developer services that include generating the certificates, keys and profiles necessary to get an iOS device to accept apps signed using those certificates.

      How much does a Windows Phone 7 code signing certificate cost, though?

    7. Re:Your figures are bogus. by iinlane · · Score: 1

      I wonder why they ask the $5 for it. The XCode is worth thousands of dollars but apple chose to give it away for free. Comparing to the actual price the $5 is as good as free but creates a small entry barrier in sense I have to go searching for my credit card or iTunes store credentials. Maybe they want us to be all set for publishing once we get this XCode running on our machines making the iTunes account creation a part of installation process.

    8. Re:Your figures are bogus. by iinlane · · Score: 1

      Good developer tools cost money. A lot of money. If you think that Apple or Microsoft make profit on this $99 then you're mistaken.
      Don't be cheap and just buy those damn licenses if you're really interested or leave it if you aren't. There are far too many "me too" apps in android store diluting the value of professional made apps making the android worth less for developers and consumers.

    9. Re:Your figures are bogus. by tlhIngan · · Score: 2

      I wonder why they ask the $5 for it. The XCode is worth thousands of dollars but apple chose to give it away for free. Comparing to the actual price the $5 is as good as free but creates a small entry barrier in sense I have to go searching for my credit card or iTunes store credentials. Maybe they want us to be all set for publishing once we get this XCode running on our machines making the iTunes account creation a part of installation process.

      SOX compliance.

      Xcode4 contains so many new significant features and changes that if Apple gave it for free, they'd have to restate their revenue numbers (because they've already recognized the "revenue" for Xcode 3.x in the cost of a Snow Leopard).

      XCode 3.x is still free because there's no new features.

      Apple's recognizes revenue for most of their products at the time of purchase. For the iPhone, they split it over 2 years. Microsoft recognizes revenue for all their sales over 3 years or so.

    10. Re:Your figures are bogus. by Kalriath · · Score: 2

      I still cannot fathom how every company in the world is capable of giving you updates to a product you got from them for free without attracting SEC investigators and IRS auditors out the wazoo. Every company in the world, that is, except Apple. Unless... here's the most likely reason... the "SOX compliance" issue is a load of bullshit.

      Just as a reminder, here's a nonexhaustive list of companies who can give you updates to products from them for free:
      Sony
      Microsoft
      Nintendo
      Dell
      HP
      Samsung
      HTC
      Google

      And now here's an exhaustive list of companies that have to charge you "for SOX compliance reasons":
      Apple

      Unless there's a section of SOX that starts off with "If you are Apple Incorporated..." then this excuse is crap.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    11. Re:Your figures are bogus. by Paradise+Pete · · Score: 1

      I wonder why they ask the $5 for it.

      It's a giant honking download. Maybe they simply wanted to keep a zillion people from downloading it just because they can.

    12. Re:Your figures are bogus. by CheerfulMacFanboy · · Score: 1

      I still cannot fathom how every company in the world is capable of giving you updates to a product you got from them for free without attracting SEC investigators and IRS auditors out the wazoo. Every company in the world, that is, except Apple. Unless... here's the most likely reason... the "SOX compliance" issue is a load of bullshit.

      Just as a reminder, here's a nonexhaustive list of companies who can give you updates to products from them for free: Sony Microsoft Nintendo Dell HP Samsung HTC Google

      And now here's an exhaustive list of companies that have to charge you "for SOX compliance reasons": Apple

      Unless there's a section of SOX that starts off with "If you are Apple Incorporated..." then this excuse is crap.

      So PSP to PSP2 was free, Windows Vista to 7 was free, GameCube to Wii was free ....

      --
      Fandroids hate facts.
    13. Re:Your figures are bogus. by Kalriath · · Score: 1

      Half of your examples are hardware upgrades, which are pretty obviously a bullshit analogy. The other was a completely new OS, when a closer analogy is Windows XP to Windows XP SP2 (which added about as many features as Leopard to Snow Leopard). Ever seen new features in a free Apple update? Me neither.

      But I don't expect you to accept that, your nickname alone makes it quite clear you can justify their behaviour in the face of insurmountable evidence. So I won't bother.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  17. Then how do I translate C++ into C#? by tepples · · Score: 1

    Then allow me to rephrase: So how does one translate application logic written in Standard C++ into C# or another WP7 supported language, other than doing it manually line-by-line and then trying to maintain two versions in parallel?

    1. Re:Then how do I translate C++ into C#? by Anonymous Coward · · Score: 0

      Rewrite once in C#, then use something like MonoTouch.

    2. Re:Then how do I translate C++ into C#? by tepples · · Score: 1

      I will point out that MonoTouch and Mono for Android aren't priced for developers trying to build a portfolio between having graduated and being hired or for people who program as a hobby.

    3. Re:Then how do I translate C++ into C#? by Anonymous Coward · · Score: 0

      Well you need a Mac to publish to the crApp Store, so the cost of developing for iOS is already high.

  18. William Campbell died the other day by Anonymous Coward · · Score: 1

    So Star Trek icon William Campbell, Trelane in the Squire of Gothos one of the best of TOS episodes ever, and Koloth in TOS and DS9 has died and there is nothing on Slashdot? How is this news for nerds? To bad he never submitted a bug report for some POS OSS because then maybe he'd be worth a story. Slashdot, you have disgusted me worse than Goatse x Tub Girl, please surrender your nerd credentials.

  19. Re:Other way around! by shmlco · · Score: 3, Insightful

    Blackberry's? Sorry, but corporate clients are abandoning the ship en masse. Market share is dropping and US sales in particular are tanking. The Storm line was il-received, and the Playbook is half-baked. Android app integration is going to kill QNX, just as Windows app integration put the final nail into OS/2.

    RIM is about to undergo a major implosion.

    --
    Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
  20. Re:Other way around! by mini+me · · Score: 1

    I like Objective-C. It is very Ruby-like. I think a lot of people come in thinking it is C++, or something, and entirely miss what makes the language so cool.

  21. Re:Other way around! by caywen · · Score: 2

    The real tragedy was the sheer short sightedness of the executive team. Windows Mobile went unchanged for 5 straight years. That management thought some hex-grid icon chooser thing would fix things was just mind bogglingly stupid. Kin just has the be mentioned and not explained. Even WP7 is having issues, but its chief problems are that it launched 2 years later than would be optimal, and Microsoft severely underestimating the complexity of updates. In truth, everything else looks pretty ok. It has a solid developer toolset, growing library of games and apps, and actual buy-in internally and from third parties.

    It's going to be a real hard slog for Microsoft to gain big market share. But the antitrust shackles are coming off, and co-marketing opportunities with Windows 8 might give WP7 a badly needed boost.

  22. Nintendo more expensive; M$ just as expensive by tepples · · Score: 5, Informative

    Developing for anything Apple is more expensive than any other platform.

    False. Developing for Nintendo handhelds is more expensive than developing for Apple handhelds. For one thing, just to be considered, you have to have a dedicated secure office separate from your home and a previous commercial title on another platform (according to warioworld.com). I'd look up information about developing for Sony handhelds, but http://www.tpr.scea.com/ has been down for three weeks.

    And I wont get into all the added hoops that Apple development entails - like paying $99 to join the Developer Network just to be able to put your own app on your own device?!?

    And I wont get into all the added hoops that Microsoft development entails - like paying $99 to join App Hub just to be able to put your own app on your own Windows Phone 7 or Xbox 360 device?!?

  23. Appple by Anonymous Coward · · Score: 0

    Is there a new company called Appple? Surely they're infringing on Apple's trademark

  24. Open WP7 to native developers by Moondevil · · Score: 1

    If Microsoft is really serious about convincing developers to port to WP7 from iPhone, they should offer native access to the platform to everyone and
    not just special partners.

    Most developer shops don't have enough resources to keep parallel versions of the application code in different languages.

  25. MonoTouch is more expensive than a Mac by tepples · · Score: 2

    Well you need a Mac to publish to the crApp Store, so the cost of developing for iOS is already high.

    MonoTouch is more expensive than a Mac. Here are all the costs that I've identified, which quickly (in my opinion) become prohibitive for a hobbyist.

    • Mac mini (for Xcode): $599, not recurring
    • Windows 7 (for Visual Studio Express): $200, not recurring
    • iPhone developer program: $297 for three years (includes Xcode updates)
    • Android developer registration: $25, not recurring
    • App Hub: $297 for three years (includes Visual Studio Express updates)
    • MonoTouch: $897 for three years ($399 for the first year, plus $249 per year after the first for updates)
    • Mono for Android: $597 for three years ($199 per year for MonoTouch licensees with valid update subscriptions

    And this doesn't include the price of phone service (a Windows Phone 7 device isn't sold as a PDA, unlike iPod touch and Archos 43, or even as a prepaid phone).

    1. Re:MonoTouch is more expensive than a Mac by zach_the_lizard · · Score: 1

      What I did was I bought a used device off of eBay for development with WP7. The previous owner left all of her text messages and emails on the device, and she kept writing about how she hated the phone so much. Needless to say, it didn't cost very much. You can test everything without a phone plan (minus any transfer speeds over edge or 3G). I suspect the same is the case for an iPhone (though I own one already) and Android (haven't done any work there).

      --
      SSC
    2. Re:MonoTouch is more expensive than a Mac by gbjbaanb · · Score: 1

      What I did was I bought a used device off of eBay for development with WP7. The previous owner left all of her text messages and emails on the device, and she kept writing about how she hated the phone so much

      This is your user base that you are developing your apps for. A wise businessman listens to his customers :)

    3. Re:MonoTouch is more expensive than a Mac by zach_the_lizard · · Score: 1

      Indeed. My current income from WP7 isn't spectacular, and quite frankly I feel that investing the same amount of time on Android would have been more fruitful. I have a game I'm coming out with for WP7 and XBLIG, and if the game doesn't reach a certain target, I may not renew the license. After this game and a project I'm working on for a company (the real reason I paid the $99), I'm shifting everything to Android and probably iOS (once I get new hardware).

      --
      SSC
    4. Re:MonoTouch is more expensive than a Mac by tepples · · Score: 1

      Other than XBLIG, how do you recommend that a hobbyist video game developer make a title on a TV-connected platform to add to a portfolio?

    5. Re:MonoTouch is more expensive than a Mac by Kalriath · · Score: 1

      And this doesn't include the price of phone service (a Windows Phone 7 device isn't sold as a PDA, unlike iPod touch and Archos 43, or even as a prepaid phone).

      Microsoft sells phones without a service plan directly for just this reason.

      Oh wait, that's the opposite of what you're saying. Anyway, go here: http://www.zones.com/windowsphonedeveloperpurchase

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    6. Re:MonoTouch is more expensive than a Mac by gbjbaanb · · Score: 1

      I think you'd be best off writing for iOS if you want to sell apps, the people who buy an iPhone are most likely to buy apps too. However, there is good money to be made from Android - but you're going to get more there from advertising revenue instead.

      I had a link a while back, someone with just a handful of Android apps was making $500 a month from them. I also know a friend who had a handful of apps, the for-sale ones had sold next to none but the free ones he released had strong download numbers.

      The guy who made Advanced Task Manager for Android earned $80,000 revenue over a year for it (but that was pretty well-featured in top apps in the marketplace). So good luck.

    7. Re:MonoTouch is more expensive than a Mac by exomondo · · Score: 1

      Indeed. My current income from WP7 isn't spectacular

      What app(s) is it derived from?

  26. Microsoft Standards! That's hilarious. by Anonymous Coward · · Score: 1

    Microsoft Standards don't even work with Microsoft Standards.

  27. How about a mapping tool for WM6 C# .NET? by NicknamesAreStupid · · Score: 1

    Duh, I guess they figure that those thousands of Windows Mobile developers, whose apps are now worthless, can fend for themselves. Actually, many of them went to the iPhone.

    1. Re:How about a mapping tool for WM6 C# .NET? by nog_lorp · · Score: 1

      "whose apps are now worthless" You say that as if they had worth at one time!

    2. Re:How about a mapping tool for WM6 C# .NET? by RogerWilco · · Score: 1

      A fried of mine works at a company where about 20 people make a living selling apps on Windows mobile to the medical world. They now have to do a serious rethink of their business because most of their software was tied to Windows CE/Mobile for the last 10 years. They'll probably go web-based, but then you're depending on the WiFi in the hospital.

      --
      RogerWilco the Adventurous Janitor
    3. Re:How about a mapping tool for WM6 C# .NET? by cbhacking · · Score: 1

      Um, C# is also used on WP7. WinMo supported native development, which WP7 doesn't (officially, it's possible unofficially) but the encouraged path was to use managed code. The UI needs to be re-written to use Silverlight, but the functional code can be re-used without any modification in many cases.

      --
      There's no place I could be, since I've found Serenity...
    4. Re:How about a mapping tool for WM6 C# .NET? by am+2k · · Score: 1

      They'll probably go web-based, but then you're depending on the WiFi in the hospital.

      Dunno about Windows Phone 7, but the iPhone runs offline HTML5 apps just fine (sans the new js engine, unfortunately).

    5. Re:How about a mapping tool for WM6 C# .NET? by am+2k · · Score: 1

      The UI needs to be re-written to use Silverlight, but the functional code can be re-used without any modification in many cases.

      That requires a clean MVC implementation, which most probably didn't do.

    6. Re:How about a mapping tool for WM6 C# .NET? by gig · · Score: 1

      Yeah, you can install an HTML5 app on iPhone from any server and run it side-by-side with native apps, regardless of Internet connection.

      The newer JS engine will likely come later, because of security concerns. Even so, you have hardware acceleration already, it is the best HTML5 environment.

  28. Re:Other way around! by SpryGuy · · Score: 1, Insightful

    I hate Objective-C (as do most developers I know). It's syntax is just annoying and awful. It's probably the number one reason I don't do any development for OS X or iOS.

    C# is vastly superior. I even perferred C++. Hell, I even liked Java better.

    --

    - Spryguy
    There are three kinds of people in this world: those that can count and those that can't
  29. How to? by nog_lorp · · Score: 2

    So let's see, what's the API to pop up the Apple App Store on Windows 7 phones? xD

  30. Not all calls have a parallel by Anonymous Coward · · Score: 0

    Wonder what it does when you point it at the iOS camera API?

  31. Guess they need to fix Bing first by Anonymous Coward · · Score: 0

    Seriously, go look for UIPageControl on bing - it's full of boobs!

  32. Re:The first step to meeting Microsoft's standards by jimmydigital · · Score: 1

    ...is lowering your own.

    Anyone else as surprised as I am that Microsoft HAS standards? All evidence points to the contrary...

    --
    Every normal man must be tempted, at times, to spit on his hands, hoist the black flag, and begin slitting throats. -HLM
  33. Re:Other way around! by guyminuslife · · Score: 1

    What would be really great is if they built this API mapping system... ...and then ensured that the Windows Phone 7 API would map to the desktop Windows API... ...and then you put Wine on a Linux-based phone...

    --
    I don't believe in time. It's a grand conspiracy designed to sell watches.
  34. Re:Other way around! by Ironhandx · · Score: 1

    The Storm I was ill-received. For good reason.

    Rather than rebranding and releasing as a new product and pushing it hard like they did the Storm I they left the Storm II to sit in the backlash of terrible Storm I brand experience, then discontinued it just as it was starting to gain steam as a viable contender in the group-think.

    End result is the same, but there was an entire series of bad calls at RIM that leads into their current situation.

  35. Let us see how they like their own medecine. by 140Mandak262Jamuna · · Score: 1
    Let us say they were able to map bulk of the API that does the actual work on the app. Let us even assume they kluge a virtual environment to let the app talk to "apple app store" and transfer it to MS app store and then hack some authentication too. After all one should be able to simulate enough of it in vm to get it going. Then what?

    Back in the days of Visual Studio 4 our company was doing mainly unix development. We hacked enough scripts to take the unix Imakefile and make it call the Visual Studio compilers and linkers to get the nightly build done on PCs. Main development was in unix. In version 4 or 5 they took away the command line. It was brought back later in v6 or so by the big players. But the damage was already done in our company. We had moved all the Imakefiles out, and wrote out vcproj files, and went to that nightmare called Mainsoft and the build env could never go back to Imakefile and linux when eventually much cheaper alternative to solaris, hpux, irix and Del Alpha emerged. One code base. Overnight builds. We did not need bounds checker or purify. Any memory error forgiven in one platform will crash in another.

    I just wish MS would sink a couple of billion dollars to make this kluge work and then Apple make enough tiny changes to the API to make it such pain they get the taste of what they were dishing out to others. I want Apple and Microsoft enter into such a slugfest most developers give up in disgust and move to some platform neutral development environment. I want the dev tool makers to have no incentive to push one platform over another. Would that day ever come?

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    1. Re:Let us see how they like their own medecine. by gig · · Score: 1

      If you want platform neutral, then make HTML5. That is what it is for. iOS supports both HTML5 and Cocoa so you can choose what is best for your app. App Store is totally optional on iOS, and didn't even ship until year 2.

  36. Nope, cannot virtualize by SuperKendall · · Score: 1

    Or you have to buy a retail copy of Windows to run in dual-boot or virtualization

    The last I heard the Windows Phone Seven emulator that you use for developing applications, would not run in a virtualized environment (perhaps it's really a virtualized instance of the phone OS itself?).

    Annoying anyway, and it's kept me from playing with the WP7 dev tools.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  37. Bad feeling... by SuperKendall · · Score: 1

    I'd look up information about developing for Sony handhelds, but http://www.tpr.scea.com/ has been down for three weeks.

    Between this and PSN, I'm starting to get the feeling that Sony has actually packed up and left the planet with all the money from Sony customers, leaving behind only an AI that issues random press releases to give them time to make a getaway...

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:Bad feeling... by Kalriath · · Score: 1

      Perhaps that's why they joined up with Valve/Steam?

      "Please assume the Party Escort Submission Position..."

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  38. App Hub is likewise $99 per year by tepples · · Score: 1

    How much does a Windows Phone 7 code signing certificate cost, though?

    The $99/year gives access to the developer services that include generating the certificates, keys and profiles necessary to get a Windows Phone 7 device to accept apps signed using those certificates.

  39. Re:Other way around! by mini+me · · Score: 1

    I admit the message passing interface is a little different, but I think the notation makes sense for highlighting messages given the practical constraints of the language. What else don't you like?

  40. Re:The first step to meeting Microsoft's standards by ozmanjusri · · Score: 1

    Anyone else as surprised as I am that Microsoft HAS standards?

    Of course they have standards! They bought ISO, didn't they?

    --
    "I've got more toys than Teruhisa Kitahara."
  41. mnemonic by Gary+W.+Longsine · · Score: 3, Funny

    It's easier to remember this stuff, when you recall that what actually happened was that NeXT acquired Apple for a negative four hundred million dollars ($US -400 million).

    --
    If you mod me down, I shall become more powerful than you could possibly imagine.
    1. Re:mnemonic by Samantha+Wright · · Score: 1

      And what a bargain it was!

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
  42. Ironic Reversal by Anonymous Coward · · Score: 0

    After so many years of developers struggling to adapt DirectX games to run on the Mac, this seems like a rather satisfying turnabout.

  43. Symbian is tha answer! by thaig · · Score: 1

    . . .. . but with Symbian you can develop on a Mac, Windows or Linux...... YAY! :-)

    --
    This is all just my personal opinion.
    1. Re:Symbian is tha answer! by gig · · Score: 4, Insightful

      What is Symbian?

    2. Re:Symbian is tha answer! by Kalriath · · Score: 2

      That's all well and good, but with Symbian what are you developing for?

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    3. Re:Symbian is tha answer! by thaig · · Score: 1

      I always take the bait, but just in case you are serious, it's a moble operating system. I was making the point that you have 3 options for your development environment. Symbian has had a huge bashing by some very self-satisfied people and I am enjoying pointing out that for all that, you aren't forced to buy a new computer to write software for it.

      Cheers :-)

      --
      This is all just my personal opinion.
  44. Re:Other way around! by shutdown+-p+now · · Score: 2

    The problem with Objective-C is that it has all the conciseness and execution speed of Smalltalk combined with all the ease of use and memory safety of C. ~

  45. Moonlight on Android by Gri3v3r · · Score: 1

    www.geek.com/articles/mobile/moonlight-dev-crew-brings-silverlight-to-android-20110415/

  46. Re:The first step to meeting Microsoft's standards by Anonymous Coward · · Score: 0

    It raises a difficult question though - lower, more open Microsoft standards or higher, incredibly locked-in Apple standards.

    And as a Linux/FOSS guy, I'm afraid I'm siding with Microsoft.

  47. Doesn't this sound familiar to anyone ? by slincolne · · Score: 1
    I can recall when Microsoft launched a product called Microsoft MS DOS 1.0.

    It's main claim to fame was that you could take your existing CP/M code, and with a few changes make it run on their new product.

    Of course all it did was suck programmers across to this new platform where people just stopped writing the old stuff.

    Has someone reopened the old play book ? Hello, Bill - is that you back again :-)

    1. Re:Doesn't this sound familiar to anyone ? by mario_grgic · · Score: 1

      There has been Wine Bottler (wrap entire windows app around Wine API and run on Linux) for a long time, but that alone is not enough to make everyone suddenly start using Linux. I don't think this is going to have profound effect that Microsoft is hoping. These people are just completely blind to why iOS is succeeding (otherwise they would probably come up with a viable competitor). iOS + well put together hardware + app eco system = complete refined user experience that's hard to replicate without a lot of work, strong vision and direction and impeccable execution. Microsoft just lack in the vision and direction department, they are showing again and again they can't innovate, and almost anything worthwhile they have was not thought of or developed (at least initially) in house.

      --
      As the island of our knowledge grows, so does the shore of our ignorance.
  48. WinOS2 anyone? by shorejsi · · Score: 1

    OK; I'm dating myself a bit here but back when OS/2 was more than a distant memory, IBM included a feature called WinOS2 that would allow you to run native Windows apps in OS/2. The intent was to lure developers to OS/2; it did exactly the opposite. It worked well enough that developers switched to Windows, knowing that using WinOS2 their products would also work under OS/2.

      This could have the same effect. The unintended message could be "do all your development under iOS, then do a quick port to WP7 to capture both markets." Only problem is, the 'ported' apps tend to look like exactly what they are...
     

  49. It's like a Kool-Aid to Kool-Aid flavor converter by Anonymous Coward · · Score: 0

    In goes "apple flavor Kool-aid", and out comes "orange flavor".

    I expect that the result is almost undrinkable.

  50. So does this mean by Anonymous Coward · · Score: 0

    we can now develop iPhone apps without the need for MacOSX?

  51. MS Apple by hardware1949 · · Score: 0

    How would that work? I mean would it be similar to piping the results of a Google search into Bing's search engine?

  52. Re:The first step to meeting Microsoft's standards by Anonymous Coward · · Score: 0

    Anyone else as surprised as I am that Microsoft HAS standards? All evidence points to the contrary...

    Well C# is more of a certified standard than Java is...