John Siracusa has produced another great review of OS X. He’s been doing that since “Developer Preview 2” back in 1999 – that is still an interesting article to peruse. The introduction of Aqua back in 2000 is although work a look.I loved his point, referring to Time Machine, that it’s harder not to backup now.
According to macnn, some people have Leopard already… but it’s still not on ADC. Today brings another Tiger 10.4.11 drop for us to test out however. Woo hoo.Breath… patience!
Turns out Daniel Jalkut agrees that “total investing” in Apple is not a bad idea at all.I blogged about AAPL investing a few days ago.I’m sure in 1996, Apple developers might have disagreed. Still, all things appear to be pointing up right now. The iPhone revolution is just getting started.
Speaking of ADC, for your $500 (at least) you get a set of monthly mailings. Does anyone actually use these DVDs? All the content appears to be online…
Couldn’t Apple save some DVDs and shipping and do ADC for $400 sans monthly DVDs? I called Apple and they offered to cancel the mailing for me; I backed down in case that was going to cover any actually useful mailings like Leopard seeds. Which are just posted online. Argh.
Aren’t these DVDs a complete waste?
So, according to a few sites, the final Leopard build is still not available to developers. How are we supposed to ensure our applications work properly by the 26th? We don’t know if bugs in the month-ago seed are fixed or not; do we need to work around them or not? Apple, let us do our jobs! I didn’t know we were the bad guys.What happens on the 26th? We paid $500 or more for the privilege of checking our applications work with Leopard, we reported bugs, we check interim builds (who is working for who here?). Now it seems we’d better get in line at a Store and pay up more money to see if our applications still work or not!Of course, due to NDA I cannot confirm or deny these rumors of Apple’s torturous passive-aggressiveness towards its developer community. However I’ve got a good idea where I can save $500 next year.
Hands up, who’s making more money from AAPL than they are from their Mac software?Is investing in AAPL a reasonable business decision for Mac-based companies? On the one hand, you don’t want too many eggs in one basket. On the other hand, it’s OK as long as you watch that basket. And most of us follow Apple as closely as possible.Given that you’re writing Mac software, you are already committed to Apple and relying on Apple being successful. And if you think Apple will do well, so will AAPL. Therefore parking any spare money in AAPL is a sound business decision.Right?
So “stuffonfire” blogged about “get” methods, here.
Chris Hanson then covered Cocoa’s convention for get.
Just thought I’d mention that the Win16/Win32 API used Get methods all over the place. When someone (I’d love to know who) modified that to come up with the OS/2 API, they made Get mean acquire, and substituted Query when the method was a simple return-a-value type.
So you’d have things like GetMemory, GetFileHandle (I forget exact examples, there weren’t many Get APIs), and QueryWindowCount, QueryThis, QueryThat, and so on. I liked Query (it was somehow easy on my eyes), but it meant everyone had two more characters to type for 99% of API calls.
So it’s great to have property style accessors, no Query or Get required!
Time to post some code. The TimeFlyer update is out, with new data model, and so far no screams of lost data.
If you need to version your Core Data model, read on…
