7 Nov
2015
7 Nov
'15
11:49 a.m.
On Thu, Nov 05, 2015 at 04:09:43PM -0500, Paul Davis wrote:
How would anyone start the server with a non-default name and
not know what he/she is doing ? Looks like a documentation
problem in that case.
Supporting your software doesn't mean you have to be available
for any noob 24/7. You're to linux audio what Linus is for
the kernel, but I don't think Linus hangs out in IRC all day
to answer questions about kernel parameters to people who are
too lazy to read the docs.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
The clean
solution to that would be to remove testing that
env variable. In other words, *if* you want a non-default
server, you (the app) has to specify it. Much less confusing.
this doesn't address what happens when someone has started the *server*
with a name (because they didn't understand the significance of doing so). i want to support corner case use cases only to the
extent that they do not
pollute/confuse the workflow for the common case.
It's easy enough to do that without making things impossible.
If that is
your problem then *just stop hanging out on IRC all day*.
Honestly, I can't imagine how anyone can do any sort of serious work
requiring a minimum of concentration, or enjoy any entertainment, or
whatever, if he/she his hanging out on IRC all day. It's your choice.
i write software for other people, not for myself. ssupporting them through
IRC is time-efficient even if it is not always attention-efficient. i also
write software in active collaborations with several other developers, who
do not all share the same geographic space.