News for hackers. Stuff that matters.
Re:Dear Apple by eddieroger on Sunday February 19, 2017 @12:59PM (#13680912)
Yup, that. Vote with your keyboards. Apple writes software with the same tools and languages - if they considered this stuff a problem, they'd have fixed it by now. Besides, Apple has mechanisms for feedback, and it's not open letters on GitHub.
Re:Dear Apple by orbitur on Sunday February 19, 2017 @01:24PM (#13681066)
> if they considered this stuff a problem, they'd have fixed it by now

It's not good but it's workable. Which Apple accepts as a reason to focus very few resources on dev tools.

Re:Dear Apple by eddieroger on Sunday February 19, 2017 @02:09PM (#13681312)
Sure. My point is more if it's good enough for Apple at their scale - I mean, Xcode itself is written in Objective-C with Xcode - and they're willing to work around it, then 25 developers (at time of viewing) in a GDocs sheet and a readme file will probably not be the straw that breaks this camel's back.
Re:Dear Apple by EdHominem on Sunday February 19, 2017 @03:58PM (#13681930)
They don't really, not ones that they won't delete when they want the problem to go away. Using corporate forums for problems is a losing game.

Yes, this letter should probably reference a bug#, but it should not be in the bug itself. And, because it's an open letter, you can go add a bug and make a PR to add it to the letter.