On Tue, May 26, 2015 at 1:27 PM Esteban Lorenzano <[email protected]> wrote:
> or we can rename it as "System Browser (Nautilus)” in the title, or > something like that > > I think this is ideal. I remember back when I used to use Perl, and it had CPAN, which was great. The only problem was that someone would say "use the XML library!" and you'd look in CPAN and there'd be xml and xmllib and libxml and fastxml or whatever, and you'd be like "uh... which one would that be?" Ruby went the other way entirely, with idiosyncratic names like "Nokogiri". The obvious down side is that if you see that in an app's dependencies and you're a newbie, you have no fricking clue what it is. The upside, though, is that if someone tells you "use Nokogiri!" there is zero ambiguity about what you're supposed to use. It gives the project a distinct, memorable personality. If you can keep distinctive project names, but also name menus and title bars such that they link the distinct project to the *role* that project plays, you've got the best of both worlds.
