1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <etotheipi@gmail.com>) id 1SoQQp-0001yp-3P
for bitcoin-development@lists.sourceforge.net;
Tue, 10 Jul 2012 02:44:07 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.175 as permitted sender)
client-ip=209.85.216.175; envelope-from=etotheipi@gmail.com;
helo=mail-qc0-f175.google.com;
Received: from mail-qc0-f175.google.com ([209.85.216.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SoQQo-0004OG-BF
for bitcoin-development@lists.sourceforge.net;
Tue, 10 Jul 2012 02:44:07 +0000
Received: by qcad10 with SMTP id d10so6005209qca.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 09 Jul 2012 19:44:01 -0700 (PDT)
Received: by 10.224.199.201 with SMTP id et9mr47458926qab.59.1341888240845;
Mon, 09 Jul 2012 19:44:00 -0700 (PDT)
Received: from [192.168.1.85] (c-76-111-96-126.hsd1.md.comcast.net.
[76.111.96.126]) by mx.google.com with ESMTPS id
bh13sm64001665qab.21.2012.07.09.19.43.59
(version=SSLv3 cipher=OTHER); Mon, 09 Jul 2012 19:44:00 -0700 (PDT)
Message-ID: <4FFB9707.9020307@gmail.com>
Date: Mon, 09 Jul 2012 22:44:23 -0400
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64;
rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <1341849295.94710.YahooMailNeo@web121003.mail.ne1.yahoo.com>
<CAAS2fgRd0gqrxXs4Le6nydYBaG7EO=T7FrtX6QZpg3aJtAxSvg@mail.gmail.com>
<1341850157.18601.YahooMailNeo@web121006.mail.ne1.yahoo.com>
<CAAS2fgQRo4swDTQjPE0PmnpZ9uS+TDNQdOR6q4K70xsNJY9RfQ@mail.gmail.com>
<1341857882.56956.YahooMailNeo@web121006.mail.ne1.yahoo.com>
<CANEZrP1vwDubXrY3eoq4P4SAN=GK06iVaVx4pMWZKmBwQc9awg@mail.gmail.com>
<4FFB5A7E.7020604@justmoon.de>
<CANEZrP3Y3nvRwiPw66bDhp01JnE-zVurw5MnxPzR-bi5H8h4Aw@mail.gmail.com>
<4FFB9537.8040909@justmoon.de>
In-Reply-To: <4FFB9537.8040909@justmoon.de>
Content-Type: multipart/alternative;
boundary="------------080506040401070200000204"
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(etotheipi[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1SoQQo-0004OG-BF
Subject: Re: [Bitcoin-development] Random order for clients page
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 02:44:07 -0000
This is a multi-part message in MIME format.
--------------080506040401070200000204
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 07/09/2012 10:36 PM, Stefan Thomas wrote:
>> It looks like that because feature matrices aren't especially helpful
>> for newbies to make a decision, especially when the "features" in
>> question were often things like how they handled the block chain or
>> which protocol standards they support, ie, things only of interest to
>> developers.
> A well-designed feature matrix can quite useful and user-friendly.
>
> http://www.apple.com/ipod/compare-ipod-models/
>
> Prose is better to get a sense of the philosophy and basic idea of a
> client. If it was between having only a feature matrix or only prose,
> I'd probably go for the prose as well.
>
> What a feature matrix is good at though is it allows you to very quickly
> find the specific feature or general criteria you're looking for without
> reading through all of the text. So it might be a useful addition maybe
> not on Bitcoin.org, but certainly on the wiki.
>
If we're keeping the clients page, I would really like to see the
feature matrix linked from that page. It shouldn't be on that main
clients page (for the reasons already stated), but Stefan makes a point
that /it is really useful for many users./ Add "Compare features of the
various different clients here: <link>" and users who will benefit will
most definitely click on it. I think that's win-win.
--------------080506040401070200000204
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 07/09/2012 10:36 PM, Stefan Thomas
wrote:<br>
</div>
<blockquote cite="mid:4FFB9537.8040909@justmoon.de" type="cite">
<blockquote type="cite">
<pre wrap="">It looks like that because feature matrices aren't especially helpful
for newbies to make a decision, especially when the "features" in
question were often things like how they handled the block chain or
which protocol standards they support, ie, things only of interest to
developers.
</pre>
</blockquote>
<pre wrap="">
A well-designed feature matrix can quite useful and user-friendly.
<a class="moz-txt-link-freetext" href="http://www.apple.com/ipod/compare-ipod-models/">http://www.apple.com/ipod/compare-ipod-models/</a>
Prose is better to get a sense of the philosophy and basic idea of a
client. If it was between having only a feature matrix or only prose,
I'd probably go for the prose as well.
What a feature matrix is good at though is it allows you to very quickly
find the specific feature or general criteria you're looking for without
reading through all of the text. So it might be a useful addition maybe
not on Bitcoin.org, but certainly on the wiki.
</pre>
</blockquote>
If we're keeping the clients page, I would really like to see the
feature matrix linked from that page. It shouldn't be on that main
clients page (for the reasons already stated), but Stefan makes a
point that <i>it is really useful for many users.</i> Add "Compare
features of the various different clients here: <link>" and
users who will benefit will most definitely click on it. I think
that's win-win. <br>
</body>
</html>
--------------080506040401070200000204--
|
