[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Rename `eww' to `web'
From: |
Miles Bader |
Subject: |
Re: Rename `eww' to `web' |
Date: |
Mon, 01 Jul 2013 11:03:40 +0900 |
Nic Ferrier <address@hidden> writes:
> Wait a second.
>
> I already have an HTTP client called web.
>
> So it would be a little unfair to just pinch the name?
It would be perfectly "fair." If you use a highly generic name for a
package, you shouldn't be surprised when somebody else uses the same
name, and there's little justification for feeling wronged by it.
For that reason, it's obviously a bad idea to choose highly generic
names for packages...
[See the whole stupid mess with "*Step" and their apps called
"Terminal", etc... >< Sure that made sense in a highly controlled
closed ecosystem; it makes zero sense in a shared open ecosystem.]
*However*, such names are desirable for the user when they want to just
start the app.
So the most practical thing to do seems to be use non-generic names for
packages and specific apps ("eww"), and generic names for shared thin
invocation layers [e.g. the simple (defalias 'web 'eww) dicussed
before].
-miles
--
Would you like fries with that?
- Re: Rename `eww' to `web', (continued)
- Re: Rename `eww' to `web', Richard Stallman, 2013/06/30
- Re: Rename `eww' to `web', Dmitry Gutov, 2013/06/30
- Re: Rename `eww' to `web', chad, 2013/06/30
- Re: Rename `eww' to `web', Jambunathan K, 2013/06/30
- Re: Rename `eww' to `web', Stefan Monnier, 2013/06/30
- Re: Rename `eww' to `web', Jambunathan K, 2013/06/30
- Re: Rename `eww' to `web', Xue Fuqiao, 2013/06/29
- Re: Rename `eww' to `web', Jan Djärv, 2013/06/30
- Re: Rename `eww' to `web', Xue Fuqiao, 2013/06/30
- Re: Rename `eww' to `web', Jan Djärv, 2013/06/30
- Re: Rename `eww' to `web',
Miles Bader <=
Re: Rename `eww' to `web', Richard Stallman, 2013/06/29
Re: Rename `eww' to `web', Pascal J. Bourguignon, 2013/06/29
Re: Rename `eww' to `web', Richard Stallman, 2013/06/29
Re: Rename `eww' to `web', Daimrod, 2013/06/29