Re: DiamondBack support CF, Avalon?

From: Jim Cooper (jim.cooper_at_virgin.net)
Date: 09/18/04


Date: Sat, 18 Sep 2004 13:40:50 +0100


> I understand, but my point is that Again Borland is missing the "boat".

Eh? How can they miss the boat? Avalon is still in beta. **Nobody**
supports it yet, not even Microsoft. It is just not possible to support
it yet. When it is available, Borland have said they will support it.
Whether that will be a patch to Diamondback or a new product can not yet
be predicted as it is not known for sure when Avalon will ship.

> Agree, but you still need to write different code to develop a browser based
> app and for the Windows platform.

Yes. Mostly because they require entirely different code, not just
different visual controls. I say again, a desktop app works completely
differently from a web-based one.

> My point is: since D1 Borland misjudge the popularity of Internet and
> NOT providing RAD tools for developing Browser apps..

Then you are completely wrong. Borland have been providing tools for
doing exactly that for a long time now.

> MS understand in the same period after D1/D2 the importance of Internet

And that shows a great deal of ignorance of the history of MS and the
internet. It was quite some time after D1/D2 that they caught on.

And I say again, since we now have ASP.NET, Borland only needs to
support development in that environment (which has been the case since
C# Builder). It would be downright stupid to invent a competitor.

> You missed my point again... Of course Borland cannot compete with ASP.NET
> because they all sleeping since D1....

What? I somehow don't think you understand what ASP.NET is. Why would
anyone want to compete? Have you seen how even the latest Intraweb stuff
actually works **in** ASP.NET?

> I still think that the company that can offer ONE sourcecode environment for
> developing Windows and WEB applications

Then I don't think you understand the fundamental differences in the way
those two types of applications work.

You can right now develop the same core business logic and have a web
and a desktop front-end, but having the same code for both sorts of UI
for anything but the most trivial case is doomed to failure. Web-based
apps have a ton of limitations that desktop apps just do not have.

> I suppose that this newsgroup are too crowded with "f" BIT" developers ;-)

I have no idea what that comment means.

Cheers,
Jim Cooper

_______________________________________________

Jim Cooper jim@falafelsoft.com
Falafel Software http://www.falafelsoft.co.uk
_______________________________________________



Relevant Pages

  • Re: Why Botrland are pushing C#? Is it to kill off Delphi?
    ... Dave Jewell wrote: ... It would seem that Borland may have been ... > Are we talking about visual form designer support for VB Winforms ... That is what I was talking about, and source codegen for VB apps. ...
    (borland.public.delphi.non-technical)
  • Re: Windows 95
    ... The fact that D1 apps may run on Vista does not mean that D2006/D2007 ... but I certainly would not expect Borland to support it. ...
    (borland.public.delphi.non-technical)
  • Re: usual nontechnical issues
    ... doubt that it will die, as it has, in my experience, been one of those things that made selling Delphi copies easier. ... MS has been pushing VB for enterprise apps for 10 years now... ... Mono is supposed to do that for dotNet developers??? ... Borland drops VCL, it will be IDE and language that complies to MSIL on top of net. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi Software Assurance ~ Buyer Beware!
    ... > pertain to all Borland products support, ... > Responding to the issue costs Borland money. ... If it's a bug, then they don't ...
    (borland.public.delphi.non-technical)
  • Help for deciding my future roadmap
    ... that cause failure, that its, follow the idea "self contained apps". ... i wanna support MS because market and because under proper ... - I wanna support Sql Server, ... - For realize this vision, i think in use Delphi, Kylik for main ...
    (borland.public.delphi.non-technical)