Sometime more specialized/specific is better. For instance, Gmail does support IMAP but also has non-IMAP features. Being too abstract would mean avoiding prov

Sometime more specialized/specific is better. For instance, Gmail does support IMAP but also has non-IMAP features. Being too abstract would mean avoiding providing these features. Another point is the easiness of installation/configuration/usability. For instance, with Emacs, you can use GNUs to read gmail. However, it is so generic (you can read usenet news and any kind of e-mail), that it's really a pain to get started. There are terminology confusions (i.e. you need several hacks to have a gmail-like inbox) and overall, it just doesn't feel like g-mail.. Also, by starting very specific for our own problem, it's easier to create a meaningful product that solves a real need. (Like startup!) I think it's easier to start specialized and then grow larger, than start too brood.