Re: Embarcadero Technologies to buy Borland's development products unit!



Isn't that a good thing, setting aside the damage already done?


I think so too. I'm excited to see what happens going forward. After Paradox a lot of us expanded our skills to include Delphi (many just left Paradox and went to Delphi). Delphi was king of the development world for several years and was an exciting time. Delphi went from supporting 16-bit Windows to 32-bit Windows then added Linux. About that time .Net started to take off and many Delphi developers migrated to VS.Net using C#. Borland then dropped Kylix (now a dead product for all intended purposes) but jumped into the ..Net realm. Now there's Delphi for Win32 and Delphi for .Net and soon there will be a Delphi for Win64. There's a bit of a battle going on within the Delphi community to keep as many Delphi developers as possible. Here's an interesting thread going on at the Prestwood Boards about this topic...

http://www.prestwoodboards.com/ASPSuite/eBoard/Thread.asp?MBID=12733

The battle for the future of Windows development is an interesting war to watch. The future of 32-bit processors and Win32 is probably the biggest threat to Paradox considering it doesn't look like Corel is going to port Paradox to a 64-bit processor. However, legacy Paradox apps will probably run for along time. Consider the fact that Microsoft just recently started the process of dumping DOS applications. Vista 32-bit supports 16-bit DOS apps but Vista 64-bit does not so you have to result to emulators.

They also offer Delphi for PHP but the name is really just a marketing thing.

"Larry DiGiovanni" <nospam@nospam> wrote in message news:482302b4@xxxxxxxxxxxxxxxxxxxxxxxxxxx
Rodney Wise wrote:

What's up????

Uh, Borland spun off its developer tools division as CodeGear for the expressly stated purpose of selling it off, because Borland wanted to focus on lifecycle management tools, not developer/RAD tools. Your rant is two years late.

The Embarcadero acquisition is probably a good thing for the CodeGear tools.

RAD Software developing tools are used to produce complex solutions that may takes several years to develop...

Really? Then why call it Rapid Application Development?

Most software developers also hope that it will require many more years
to support.

Software of any value requires years of support.

In my opinion, Borland has hurt itself severely by constantly trying to "find itself"...

Borland's ongoing identity crisis can no longer harm users of its development products. Isn't that a good thing, setting aside the damage already done?

--
Larry DiGiovanni


.



Relevant Pages

  • Re: (Microsoft) The Future of Delphi?
    ... Paradox was a non-factor. ... Microsoft Access quite frankly crushed it. ... So even if Borland, at that time, did not foresee the writing on the wall before the acquisition, the result is that, by owning these formats and making it easy to get to from Delphi via the BDE, Borland provided a natural migration - people could go to Borland in order to develop new front-ends for existing Dbase and Paradox databases. ...
    (borland.public.delphi.non-technical)
  • Re: Borland : Inprise : Codegear
    ... It spun off the Developer Tools Group which is responsible for Developer Studio (Delphi, C++, C#), Jbuilder and Interbase. ... Borland no longer does developer tools (those are done by CodeGear) but now focuses on ALM and other enterprise-level technologies. ...
    (borland.public.delphi.non-technical)
  • Importing Delphi .dll into Paradox 7 issues
    ... I have a very interesting situation involving importing a Delphi ... .dll that I wrote into Paradox 7. ...
    (borland.public.delphi.language.objectpascal)
  • Re: which type of database should i use?
    ... gets along well with delphi? ... suggest that you simply use the BDE and either Paradox or Access db. ... system crashes (and just try to find the lock files on an XP ...
    (comp.lang.pascal.delphi.databases)
  • Re: New features for Delphi
    ... The reason I see Paradox so valuable in tandem with Delphi is NOT for its database particular qualities. ... the object model, the RTL, is well architected, feature complete and simple to understand ...
    (borland.public.delphi.non-technical)