Leo Simons wrote: >> + A4 -> A5 proposal would have changed just about everything about >> how you write and interact with components. (Instability.) >> >> <more snipped>
> >How many people have mentioned to you over the last few days they are >unsure of using avalon because they hear in places it is unstable? The >goal of marketing and branding is increasing the user base (besides >other things), marking products as unstable decreases the user base. > > > How about if this is not made more complex of a problem than it really is? From an outsider's view it seems to be only an ego problem wrapped up in call signatures. Just set the ego aside long enough to come up with one set of interfaces or call signatures or meta-info patterns or whatever you want to call the communications pattern. Make it please Stefano and Peter Donald and every other committer. And if possible make it as simple as possible to grasp. But once you have the communcation pattern down that pleases everyone, stick to it even if it isn't perfect. That is what outsiders think of as stability, or so it seems from my simplistic viewpoint. Repeat, this is not nearly as challenging a set of objectives as perfection. But you can always perfect it later, on the practices side. Just leave the communications patterns stable. Wish there was a better name for communications patterns. I would just call it interface, except for that leaves out meta-info, config files and every other form which is just as important.
