compiler
Latest
Code compiler pioneer Frances Allen dies at 88
Frances Allen, who helped invent the code compiler and parallel computing, has died at the age of 88.
Microsoft pulling free development tools for Windows 8 desktop apps, only lets you ride the Metro for free (update: confirmed)
Microsoft has instituted a big change with its free Visual Studio 11 Express suite that's leaving some current- and soon-to-be Windows 8 developers up in arms: it's pulling support for creating anything but Metro-native apps. After 11 becomes the norm, desktop developers will need to either cling to Visual Studio 2010 for dear life or fork over the $500 for Visual Studio 11 Professional. Programmers won't have the option of backdoor coding, either, with both the compiler and toolchain being pulled from Windows' framework. The situation doesn't represent the end of the world for some developers -- more established pros don't balk at a $500 price, and third-party tools will likely live on -- but it sets a much higher price of entry for desktop apps developed through the official route, especially if you want to write games using XNA. We've reached out to Microsoft for a response, but for now we'd suggest setting aside five Benjamins if Start screen tiles and app charms aren't your cups of tea. Update: We've confirmed with a Microsoft spokesperson that it's true you'll need Professional if you want to write desktop apps using Visual Studio. It's equally correct, though, that third-party developer kits will keep building desktop apps as long as they have their own compilers and related tools. Students can get Professional for free if they're in the Dreamspark program.
PhoneGap framework fine for App Store development, sez Apple
Now, we've all been concerned about recent updates to the iPhone dev agreement -- you haven't been sleeping and your parents are, quite frankly, worried for your sanity. And it's a heady subject: "what is the fate of PhoneGap in the wake of the iPhone OS 4 beta SDK?" Well, worry no more, little one -- it seems that Jesse Macfadyen, a contributor to the project, pinged Apple to make sure that users of the mobile development platform wouldn't find their apps rejected simply for using the tool. As you remember, the agreement states: "Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine" (and of course HTML and CSS are cool), so PhoneGap -- which indeed sticks to HTML, CSS and Javascript -- is totally safe. Now developers can get back to having their apps rejected for any number of other silly reasons. [Thanks, Bea]
Apple's iPhone lockdown: apps must be written in one of three languages, Adobe in the hurt locker
Apple's already got a veritable novella describing things you can't do with the iPhone as a developer -- create apps that execute their own code is the biggie, obviously, blocking technologies Flash and Java in the absence of a loophole -- but it seems they've locked down the ecosystem just a little further today with the release of the iPhone OS 4 beta SDK. Check out this snippet from the developer's agreement: Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited). What does that mean, exactly? Well, it means that technologies like Adobe's iPhone compiler in Flash CS5 won't be allowed, simply because the source code of the app that you're writing isn't in a language Apple's comfortable with. The compiler had been seen as a potential boon for Flash devs that had already been blocked out of the iPhone ecosystem for lack of a true Flash player, but Apple's found a way to block even this workaround -- technically you don't need to be using Apple's own tools, but you've got be using one of three variants of a single programming language. It's hard to say why Apple cares, exactly, but we suspect that the company would have to analyze your app pretty closely to detect variances in how the compiler produced your machine code in order to determine that you'd violated the rule. This could be a blow to publishers -- Condé Nast included -- who'd been banking on Adobe Air to lead the digital push, since those guys presumably won't be able to bring their issues to the iPhone (and, more importantly, the iPad) without violating the terms of Apple's agreement. Protectionism is a core element of the iPhone's success, in Apple's view -- but ultimately, this might come out as a decision that's difficult to defend, unnecessarily sours publishers to the platform, and turns Flash devs' heads just a little grayer than they already were.
Update on Intel's OS X Software Development Tools
I have a bit of an update to my previous post on Intel's release of Fortran, C , and Math Kernel Libraries for OS X. In an article at ZDNet, James Reinders of Intel notes that to take full advantage of the Intel Core Duo dual processors for OS X applications, programmers will need to use these tools. This sounds like a bit of marketing hutzpa, but maybe it's true that XCode in and of itself won't be tuned for dual core processors.Also, pricing has been released for the tools (currently in beta) set to release in Summer of 2006: Intel® C Compiler for Mac OS: $399 Intel® Fortran Compiler for Mac OS: $499 Intel® Math Kernel Library for Mac OS: $399 Intel® Integrated Performance Primitives for Mac OS: $199 I sure hope they have educational discounts for the numerous researchers in science and math who commented on the last post.[via MacFixIt]
