I'm not sure what the problem is. Apple has created a filter to bug reporting that they're clearly comfortable with.
Fix Radar or GTFO
11–20 of 36 posts
Re: Fix Radar or GTFO
#12"Fix Radar or... Carry on making large sums of money regardless." Developers aren't their primary concern. Look at Xcode for crying out loud (and wonder at its magical ever-crashing nature).
XCode has never crashed for me in 3+ years. Your project is corrupt. You're doing something wrong. Look to a professional for assistance with your IDE.
You're not using Xcode. I mean Really Using Xcode. Like making a serious attempt at exercising its features. Hell, you really don't even have to do that. Create a project, edit some code, compile and run your app. That's usually fine. Now, try repeatedly, several times a minute for eight hours straight to use the debugger on your app (intentionally overrelease something or create some other reason for Xcode to launch lldb when your app crashes.)
Xcode will crash.
Re: Fix Radar or GTFO
#13"Fix Radar or... Carry on making large sums of money regardless." Developers aren't their primary concern. Look at Xcode for crying out loud (and wonder at its magical ever-crashing nature).
Seriously the crashing is what amazes you about XCode ?
How about the lack of ANY refactoring support emphasis on ANY, the joke that is autocomplete, the atrocious file management, the complete lack of preferences, the way SCM destroys project, the inane approach to compiler flags. And don't even start on the index.
Honest to god. I swear the XCode team must be stuck in the 80s still listening to walkmans.
Re: Fix Radar or GTFO
#14Why would Apple want to "fix" Radar? It seems to meet _their_ requirements quite well: - Developers have a place that they can report things which is industry best practice - They don't need to put in as much money to staffing it If it's a big enough issue then they'll hear about it through other channels. (EDIT: formatting)
I used to develop at Apple. Radar is a piece of junk.
Re: Fix Radar or GTFO
#15I don't this is specifically an Apple issue either, I've filled bug reports on quite a few different projects (mostly open source) including at least one that's a full application framework and rarely do they ever move into 'confirmed' or 'accepted' status. The entire reason of letting people add bugs is that they can be tracked, if the submitter can't track it then why would they want to add it? If you can't see a p…
I believe that at a certain size of the project you will get more incoming bugs than you can handle. Doesn't matter if it's closed/open source, who the users are or anything else. It's just a matter of the number of users / size of QA. Basically over some threshold you'll get conflicting behaviour expectations, duplicates formulated differently so they cannot be linked, QA finding more tiny issues in every release th…
True, it's definitely a case where eventually the number of bugs becomes incredibly difficult to manage but it's still essentially training people to not report bugs if they can't see even the smallest amount of traction on it.
Re: Fix Radar or GTFO
#16This has been solved already: http://openradar.appspot.com If you file a new bug with Apple, publish it here as well. No more black hole, you can see what others have already posted. You can even see what duplicates are about (if the original bug was also at open radar).
So a parallel bug tracking system that the developers (Apple) don't update... that's not a solution, that's a kludgy workaround for a problem.
Re: Fix Radar or GTFO
#17If you file a bug report on Radar, unless you know someone at Apple who you can give the Report ID to, it is unlikely to be dealt with quickly. Seems like they don't have a dedicated team overlooking it.
Actually from what I saw on the OSX project the bugs were triaged pretty quickly by the Engineering Team. The problem is that you don't really get any feedback when it happens. And often the triage reason is technical so they can't really share it.
I think some people aren't paying much attention to Apple's products. They tend to add new features pretty quickly so doesn't leave much time for non showstopper bugs.
Re: Fix Radar or GTFO
#18"Fix Radar or... Carry on making large sums of money regardless." Developers aren't their primary concern. Look at Xcode for crying out loud (and wonder at its magical ever-crashing nature).
XCode has never crashed for me in 3+ years. Your project is corrupt. You're doing something wrong. Look to a professional for assistance with your IDE.
LOL. For the same reason, Microsoft Powerpoint has never crashed for me in 3+ years. (Because I haven't used it in 3+ years.)
I guarantee you that there is no professional programmer anywhere in the world that has used Xcode to write and compile their applications for 3 years and not had it crash. So your experience would suggest that you aren't one.
Re: Fix Radar or GTFO
#19I'm not sure what the problem is. Apple has created a filter to bug reporting that they're clearly comfortable with.
The problem is that you can't get real tracking on your business critical bugs because Apple just marks them as duplicates. And once it's a duplicate, you can't see the status, so you never know if it's actually fixed. So why even bother reporting bugs?
Here are my stats from Radar:
4 Open - All over two years old.
7 Duplicate
1 Closed - The only one I got a response back on, and that Apple said was fixed.
Re: Fix Radar or GTFO
#20Why would Apple want to "fix" Radar? It seems to meet _their_ requirements quite well: - Developers have a place that they can report things which is industry best practice - They don't need to put in as much money to staffing it If it's a big enough issue then they'll hear about it through other channels. (EDIT: formatting)
This is exactly why action on the part of developers is a good idea. Obviously Apple doesn't need to fix it, the current system is serving them well enough. Apple's target market are its users not its developers, and that's fine.
However, as a developer, I'm going to be trying my hardest to pressure Apple into making my life easier, and the more people doing the same the better. Just because they can get away with this sort of thing, and it makes logical sense for them to do so doesn't mean that's the way things have to stay. A better ecosystem for Apple developers is a better ecosystem for their end-users, down the line, anyway.