> From: Leo Simons [mailto:[EMAIL PROTECTED]]
>
> > + A4 -> A5 proposal would have changed just about everything about
> > how you write and interact with components. (Instability.)
>
> "would have changed". Not: "will change". Before avalon 5
> goes alpha this will, highly likely, not be the case.
Dropping this - more important things below. We can always come
back to this.
> 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.
Marketing isn't about always saying nice things, it is about
*doing* nice things, in my opinion.
I have taken steps to improve our branding and marketing, and
I hope I can get you and the rest into a discussion regarding
this:
+ MicroContainer will allow a zero-committment use of Avalon
components. You get the functionality of your favorite component,
but you do not have to buy into the architecture. Get you hooked.
+ As I said, I see three levels: Micro,
Embedded and Server. Micro->Server, increasing metadata, increasing
container smartness. Server->Micro, decreasing committment to
Avalon architecture. Components working in Micro work in Embedded
and Server, components working in Embedded work in Server.
So Peter can have all the metadata he wants, as long as you still
can create a component without that metadata.
*That* is my idea of marketing. Provide low-committment versions,
provide a path to increasing complexity. You know, anyone using
MicroContainer will scream for Fortress when they want pooling and
XML config.
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
