Before I begin, let me state that I am a reformed Delphi bigot. I am only such because one can only bang their head against a wall in confusion for only so long. I have been using Delphi since version 1, and have one of the most complete (and useful) Delphi libraries of any Delphi developer I have known. My copy of "Secrets of Delphi 2" is still my most valued tome in my collection, followed closely by Konopka's second "Developing Custom Delphi Components" book. I earned my certification for Delphi 5 in 2001, and attended seven consecutive conferences from 1996 through 2002.
I attended the Philadelphia Borland conference in 1999, and was in the computer lab filling out an online survey regarding my conference and Borland experience. The question asked me for three areas where I felt that Borland could show some improvement. My answer: Marketing, marketing, and marketing. Not an unfamiliar complaint for Borland-philes tired of MS dominance in the corporate application development arena.
A staffer who worked in R&D was looking over my shoulder at my response, and asked me to enlighten him on my response to that question. That discussion lasted 45 minutes. I vented everything from my appreciation for the technological superiority that Borland products provide compared to MS products, to the ongoing frustration of having to inform IT managers that rumors of Borland's demise are vastly exaggerated. Borland has constantly and consistently placed the burden on the developer to be advocates for their products, while providing no voice of their own. The vast majority of IT management have limited exposure to the technical details of competing products, so they focus on colorful ads and glitzy white papers. Borland's attitude can almost be described as "snobbish," choosing not to lower themselves to advertising games or boorish attacks at MS technology. Meanwhile, a frustrated Delphi community feels abandoned and cast adrift, due to the great expense of money, resources, and TIME spent becoming experts of our craft using their tools. By the way, that staffer I was telling you about? It was Simon Thornhill, who later became the Vice President in charge of RAD Products (including Delphi), and is now the Vice President and General Manager in charge of.NET Solutions. He was very attentive during our discussion, and for the next couple of conferences always took time to speak to me if our paths crossed.
When Microsoft gave Borland that $125 million payoff (which I believe was to keep Borland afloat so that the DOJ wouldn't consider them a monopoly), the Delphi developer community saw that as an opportunity for Borland to finally be able to complete with MS on a level playing field. Delphi (version 7) versus Visual Studio.NET (version 1)...do you want to risk investing in new, untested technology or put your trust in a product that has been around for more than six years and seven iterations? Once again, Borland not only dropped the ball, but kicked it out of bounds, down the block, and into the mulcher.
Borland will be around for as long as Microsoft needs them. Whenever the heat picks up from the DOJ, Microsoft will "buy some tech" from Borland just to keep them afloat. For more than fifteen years, the story has been that Microsoft will buy Borland. It will never happen, because, right now, Borland is Microsoft's only competitor, and, to a community's continued frustration, it's not even a competition.
Slashdot Mirror
Before I begin, let me state that I am a reformed Delphi bigot. I am only such because one can only bang their head against a wall in confusion for only so long. I have been using Delphi since version 1, and have one of the most complete (and useful) Delphi libraries of any Delphi developer I have known. My copy of "Secrets of Delphi 2" is still my most valued tome in my collection, followed closely by Konopka's second "Developing Custom Delphi Components" book. I earned my certification for Delphi 5 in 2001, and attended seven consecutive conferences from 1996 through 2002.
.NET Solutions. He was very attentive during our discussion, and for the next couple of conferences always took time to speak to me if our paths crossed.
.NET (version 1)...do you want to risk investing in new, untested technology or put your trust in a product that has been around for more than six years and seven iterations? Once again, Borland not only dropped the ball, but kicked it out of bounds, down the block, and into the mulcher.
I attended the Philadelphia Borland conference in 1999, and was in the computer lab filling out an online survey regarding my conference and Borland experience. The question asked me for three areas where I felt that Borland could show some improvement. My answer: Marketing, marketing, and marketing. Not an unfamiliar complaint for Borland-philes tired of MS dominance in the corporate application development arena.
A staffer who worked in R&D was looking over my shoulder at my response, and asked me to enlighten him on my response to that question. That discussion lasted 45 minutes. I vented everything from my appreciation for the technological superiority that Borland products provide compared to MS products, to the ongoing frustration of having to inform IT managers that rumors of Borland's demise are vastly exaggerated. Borland has constantly and consistently placed the burden on the developer to be advocates for their products, while providing no voice of their own. The vast majority of IT management have limited exposure to the technical details of competing products, so they focus on colorful ads and glitzy white papers. Borland's attitude can almost be described as "snobbish," choosing not to lower themselves to advertising games or boorish attacks at MS technology. Meanwhile, a frustrated Delphi community feels abandoned and cast adrift, due to the great expense of money, resources, and TIME spent becoming experts of our craft using their tools. By the way, that staffer I was telling you about? It was Simon Thornhill, who later became the Vice President in charge of RAD Products (including Delphi), and is now the Vice President and General Manager in charge of
When Microsoft gave Borland that $125 million payoff (which I believe was to keep Borland afloat so that the DOJ wouldn't consider them a monopoly), the Delphi developer community saw that as an opportunity for Borland to finally be able to complete with MS on a level playing field. Delphi (version 7) versus Visual Studio
Borland will be around for as long as Microsoft needs them. Whenever the heat picks up from the DOJ, Microsoft will "buy some tech" from Borland just to keep them afloat. For more than fifteen years, the story has been that Microsoft will buy Borland. It will never happen, because, right now, Borland is Microsoft's only competitor, and, to a community's continued frustration, it's not even a competition.