[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] FW: WCOWORK vs WINDOM for components
Quoting Lonny Pursell <atari@bright.net>:
Because there are no libs that require or use WCO to date, thus you are in
effect talking about old libs. As I said if you want to use it you will
have to be darn sure all your components can deal with it. It's new.
Old libs? You mean ALL libs. Making sure all components can deal with it
sound like exactly my point ... I can't use it, so why should someone else?
And it goes nowhere.
Even if you changed the way it works, and converted it all to new API calls.
Same problem. Someone could just as easily make a lib that required the new
API calls and ignores the old calls, or vise versa. Then you are back to
square one, not knowing what works with what.
This is an endless loop.
My point exactly!
I have tried. Not getting anywhere. I would suggest at this point you do
one of 3 things.
1) Stop complaining about it, since that route generally don't work in the
end, especially if the main gripe is simply "This is not a good design"
That does not exactly clarify anything for Ozk.
I'm not complaining - I've asked for specifics on what the benefits are
and why
the alternative solution would not offer that benefit, but no one can tell me.
2) Present some VERY detailed alternative with some example code, API calls,
docs etc. Pretty much the only way you are going to effectively change
minds.
I did! No one read it or they simply dismissed it. Ozk simply ignored it
because he is adamant that using new calls is a bad idea, but has yet to
express why. Apparently no one knows the answer.
3) Take over dev yourself. Ultimately the best way to get your point
across.
No - Implementing my ideas without discussion is as bad or worse than
implementing someone elses. I want the discussion and resolution and
compromise to get the majority of people understanding why its being done and
happy with the solution before its implemented. I see no point in fragmenting
whats left of the existing user base. We're supposed to work together here.