My recent usage of the GNU Win32 port of Grep resulted in my discovery of a bug and in custom with my practice, I filed a report. What happened next is a lesson that Borland/CodeGear should learn from the Open Source community.
Not only did they not whinged, throwing up excuses, calling their user and bug reporter not understanding their 'feature', they digested my bug report carefully and promptly acknowledged that was a genuine bug. Even when Borland's bug has been proven beyond doubt, yet they still refused to fix it.
Within a short time, they posted me a message advising me a bug fixed version is available. Full mark for that.
Contrasting that with CodeGear's Delphi bug reports I have filed over the years, I have never received this kind of acknowledgment and quick response. More disturbingly CodeGear's Delphi product is NOT FREE and yet providing far worse support than free stuff. Hence, price does not equate to provision of support, not even meager support.
People considering CodeGear software needs to remember this before spending your money.
A site devoted to discussing techniques that promote quality and ethical practices in software development.
Saturday, June 23, 2007
- ► 2013 (13)
- ► 2012 (23)
- ► 2011 (23)
- ► 2010 (60)
- ► 2009 (60)
- ► 2008 (25)
- Changing pricing model to survive for software pro...
- Is lack of experience a good reason to discard a t...
- Excel/VBA Error with .Net COM component
- Two very poorly understood and appropriately staff...
- Outlook Clone - Evolution in Windows at last
- Bug reporting - a lesson CodeGear can learn from O...
- Different approaches in handling users' bug report...
- Class libraries not aware of LUA
- VCL Form Vs Win Form performance (old posting)
- Configuring SVN
- "Pragmatic Version Control - Using Subversion" by ...
- ▼ June (11)