Re: Delphi in the enterprise

However, they indicate they do indeed want to address the Enterprise
.Net area as well. Currently their view, as was stated to us by Boz,
is that most of the larger customers are going to buy VS no matter
what and so Borland will sell the rest of the package to them (the ALM
tools already integrate with VS).


Yep, I agree with Boz' assessment there.

IMO, Borland has been weak on providing a .NET solution for their SDO vision; but when they do seriously address the .NET market for SDO, it will be done with VS.NET as their primary IDE.

However (again), the effort to have BDS come together as a true studio
(C# and C++ as well as Delphi) *should* mean that they do indeed have
a product they can ship with any sales into these corporations for
.Net and I expect they will be able to do so; the only question is
whether they will *make the effort* to do so.

I doubt they will make the effort to push BDS into enterprises. What they will do is integrate into VS.NET and sell a much more expensive CoreSDP solution on top of VS.NET. The effort required to push BDS into an enterprise is not worth the money reaped for that effort.

As we all know, once developers get attached to a certain IDE, it's almost impossible to pry it away from them. Therefore, IMO, it would be foolish for Borland to jeopardize a much larger sale (100k+) for a smaller amount of additional revenue (20k-50k). If I were a salesperson the last thing I would do is try to push BDS in favor of VS.NET, when CoreSDP for .NET can be positioned as an upsell for VS.NET. BDS is just a distraction from the larger sale Borland wants to make with its product suite.

The packaging of JBuilder into a larger CoreSDP offering is Borland's
response to a market trend where they see larger enterprises no longer
buying development tools by themselves - IDEs are a *necessary but
insufficient* component and are beginning to be taken for granted
(commoditized), and thus they are something that is included with the
larger package of tools rather than independently marketed. However,
it should not mean the IDE that is included *can't* be BDS where
appropriate.

Certainly. I suspect that BT is one of those enterprise places that does use BDS. Although, I defintely believe that the majority of the enterprise market uses VS.NET for .NET development.

--
Brian Moelk
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.brainendeavor.com


.

Relevant Pages

  • Re: Delphi in the enterprise
    ... The more Borland sells their CoreSDP for .NET stuff, the better it is for MS ... teamsystem will be more profitable if the ALM ... need BDS in next 2-3 years to push into that market. ... pushing BDS as the premier IDE in their .NET CoreSDP offering is ...
    (borland.public.delphi.non-technical)
  • Re: Opportunity passed by
    ... That means Kylix would be competing with Java, and I doubt they would have ... in order to target the browser Borland would probably have had to reinvent ... you produce an IDE as buggy and maginally useful as Kylix. ... But arguably not productive enough to make the market viable. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi in the enterprise
    ... BDS simply doesn't have the market penetration that VS.NET does in the enterprise space. ... Nor does it make too much sense for Borland to push BDS over VS.NET when what they want to sell is .NET ALM/SDO product. ... Delphi is not a mainstream language, it never was and never will be. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi in the enterprise
    ... + It is good that Borland is aiming for VS market, ... - integration within VS 2003 and now 2005 is much easier then it is in ... - Saying that Delphi or BDS in this extend is like saying that ECO in not ...
    (borland.public.delphi.non-technical)
  • Re: About .NET strategy
    ... I don't believe this means that Borland should concede the platform as a whole from a Delphi standpoint. ... MS on the IDE front and maybe even win a few VS developers along the way. ... IntelliJ has carved out a market between the two. ...
    (borland.public.delphi.non-technical)