Existing users, 
don't believe the Bare Bones hype - barberfloyd
If the Bare Bones people are correct then why is it that I have never had a problem with an Unsanity product? I have used TextWrangler and I have had problems with that. I also used to have problems with BBEdit Light. Maybe Bare Bones just needs something to explain away the troubles with the performance of their software.Thursday, June 01 2006 @ 06:51 AM PDT
don't believe the hype - domo
Yup. I'm aware of this particular set of blinkers. I've never had a crash in Apple, third-party or my own software that, on examining the logs, I can attribute to Ape. But if I want to raise a bug report for a crash, I'll always reproduce the problem with Ape disabled and attach the new log to the crash report, so that the developer can't just say "It was Ape! It's not my problem." It's a bit more trouble for me, but, given the usefulness of Ape, I think it's worth it.Thursday, June 01 2006 @ 10:45 AM PDT
don't believe the hype - wgscott
I have 8 or 10 macs (yeah, I lose count) for scientific research purposes, including heavy-duty computations. If Unsanity's stuff slowed anything down significantly, or caused instability, I would ditch it in a second. The fact is I have used some of this stuff (fruitmenu, cleardock) for over 4 years without a single problem.Tuesday, June 27 2006 @ 10:19 AM PDT
don't believe the hype - wgscott
I have 8 or 10 macs (yeah, I lose count) for scientific research purposes, including heavy-duty computations. If Unsanity's stuff slowed anything down significantly, or caused instability, I would ditch it in a second. The fact is I have used some of this stuff (fruitmenu, cleardock) for over 4 years without a single problem.Tuesday, June 27 2006 @ 10:24 AM PDT
Fed up with jelous developers - Ilgaz
I am a paid user of many application enhancers now using them on my Quad Mac. I have seen ONCE, JUST ONCE APE causes crash. It went to unsanity thanks to their smart crash reports and they spared their time to investigate it. False alert. The programs copy protection ASM routines were causing the crash, not APE. I am telling this as a guy who paid $140 to every OS X released and get ZERO RESPONSE and IRC BAN from Apple when my modem which THEY SHIPPED stopped working until 10.4.3From what I have seen, some developers have kind of "social" problems like jealous , personal hate and personal "show off" problems tricking ordinary end users.
Every Unsanity tool has "money back guarantee" which is rare in OS X World, they give priceless (in fact pricey, $3000 similar functionality) utilities as "Smart crash reports" for free, give the functionality which Apple Inc. can't and WON'T deliver to OS X and get these misinformed, trollish "BLOG" entries as return.
They coded APE in 1 or 2 months, moved from PPC only to x86/PPC ASM. Live with it, shut up.
We speak with Bare Bones guys when they offer a SINGLE TOOL that is SUCCESSFUL for free. TextWrangler is free because they couldn't sell such a pathetic thing. So, as Unsanity "fanboy" should I take my time to go to that programs page and tell these facts? I am not that low.
I am sometimes really glad that I am just an advanced user, not developer since I wouldn't just sit there , I would sue whoever spreads misinformation about my commercial products.
As a paying $25 Versiontracker user which I suspect your types actually think as "stupid", I announce that I will use my legal and international rights and paying vt members rights if you call me a guy who got paid by Unsanity to write this message.
As your types does many times... Jealous misinformers.
Reply to This
Thursday, June 01 2006 @ 05:17 AM PDT