Re: five years old future

From: Dan Miser (dmiser_at_wi.rr.com)
Date: 02/11/04


Date: Wed, 11 Feb 2004 09:50:41 -0600


"Hrvoje Brozovic" <a.b@c.de> wrote in message
news:4029e0fe$1@newsgroups.borland.com...
> My impression is that they were more improved
> because of kylix forced them to revisit sysint, system and sysutils.
>
I would agree that Kylix had a positive impact, in addition to the
distributed application focus, yes.

> Serviceas let their own windows live after logon logoff,
> and after that it can't find them anymore, dll init code was
> doing loadlibrary calls which is documented no no,
> and threads works only using with workarounds.
> (you must google for this one, since there
> are to many non working scenarios )
>
Ah, so we're talking about some of your pet bugs and generalizing that into
a whole argument that Borland failed all of us.

> > You can interface to those other Windows technologies (DirectX, OpenGL,
> > etc.) using Borland tools just fine. Had Borland extended those
> technologies
> > only to have MS co-opt Borland's ideas, I'm sure you'd be clamoring that
> > Borland had no vision there either.
>
> No, I'll be happy.
>
Sure. Would that be because you have more of an interest in those
technologies than DC? So if Borland pursued that course, the DC crowd would
be complaining. Or should they have just done everything for everybody?

> >Secondly, you've now changed your story from "Borland failed at
> > giving us distributed applications" to "Because Borland did well at
> > distributed applications they neglected everything else".
>
> DC support is mostly components, and core IDE/compiler
> efforts were moved to BCB, Kylix and finally NET.
> Is this neglecting of Delphi for Windows or what?
>
Yes, mostly components. But there *were* compiler efforts to support it,
too. And you've now changed your argument for a third time. We're down to
"Delphi for Windows has been neglected". No, I do not believe that Delphi
for Windows has been neglected for the past 5 years. Part of the things that
happened during platform shifts is that improvements were brought back to
Delphi for Windows (as you mentioned above in the Kylix example).

> I still think that they did not delivered distributed computing in a way
> that they did with IDE and RAD. It was impossible mission anyway,
> since it is not for everybody, and first two things were for everybody.
>
> If their goal was to bring distributed computing to everybody,
> they failed since not everybody using it.
>
You are the only one to claim that Borland wanted everybody to use DC!
Obviously they didn't. Do you think 100% of Delphi programmers are DB
programmers? But the technology shift happened, and Borland was smart to
catch that wave - and in some ways shape that wave for the entire industry.

> If their goal was to give DC to part of their customers, they
> succeeded, but then, with focus on that, it is obvious that they
> neglected others.
>
The "focus" on DC was done by folks who were in the DB group. It wasn't like
they had a meeting one day and said "OK, everyone focus on DC only." It was
a natural evolution from C/S DB programming to multi-tier, DC programming.
But now Borland is being villified by you for having their DB programmers
innovate. Priceless.

> So it is for you to chose: neglect or failure
>
Sure, if you are so narrow minded as to only see your 2 options.

-- 
Dan Miser
http://www.distribucon.com


Relevant Pages

  • Re: The 64-bit Strategy Session commence.
    ... is here, works, I can use SOAP to talk to my Delphi client. ... Sure there are *better* choices than Kylix, the whole point is that you can ... product, etc. IIRC, you stated that Borland was much too late to the party. ... lose their existing customer base. ...
    (borland.public.delphi.non-technical)
  • Re: Opinions on KYLIX 3 (Delphi 4 Linux)
    ... To be fair though, it is easy to see the difficulty for Borland to deploy a Linux IDE of the same quality as Delphi when so much in different Linux distributions is variable, the widget set being a prime example: CLX just never caught on, amongst the myriad of more mature and more open toolsets. ... I am assuming that you have experience with pascal, or ObjectPascal as the Delphi manuals call it (if not, why Kylix?). ... Though python is probably my favourite language for general purpose hacking, there is a lot to be said for a native compiled language, and in particular there is a lot to be said for fpc: ...
    (comp.lang.python)
  • Re: There Will Be No 64-Bit Delphi Compiler Even Ten Years From Now
    ... The Delphi developers are fully convinced that .NET's ... Borland is doing/planning now.. ... .Netv2-64 which are not compatible and for which we will have to upgrade ... I could not do it in any other dev tool like I can in Kylix ...
    (borland.public.delphi.non-technical)
  • Re: Future of Delphi 7.x - need official word from Borland
    ... Another temper tantrum "Never again Borland". ... At present Delphi is powering the turnaround of the company I work for. ... to cause programmers to build lower quality code than Delphi. ... good fit for some business apps, but isn't shining for mass market software. ...
    (borland.public.delphi.non-technical)
  • Re: Borland Layoffs?
    ... David Intersimone (Borland) wrote: ... compilers do not support driver format. ... only compiler left: Delphi. ... versions) to pirate programmers. ...
    (borland.public.delphi.non-technical)