Nacho Soto@NachoSoto·Sep 9, 2015This is freaking embarrassing, Apple. I'm so madQuote TweetJoar Wingfors@joar_at_work · Sep 9, 2015Replying to @NachoSoto@NachoSoto It won’t. But it is a known issue, that will be addressed in a later release of Xcode.222
Andy Matuschak@andy_matuschak·Sep 9, 2015@NachoSoto the situation with Apple's swe org design practices has gotten to the point where I just find it an interesting case study? :/115
Nacho Soto@NachoSoto·Sep 9, 2015@andy_matuschak yeah it’s fascinating. I wonder if Hollywood will turn it into a movie.1
Andy Matuschak@andy_matuschak·Sep 9, 2015@NachoSoto nope too boring. we already know we must not rely on Apple to steward the dev platform. further evidence should not surprise? :/111
Andy Matuschak@andy_matuschak·Sep 9, 2015@NachoSoto nah just rely way less on their abstractions and tools31
Andy Matuschak@andy_matuschakReplying to @MarkVillacampa@MarkVillacampa @NachoSoto I mean I did for a long time. It got better, started using it. I stop when it misbehaves. Do what makes sense.4:58 PM · Sep 9, 2015·Twitter for iPhone
Daniel Galasko@danielgalasko·Sep 10, 2015Replying to @andy_matuschak@andy_matuschak @MarkVillacampa @NachoSoto issue seems resolved in 7.1 see release notes1