WWDC 2017 runs 5-9 June 2017, at which (among many other things) the next versions of iOS and macOS are expected to be announced with the end-user releases coming 3 months later in September. What this also means is the MacBook I’m writing this on – one of the oldest machines which can run macOS Sierra – will likely *not* be able to run the next versions of macOS and Xcode. <sigh> I might also want to reconsider getting an iPhone SE, although the fact Michael Tsai uses one is a compelling factor. However, I probably have to bite the bullet and either get an iMac or a MacBook Pro in October or so… and a reasonably modern iPad. Ugh.
Actually, I should be able to run Xcode 9, so maybe I can push off a new Mac purchase to 2018.
UPDATE: well, it looks like macOS High Sierra will run on the MacBook just fine. <phew> Of course, I’m really lusting after an iMac Pro now…
After attending the Orlando iOS Developer Group’s Meetup last week, I’m considering starting something similar for the Space Coast. I have no idea how many other Apple developers there are in this area, but I’d like to find out and see if we can get a community going.
I’m thinking of naming the group Space Coast iDevelopers
For interests (limit 15), I have
- Swift Language
- Server Side Swift
For a description, I was going to use:
Interested in building apps for the iPhone, iPad, Mac, Apple TV, or Apple Watch? Interested in Swift, Objective-C, and Xcode? From newbies to experts, all skill levels are welcome.
The one thing I need to figure out to really take a crack at this is where to hold the meetings. I also need to line up sponsorships, but I’m fine buying pizza and soda for the first few meetings until it takes off.
The Suntree-Viera Public Library has a 10-15 person conference room I could probably use to get the group started, but I just realized I should also have a 1080p projector. That’ll run about $50-100, but I can list it as a business expense, so it might be worth it. I could get a 32″ HD TV instead for a little more and schlep that around instead: might actually be a better option.
Good tip in this article about build times on 12-core Mac Pros for Swift projects:
Disable Spotlight indexing for build cache folders. I saw 10% improvement after blacklisting derived data, cache and related folders (“~/Library/Developer” and “~/Library/Caches”) from Spotlight indexing.
Update: actually, from recent comments on the article, it looks like ~/Library/Developer/Xcode/DerivedData is a better candidate than ~/Library/Developer
It isn’t possible at present:
Yes, there are tools like Refactorator I can add to Xcode to provide this, but this goes against my minimalist/cheap approach, and frankly, unless it’s something on the order of JetBrains’ ReSharper, why bother? Well, there *is* JetBrains’ AppCode, and maybe I’ll check it out when I’m past the inflection point on the Swift learning curve, but $200 more into what is at present a hobby is hard to justify.
Ugh, just ran into an ugly bug in my code, and I can’t find a way to have the Swift compiler warn me about it. My class has a property named progressView –
var progressView: UIProgressView!
– and I inadvertently aliased it with a local constant in a function –
let progressView = UIProgressView(progressViewStyle: .default)
– with the net result that I crashed in KVO code because the progressView property was nil.