Thanks again, salesagility.
I've watched the running battle over the SugarCRM mail client for the last few years (including the recent issue of dropping POP support--huh?) but am inclined to stick it out with the SugarCRM client because SugarCRM is all about relationships with the client. Since email is the major link with clients, I expect the SugarCRM email client to eventually have some goodies that will be a pain to inject into external clients.
Or not...
I'm also inclined to stick with the SugarCRM client because I mostly use SugarCRM as a turbocharged address book that automatically relates Contacts to Accounts, and also relates Accounts to other Accounts. I'm a contract programmer, and use brokers (AKA "body shops") to market me to hiring managers; it's very important to remember who represents me where, and I'm really happy that SugarCRM lets me group hiring managers' company Accounts under broker accounts so that I can ensure that I'm not double-submitted, which usually means sudden exclusion from consideration for a programming job.
Another reason is that SugarCRM uses the PHP+MySQL combo about which I want to learn more, so problems that crop up which are merely headaches for others represent "learning experiences" for me given my inquisitive and slightly masochistic bent.Note: I unburdened myself about what this feels like to a legacy systems programmer
here.The point of the blog is that forums are the enabling technology for open source, without which large and complex projects like SugarCRM would have never been widely adopted because the self-service support enabled by forums would have been simply missing.
I do my personal email out of Thunderbird anyway, so the continuing saga of the SugarCRM email client doesn't really bother me that much.
Bookmarks