Luigi Sandon wrote:

> > Wow, what faith. I'm touched.

> Telling your customer now how you are going to implement xplat GUI
> will allow the to decide if Delphi will be their way to go xplat, or
> if their requirements need a different tool. For you nothing changes
> - those who won't find your xplat approach appealing will use other
> tools anyway - you avoid to turn hopeful customers into disgrunted
> ones later, you'll just allow them to plan their xplat future earlier
> and with the right knowledge - as it is expected by a technology
> partner. Instead you often work a gainst your own customers, once it
> was SOX, not it is whatever else, and we don't understand why. We're
> just left unable to plan for our product future, that in turn it's
> often yours too.

I hate the lack of information too. I wish I could say more. But the
cold hard reality is that if we divulge too much too soon, sales of the
current product tank, layoffs happen, pay is cut and we are left with
less people, less time, and more work. I've seen it happen many times.
It sucks for us, it sucks for you.


As for the xplat plans, we're working hard to get something very usable
before we begin to divulge the details. Many of us were around for the
Kylix days and are fully aware of some of the problems with the
frameworks.


FWIW, Kylix was *very* successful... The problem was that it took way
too many resources from our core product, so it suffered. Also the
upper management forced us to price it a little too high for the market
at large. If Kylix were the only thing we did, it would be considered a
resounding success and it would probably stil be around.


-- 
Allen Bauer
Embarcadero Chief Scientist
http://blogs.embarcadero.com/abauer