3 ms·
How about we open a radar? Is there one yet? The engineers who read those are not entirely unreasonable... just really busy.
by andymoe 13y ago
How about we open a radar? Is there one yet? The engineers who read those are not entirely unreasonable... just really busy.
- comex 13y agoOr have the build system check if the SDK name ends in ".internal" and change the name and/or complain if so. Seriously, adding licensing requirements is silly when most likely the engineers responsible just need to know what's going on.
- mwfunk 13y agocomex's second comment pretty much sums up the whole situation. It's bizarre that anyone even has other ideas at this point.
- Alphasite_ 13y agoIt feels like the only unreasonable party is the author.
- Gigablah 13y agoIt feels like shoddy work by Apple engineers, actually. Seriously, making use of an open source library and breaking it (indirectly) for everyone else in the process?
- bigiain 13y ago"Shoddy work" is maybe a little over-the-top, but I certainly agree that they've screwed up here by not thinking through the implications of the system within which they've made all their design/coding choices (or considering the impenetrability of the system to outside developers, who's work they're happy to use, but who then have very few other workable option except "public shaming" when this sort of unintended consequence occurs).
- gress 13y agoThe other options include: 1. Filing a Radar. 2. Using a DTS incident. 3. Emailing a platform evangelist. Seems like quite a lot can be tried before "public shaming" becomes the only option.