In message <
slrnk4hcdi...@um5000.mystora.com>
[Enchicken post A, then abandon it and post non-enchickened post B. Then
wonder why your gem of wisdom does not appear. Doh.]
I'm kind of inclined to take the idea of a suckage index semi-seriously. If
this bugs anyone, moan pre-emptively and I'll take it to email. Email
address is valid with or without the _news.
I was thinking that something like the Purity Test might be a suitable model
to follow, but with a perfect score of zero for the Mythical Non-Sucking
<foo>, and with real-world <foo>s losing points for doing things that suck,
with particular implementations that suck mightily losing more points than
things that suck by the least possible amount.
For example: The Purity-1 version has a single question - Are you pure? with
a Yes/No answer. The Suckiness Test equivalent would be Do this <foo> suck?,
again with a Yes/No answer. A perfect score in the test would be zero, and a
response of 'yes' would score -1 while 'no' would score -2. Thus anyone dumb
enough to claim their particular <foo> doesn't suck is hit for an extra
penalty, and a <foo> that got lots of 'nos' would correctly be flagged as
sucking harder than a <foo> that scored a greater proportion of 'yeses'. I
think this is the scoring philosophy we'd need to follow.
I also think we would need separate Suckiness tests for hardware, operating
systems, and so on, so unfortunately this is likely to be rather more work
than the original purity tests.
The original purity tests grew by accretion - purity-1000 with 1000
questions was significantly later than purity-400 (although purity-1 was
quite a late addition to the oeuvre). But by following that model we can
start with a manageable number of questions - OS-Suckiness-50 or so to begin
with, and then add more with time.
For questions like the directory separator issue, it's clear some choices
are better than others. By being plain about the principles we're trying to
identify, we might be in with a slight chance of articulating /why/ some
choices are bad, and, you know, there might even be a slim chance of
avoiding them in the future. Heh.
For that particular issue I'd suggest scoring of -1 for . (unless someone
can come up with a very good reason for why it deserves to score 0), -2 for
/ and -3 for \
If someone finds some way to implement directory separators that's even
stupider, we can add a new entry to the list. Possibly the scoring per
question will need to be weighted and/or normalised, so it already seems
likely that Suckiness tests are also going to suck.
I am going to keep mulling the issue for a OS-Suckiness test. Things like
scriptability, the directory separator, filename length, case sensitivity of
filenames, ability to do stuff (or not) from the command line, and so forth
is barely the start.
But it does seem strangely fitting to me that my proposed Suckiness test is
itself, quite clearly, going to suck.
--
Simon Smith
When emailing me, please use my preferred email address, which is on my web
site at
http://www.simon-smith.org