[Adium-devl] Looking at Smart Crash Reports redeux

[Jeffrey Melloy]

David Smith wrote:
> 	I don't think we can reasonably do that. We *know* how to support  
> 10.3 with no major compromises for all planned 1.0 features except  
> the crash reporter. In an ideal world the crash reporter shouldn't  
> even be a user visible feature, it's only there to help us. The  
> reason why I think we can drop 10.3 crash reports is that (for me, at  
> least) the current crash reporter is enough of a pain to use that I  
> don't look at it much. Even when I do look at it, searches take so  
> long that I've often gotten distracted by something else by the time  
> the result appears. With good reporting statistics and good  
> searchability we can make Adium's stability something we can focus on  
> in a quantitative way, rather than just having a vague idea that "oh,  
> we fixed some crashes in this build. It's probably more stable". If  
> SCR can't provide what we need (not sure if they have crash  
> statistics, they don't have our exception handling), I think we  
> should work with Unsanity to get it integrated. As boredzo says, we  
> do have BSD-licensed exception code they can use.
> 														David
>   

Keep in mind that, as the author of the current web interface, it got 
thrown together in 3 hours and hasn't been touched since.  (And I don't 
particularly care if it stops getting used.)

I can think of a few ways to improve the speed of the thing off the top 
of my head, and the reason it hasn't changed is mostly the 
squeaky/silent wheel principle.  So regardless of whether we use SCR or 
not, the current interface could certainly be changed to accommodate 
better usage.

Jeff