I've had some feedback that I've made a bit of a mess with casting when trying to calculate a random number - would appreciate any best practices or thoughts on that...
The main goal was try and introduce these APIs to designers, since there seems to be a current of interest around designers getting excited about learning Swift.
This just feels like more proof that Swift will be nominally better than ObjC for the next 5 years, until Apple's APIs are (re?)written to make use of reasonable Swift idioms.
Also, this is the community's periodic reminder that not all ObjC (and soon Swift) is iOS; people still write (and use! imagine that!) OS X apps.
6 comments
[ 3.1 ms ] story [ 20.6 ms ] threadI've had some feedback that I've made a bit of a mess with casting when trying to calculate a random number - would appreciate any best practices or thoughts on that...
https://gist.github.com/mathewsanders/82311409978066b02932
delay = NSTimeInterval(arc4random_uniform(900)+100) / 1000
Not sure why I didn't do that in the first place...
You brought up a couple of neat concepts that I wasn't aware of, especially "UISystemAnimation.Delete".
The main goal was try and introduce these APIs to designers, since there seems to be a current of interest around designers getting excited about learning Swift.
Also, this is the community's periodic reminder that not all ObjC (and soon Swift) is iOS; people still write (and use! imagine that!) OS X apps.