The Swift success stories just keep rolling in. WWDC 2020!

Labels: swift, swiftui, wwdc, wwdc 2020

This message will self-destruct in 5 seconds...

Labels: infantile

Well, we won't be putting it in the Mac App Store -- apparently Apple doesn't allow QuickTime APIs to be used in MAS submissions. Thank gawd for Developer ID.

Labels: apple, composition, mov, qtz, quartz composer

VMware: Windows 'Is Coming To An End' - Business Insider
In Q4 2013, Apple sold 2.1 million Macs, which represented nearly 14% of the PC market, Gartner reported. That was a whopping 28.5% year-over-year increase over the number of Macs Apple sold year before, compared to 2% growth of the overall PC market.

It's nice to have a morning for once when the news is good for Mac users. While iOS is a nice success, it's a weird marketplace filled with crapplications, marketers that buy users and other phenomenon not conducive to building an actual business based on things people will use.

Labels: apple, mac

Rumor: Apple working on ARM-based Mac variants with larger trackpad built into keyboard | 9to5Mac
MacBidouille is the source of an interesting new rumor [translation] that Apple is currently experimenting with new ARM-powered Mac variants that include a Magic trackpad built into the system’s keyboard. The company is also reportedly working on a new version of OS X that will be compatible with these ARM machines."

I once invested heavily in Altivec (SSE for PowerPC) and regretted it deeply during the switch to Intel. I'm happy to say that my GLSL shader experiments on OSX and iOS have us in great shape for a transition to ARM. While it may have a downside, I'm not entirely opposed to it. I think the price of Intel CPUs keeps Macs artificially expensive. There is NOTHING high end about Intel HD graphics. Give me back the Nvidia and the ATI GPUs. Intel integrated graphics is fine for low-power modes. End rant.

Labels: arm, intel

Another reason to go with the robot: Android apps are faster to build | VentureBeat | Dev | by J. O'Dell - If you’re building a new app from scratch, you might want to ditch the iOS option in favor of Android — especially if you want to get up and running quickly.

I'm not sure I agree with this, regardless as to what the survey results say. It is possible that Java developers would find Android significantly faster to develop for. Personally, I don't think that ARC (automatic reference counting) has contributed to any improvements in this regard. I'm toying with the idea of writing an anti-ARC diatribe.

Mac and iOS development is so strongly tied to CoreFoundation style programming, the new casting operators are anything but simple. ARC rules are complicated. Pre-arc memory management rules were simple and consistent.

Labels: android, cocoa