Re: [AD] Splitting filesystem APIs

[Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx>]

On Sat April 18 2009, Evert Glebbeek wrote:
> On 18 Apr 2009, at 22:23 , Thomas Fjellstrom wrote:
> > Fine. Feel free to remove all my work.
>
> Oh, come on, please. Don't be like that. No one said they wanted to do
> that and no one said they don't appreciate all the hard work you've
> done.
>
> > Don't make a new api that will be
> > easier to work with, especially for new coders.
>
> Ok, rather than exchanging opinions on what's easier and what isn't,
> why don't we get a clear picture of what the advantages of either
> design are (I know, some things have been mentioned here and there as
> examples for this case or that, but I for one don't have a clear image
> in my mind that gives me the complete picture) and give clear, real
> world examples. Get some input (especially from aforementioned "new
> coders"). Get a few people from ACC who have been using the new API to
> comment on things.

How do you think I came up with the design? I asked on A.cc, the mailing list, 
and the IRC channel. I did some actual research. I guess it was so long ago 
that you've all forgotten?

> > No we don't need to evolve
> > anything at all, it just needs to be more of the same.
>
> Now you're just being silly.
>
> > Trying new things == bad. Obviously.
>
> No, but changing things for the sake of changing things is worse. And
> there *is* something to be said for a conservative design that people
> are more familiar with.
> Hey, guess what. I never liked state-based APIs and I still don't. But
> I can live with it.

I also never liked being called silly.

> Evert
>

It is becoming clear that I have less than no say in what happens to the lib 
though. (I suppose thats fine, I've really only contributed this code, the old 
alsa 0.9/1.x driver, and a small fix for xinerama support in a5). It has made 
me think about evaluating how I spend my time. I'm not sure this has been 
entirely worth it.

-- 
Thomas Fjellstrom
tfjellstrom@xxxxxxxxxx