Why Pro Matters

Sebastiaan de With pens what I consider to be the best argument for why Apple should care about a niche market of Pro Mac users:

Macs became the tool of choice of this new wave of designers, and as the web evolved Apple kept its OS and app ecosystem in sync with its trends; as online video became popular, Apple offered the easiest editing software in iMovie. Blogs and RSS had a peak; Macs came with iWeb that let you author blogs literally out of the box. These designers started to code, or came in contact with developers.

I was there for this, with both G5 and Intel variations of the cheese grater Mac Pro. Before Apple was the largest company in the world, they built the best computers and operating systems for the tastemakers of technology. I never worked with Seb on a project1, but I worked with some of the best designers that have gone on to build the biggest products of the mobile era. We'll ignore that I continue to toil in obscurity, dear reader.

I haven't said much about the Mac Pro's demise because there's plenty of other people with opinions on the hardware. That said, I am glad to see it's no longer on its deathbed. It may not be Apple's most profitable product, but it doesn't need to be. When you have the ability to positively effect the real influencers of the industry2, it's hard to see the downside. I am not sure if the Mac Pro is for me anymore, but I much prefer an Apple that invests at least some of its billions in flexing its computing muscle from time-to-time. Not because it needs to, but because it wants to and can.

(via Pixel Envy)

  1. Someday!

  2. The people that do the work, not just talk about it at tech conferences.

Read more about. . .

My Ultimate Developer and Power Users Tool List for macOS Sierra (2017 Edition)

This is the latest installment of my must have must have list of tools and utilities as a macOS and iOS developer. The idea for this list was shamelessly ripped off from Windows developer Scott Hanselman whose list has long been an enjoyable read when he updates it.

There have been significant changes since I last did one of these. I’ve tried to mark anything new in bold.

Hardware

Since I last updated this in 2013, my hardware has changed significantly.

I am still maintaining a dual Mac setup. My daily driver is a Late 2015 27" Retina 5K iMac with a 1TB SSD and 32GB of RAM. After nearly five years, I replaced my old 2010 iMac that was starting to show its age when compiling Swift. Swift eats hardware for breakfast, lunch, dinner, and fourth meal. I’d say this was Apple’s genius plan to sell more Mac hardware, but they can’t be bothered to update their hardware lineup regularly so there went that theory.

At home I am using my 15" Retina MacBook Pro with a 1TB SSD and 16GB of RAM. This is one of the new Touch Bar models and it’s fine. I somehow have been able to survive without a physical escape key or a row of function keys. I assume this makes me lose some sort of geek cred. Sorry, nerds.

I used to be a big Dropbox user, but I’ve moved all of my files over to iCloud Drive because it’s good enough. I take advantage of the Shared Desktop and Shared Documents functionality of macOS Sierra. Photos are stored in iCloud. Calendar and Contacts too. It works, usually. There wasn’t anything wrong with Dropbox, but it was just another thing I was paying money for that wasn’t super necessary when there’s a good enough alternative baked into the OS now.

In terms of accessories and upgrades:

Software

I am really hard on software. This is for a variety of reasons, but I think it is because I build it myself. I have always envisioned that directors and actors can sometimes lose focus during a movie as they judge the decisions others made in their productions. I feel like I do the same thing with software. I loathe poor and/or non-native user interfaces and cherish simple tools. These are applications I constantly rely on.

The Essential Five

Developer Tools

User Tools

Read more about. . .

Showing Debug and Info Logs in the macOS Sierra Console

This is one of those "it's obvious in hindsight" problems I ran into recently.

At the day job, we have been migrating all of our logging code from Aspen to Apple's new Unified Logging System. This has been a win for the most part: we got to terminate a third-party dependency, while also getting some advanced features such as log filtering based on a category or subsystem.

The problem I ran into last week was trying to debug a background session issue on my iOS device. We use the different logging levels provided by os_log to help keep users logs a bit less chatty than just spitting out print or NSLog statements everywhere. By default, the new Console app in macOS Sierra only shows logs that match the error level (or have no level at all). I needed to see our debug and info log information.

If you watch the WWDC video on the new logging system they show you a few Terminal commands you can run to adjust your logging level on the Mac. It doesn't really show you how to adjust that for an iOS device plugged into your Mac, however.

Long story short, there's no Terminal command. There's two options in the "Action" menu on the Console. Just select "Include Debug Messages" or "Include Info Messages" and you are good to go.

Turn on info and debug messaging in the Sierra Console

I sure felt dumb once I figured that out. You win this round, Apple.

Read more about. . .