> I think it's a bit of all three, but also a lot because this current unhappiness is driven by developers, who had expected Apple to treat the MBP- much less t

> I think it's a bit of all three, but also a lot because this current unhappiness is driven by developers, who had expected Apple to treat the MBP- much less the Mac Pro- with greater care and respect. 2014 saw the introduction of Swift, and developers were happy. Developer happiness relative to these parts is probably the most right. There was a lot going on for Apple the last few years for developers, and they were happy. The Mac Pro refresh cycle is something that always confuses me, like why would we expect faster refreshes with the new trash can Pro than the cheese grater? The point of that machine is that it's expensive and needs to last a long time. Annual cycles don't support that model. Yes, that means it gets outdated faster, but it's not like Xcode or Final Cut or ProTools or Adobe anything stop supporting the Pro a year after it's released. I have a MacBook Pro for work that has a four year refresh cycle. It sucks to see new, shiny ones coming out that I won't be eligible to get for a few more years (excuse me - next year, it's 2017 now), but that's corporate life.