1 |
On Sat, 2005-06-11 at 14:46 -0400, Aron Griffis wrote: |
2 |
> foser wrote: [Sat Jun 11 2005, 04:15:22AM EDT] |
3 |
> > Arch keywords are concepts and as such may not primarily be dealt as |
4 |
> > a an alphabetical list but as words in a sentence, there is no abc |
5 |
> > order in sentences. |
6 |
> |
7 |
> Foser, no offense intended, but you started out in this thread making |
8 |
> a couple good points. However this is completely off the wall. The |
9 |
> KEYWORDS list isn't a sentence. |
10 |
|
11 |
The post I replied to was full of far-fetched reasoning, I just made a |
12 |
similar post. |
13 |
|
14 |
> > If you have to search, you'll have |
15 |
> > to scan anyway, exact position is not a guarantee for certainty because |
16 |
> > not every pack is available on every arch, it's not like you can go |
17 |
> > without scanning. |
18 |
> |
19 |
> Doesn't change the point that scanning in alpha order is easier than |
20 |
> scanning append order. |
21 |
> |
22 |
> > Last, this only holds to some extent true for people |
23 |
> > in countries with alphabetic scripts, outside that limited part of the |
24 |
> > globe people are not as proficient in ordering alphabetically. |
25 |
> |
26 |
> AFAIK, all Gentoo developers are fluent English speakers, even if for |
27 |
> some it isn't their first language. |
28 |
|
29 |
Fluent, right. Try some of the cjk people. Not really. Anyway, it |
30 |
doesn't matter, if you didn't grown up with the alphabet, you really |
31 |
don't know the ordering by heart like western people do. In spoken |
32 |
language it doesn't matter what the order is, it is totally arbitrary. |
33 |
Also, realistically it's probably only 1st language for maybe half of |
34 |
the devs these days. |
35 |
|
36 |
> > A certain amount of uncertainty in order actually might prove to be |
37 |
> > effective in having everyone who deals with keywords actually really |
38 |
> > check all keywords and not depend on assumptions, which both 'error' |
39 |
> > cases you mention seem to be caused by. |
40 |
> |
41 |
> Maintaining a behavior that encourages mistakes, in hopes that the |
42 |
> extra effort required will prevent those mistakes? This cannot |
43 |
> possibly be a good approach... |
44 |
|
45 |
You assume here suddenly that it encourages mistakes, there is no such |
46 |
evidence presented here or ever was, there is however evidence to the |
47 |
contrary where the continues shifting of orders (within packages) caused |
48 |
problems (the thing I disliked about this whole situation to begin |
49 |
with). I actually suggest that the opposite might be true, a certain |
50 |
degree of uncertainty (between packages) prompts caution and might prove |
51 |
to be more error-free. Sure it's all a bit far fetched, but so was the |
52 |
post that suggested that there was some grand ergonomic idea behind this |
53 |
arbitrary change. |
54 |
|
55 |
I did not in this thread challenge the ordering (who made that up?), I |
56 |
challenged the way it got 'introduced'. I just got ticked off by the |
57 |
'scientific basis' that suddenly was presented as the big reason behind |
58 |
it. |
59 |
|
60 |
To recap, it was the arbitrary /ordering change/ of a select group of |
61 |
individuals that created problems within packages, not the one or the |
62 |
other /order/. |
63 |
|
64 |
- foser |