crashing and Unsanity

Patrick Armbruster patrick at elixir.ch
Thu Sep 23 15:54:54 PDT 2004


I'd urge OmniGroup to take notice of those crashers and simply inform 
unsanity of the problem. They can then decide whether it's the haxie at 
the root of the problem or OmniWeb... Simple, 'snt it? Well no, of 
course not.
But maybe we should urge unsanity to inform _their_ customers about 
what exactly those haxies are and do - and how they _can_ affect system 
stability... But that of course would be asked a bit much for them to 
do...

Am 24.09.2004 um 00:39 schrieb Christopher Bort:

> Well said. Far more concise than my mumblings. The common factor 
> between
> everything is the OS. All other software -- apps, hacks or other -- 
> must
> play by the OS's rules. If a well-written application that conforms to
> those rules is broken by a 'hack' that does not, it is not the
> responsibility of the application's developer to 'fix' their code 
> (which is
> not broken and does not need fixing). Chasing down such hoodoos is
> ultimately a losing proposition. The proper solution is for the 'hack' 
> to
> be fixed so that it does not alter expected system behavior from the 
> pov of
> other applications.
>
> Just to keep this marginally on-topic, I'll add my vote for OmniGroup 
> to
> refrain from spending unnecessary resources chasing down compatibility 
> with
> third-party 'system enhancers' if doing so would come at the cost of 
> not
> being able to use those resources on delivering new features and/or
> squashing legitimate bugs.

Gruss
=================================================================
Patrick Armbruster
story.ch
http://story.ch - Die grösste Schweizer Online-Literaturplattform
patrick at story.ch
-----------------------------------------------------------------
AIM: fryke
=================================================================




More information about the OmniWeb-l mailing list