Re: Captain Jake's Top Ten List of what I'd like to see in thenextversionofDelphi

Brian Moelk wrote:

They are, but they could be focusing exclusively on that with their
.NET strategy, putting forth all of their resources (which I assume
that they'll need) to compete against MS. Instead, we have Delphi
for .NET and VCL for .NET which IMO, are two things that haven't
gained any significant traction, even within the existing Delphi
community.

I think if Delphi & VCL.NET weren't 1+ years behind Microsoft's
'current' version of the Framework, it might be getting more traction
than it is. It's hard enough to make the case for a non-Microsoft tool
without also having to make the case for using an old version of the
Framework.

Of course it will take more than just re-wrapping .NET with VCL.

It better, cause VCL for .NET is a dud. ;)

I just sooooo totally disagree with you here. I think it's a weapon
that's been under-deployed in the battlefield, and way undersold.
Borland missed a serious opportunity to capitalize on the anti-MS anger
from VB6 coders. You may think it's bull, but I've been frustrated
with Borland ad after Borland ad which seems absolutely intent on not
saying ANYTHING which might look like it's competing with Microsoft.
The days of the Borland barbarians with the Turbo line are a fond
memory of the good ole days when Borland knew how to punch the bully in
the mouth instead of saying platitudes in hope of not offending (it's
called the 'let's just hang in there as long as we can' approach to
product marketing).

Sure, but ECO development has to put "supporting VCL for .NET" on
their todo list, when they could be working on something else. ECO
is great, DevCo needs to continue developing ECO and do more things
like ECO. VCL for .NET OTOH IMO, is not a strategic advantage.

You're right. VCL for .NET and ECO should have been bosom buddies from
the get-go. Then it would have been. The only issue here is, is it
too late to get that leverage? I don't think it is...but of course
we'll see.

I don't think it is. If you have a mountain of "legacy" Delphi code,
why not just keep it going on Win32? If you need .NET interop, then
use COM or SOAP. One doesn't have to migrate "code" to .NET to
migrate to .NET.

Yuck, Yuck and may I say....Yuck. I don't want to go over the P/Invoke
layer. I don't want to have to wrap my Delphi code in type libraries.
I want to use it as seamlessly as I do now. I've had enough
COM/ActiveX headaches to last me a life time.

God help us all if DevCo decides to let Microsoft dictate rich UI
development with WinForms....

Well, they can and will dictate it, but IMO DevCo can offer a better
alternative within/on top of WinForms.

If DevCo drops VCL.NET and forces us into Winforms, then it will be a
sad day for customer choice. We will have no alternative but to put up
with WinForms as a Windows UI framework, and I shudder at this thought.
Once DevCo stops offering choice, I begin losing interest in its
products.

Randy




--

.

Relevant Pages

  • Re: ruby on rails
    ... I'm describing a strategy to keep the IDE business profitable. ... So it is about DevCo, not Borland. ... I'm not a soldier in the holy war of Delphi. ...
    (borland.public.delphi.non-technical)
  • Re: New Company - new ideas ?
    ... Borland was packed with new ideas and milked Delphi W32 ... If DevCo would do the same, ... I'm talking about functional languages that are getting more and more ...
    (borland.public.delphi.non-technical)
  • Dont cut the umbilibal
    ... It seems to me that since DevCo is getting on just fine even before ... prospects of Delphi and the other Borland tools. ... DevCo becomes a Borland subsidiary, ... prosperity of Delphi. ...
    (borland.public.delphi.non-technical)
  • Re: Devco to encourage VB users to migrate to Delphi
    ... that you don't control this DevCo creation process. ... in the past the phrase "Borland" included all that is now ... say, at that time, that Borland cared about Delphi. ... Delphi because people in DevCo care about Delphi. ...
    (borland.public.delphi.non-technical)
  • Re: Chrome - competition for Borland?
    ... >> and technically) use ECO at VS, unless Borland releases a version ... > (Delphi mainly), hence the library helped Delphi in that whoever ... > wanted VCL needed to use a Borland product. ...
    (borland.public.delphi.non-technical)