[PD] benevolent dictator? (was: 2d multiple preset interpolation?)

[Roman Haefeli]

Sorry for my random rant, but it seems purely illogical to me, that for
instance maxlib is loaded on default, which seems to have no maintainer
anymore, is buggy in some respects and creates name clashes, while
iemmatrix, a clean library, which has an active maintainer with a
well-established reputation, and which even uses a prefix and thus is
unlikely to cause any name clashes is _not_ loaded on default.

I picked some random examples, which I chose simply because I stumbled
across them. And I am aware, that this is an old discussion. It happened
to jump into my eyes just now, that's why I am bringing it up.

Is there a way the community can participate in those processes?
Currently, those things seem to be based on 'gut-decisions' made by the
benevolent dictator. Hans, if that is clearly not the case, please
accept my apologies, but that's how things look to me. 

Likely there are historical reasons for the current list of
automatically loaded libraries. However, this list looks very random to
me and I am not clear, what purpose or rule it is following. Personally,
I'd prefer to not auto-load anything at all, which would also encourage
a nice patching style with explicitly loading the required libraries.
I'd be interested to hear what others think about the matter. 

Hans, although my rants seem directed to you, let me say, that I very
much appreciate the work you put in into Pd-extended. I hope you agree,
that there might be better ways of composing a list of loaded libraries
than you just picking some.

Cheers
Roman



On Tue, 2010-07-13 at 10:44 +0200, Roman Haefeli wrote:
> On Mon, 2010-07-12 at 20:34 -0400, Mathieu Bouchard wrote:
> > On Tue, 13 Jul 2010, cyrille henry wrote:
> > 
> > > yep. cyrille
> > 
> > is yours supposed to be working in pd-extended ?
> > even when adding "iemmatrix" directly to the library list,
> > 
> >   mtx_./
> > ... couldn't create
> >   mtx_.*
> > ... couldn't create
> >   mtx_.* -1
> > ... couldn't create
> >   mtx_.* 0
> > ... couldn't create
> >   mtx_+
> > ... couldn't create
> >   mtx_./ 1
> > ... couldn't create
> >   mtx_.^ 0.5
> > ... couldn't create
> > 
> > does it work with a more recent version ? how recent does it have to be ?
> > 
> 
> I added all missing aliases, so that using those names works directly
> also in Pd-extended's libdir format, without having to use any quirks as
> loading [mtx_add] before [mtx_+]. 
> 
> Unfortunately, Hans is not comfortable with auto-enabling hexloader, so
> in order to be able to use those aliases, you need an [import hexloader
> iemmatrix] in order to take advantage of those aliases.
> 
> Even I, who already discussed with Hans about the issue with
> en/disabling hexloader on default, first forgot to enable it manually,
> which made me think, that the aliases are not working. I still think,
> that _not_ enabling hexloader causes more confusion than simply loading
> it on default. I thought I delivered enough proof that it is not causing
> any harm.
> 
> So, using an rc4 autobuild and putting an [import hexloader iemmatrix]
> (iemmatrix is not loaded per default) should work.
> 
> Roma
> 
> 
> 
> _______________________________________________
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list