> My experience is that Bare Bones chooses features on priorities that include > stability, ease of implementation, how they fit with other features, and how > they accord with BB's vision of what a compact, conceptually-unified > application should look like. Volume of requests surely figures into it, > especially if they come with cogent use cases, but that's not the same as > voting.
FWIW, "ease of implementation" is almost never a consideration. The rest of what you said, particularly the use case item, is pretty accurate. Steve -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "supp...@barebones.com" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
