Recently, I wrote a series of Swift tips over at my company’s blog. This started out as a simple CocoaHeads talk where I was sharing my own personal best practices with the group.
I’ve lamented about my love/hate relationship with Evernote but I never followed up about my solution to this problem. For now, I’ve given up on my dream of a custom built solution in favor of Bear, a simple yet beautiful note taking solution. It even checks off many of the boxes from my wish list:
I’ve been a long time Evernote user. With few exceptions, I dump everything that I think or discover into my Evernote database. I’ve even been a premium member until recently.
We all knew what was coming and it was still a doozy. The rumor mill basically got everything correct and this was still one of the best keynotes in a long time. I plan on writing more in depth about each major topic but for now, here are my first impressions.
Speaking of Swift, I delivered a presentation on scripting with Swift at Nashville CocoaHeads at the end of January, earlier this year. Check out the video and head over to the Github repository for the source code and more information.
I’m really excited about the changes to Swift in the current Xcode 6.3 beta. Apple has answered several of my biggest gripes with Swift. Here are some of the highlights:
Youtube recently ran into issues with it’s view counter for the Gangnum Style video. Basically, Google was using 32-bit integers to store the view counter value for its videos. This means that it had a maximum possible value of 2,147,483,647. This essentially “broke the internet” (at least for this one video) when the number of views passed that limit. My friend Allen asked me why Google didn’t already use the 64-bit version (which has a maximum value of 9,223,372,036,854,775,807… that’s nine quintillion with a Q) rather than 32-bit version. The answer: bandwidth.