"In 1996, Hejlsberg left Borland and joined Microsoft. One of his first achievements was the J++ programming language and the Windows Foundation Classes; he also became a Microsoft Distinguished Engineer and Technical Fellow. Since 2000, he has been the lead architect of the team developing the C# language. In 2012 Hejlsberg announced a new Microsoft project, TypeScript, a superset of JavaScript."
I can only speculate that lots of skilled Borland developers followed Hejlsberg and participated in creation of C# and later TypeScript.
1. At peak popularity, Borland products where easily available. Borland decided to turn to enterprise and raised the price considerably, so individuals and small companies started looking elsewhere. By the time they realised the mistake it was too late. In my opinion this was the biggest mistake.
2. Internet and Linux came, and with them Perl, PHP, Python and others. Borland missed the boat, and again by the time they realised that, it was too late.
3. Sun came with Java and Microsoft with C#, both seen as the future of enterprise, and available for free or at very low cost. Java was extremely popular at education sector, pushing out Pascal and other competitors. Both made Object Pascal obsolete.
So bad decisions and being late to the party. Also it was hard to compete with Microsoft in the long term.
As an unrelated sidenote, at the time when world was turning towards agile, they were building and marketing software for managing waterfall project management. That just shows how disconnected from reality of their customers they were.
I spent 13 years writing Object Pascal in Delphi full time, starting from Delphi 4 and ending right about where Embarcadero entered the scene.
They seriously dropped the ball by focusing on ticking enterprise boxes and charging insane amounts for it rather than evolving and fixing stuff.
We had been winning for a long time because we were close-knit and highly motivated. We were scrappy competitors. The first real blow is that we moved into a new office complex that literally forced the team to sit separately instead on close to each other. That was a big hit on morale and productivity.
Then Microsoft seemed to get its shit together and spend a lot of money on R&D. A lot more than they could have been getting in as revenue. Just after I left this forced Borland into an unsustainable cadence of delivery. Soon afterward Microsoft just started wildly hiring our best people.
The thing is, for the period I worked at Borland, I instigated or participated in many of the innovations in process and testing that even today are coming as a surprise to people I teach… We had a fantastic team! Jothy Rosenberg, for instance, whom you can find on LinkedIn as founder of his Nth successful company, was my counterpart in development. He’s probably the most gifted technical leader I have encountered in my whole career.
* Their application business lost out to Microsoft many times over the years. (Sidekick, Quattro, Sprint, etc.)
* The availability of free and open source development tools went way up. (This undermined the ability to make money selling development tools, even as they become more expensive to develop.)
* They lost Anders Hejlsberg to Microsoft. (His Microsoft resume is a testimonial to his skills, technical and otherwise, but prior to that he was the driving force for the Turbo Pascal line through Delphi. They did diversify, but Turbo Pascal really was Borland's core asset.)
* Developer mindshare pivoted away from client apps to web apps.
"Dear Phillipe, I am not your fucking friend. Got it, Phil baby?"
How could you not like a man who'd stick that on his office wall?
I do not think anything comes close to the practical feature set, ease of use, power and long term stability for GUI creation. Well QT does but at what expense.
Meanwhile HTML/javascript based frontends is a pitiful clusterfuck comparatively. Modern computers have more than enough power to have the HTML/javascript front end with the power of Delphi. Why oh why web tool creators have to come up with abominations like React instead. The end result is that in case of Delphi the tool works for you. In case of popular web GUI frameworks it is the other way around.
Terrible title but great book.
Basically Microsoft dominated every software category by waiting for the #1 company to make a dumb mistake. They then swooped in and won.
This book is an excellent but biased history of that era.
At the time Borland had sued Microsoft for some big IP feud.
Then suddenly an arrangement was made. Delphi for Linux was rushed, released unfinished and flopped. Borland got $30M and access to every .NET documentation. But Delphi.NET was never very popular because it was never as good as VS.NET.
.NET modules were added to Windows native Delphi and slowed down the IDE.
IDE price skyrocketed, users flew and after some acquisitions dance, Delphi is owned by IDERA... not sure how it's doing now because they closed developers' forums years ago.
At that time I was using Borland C++ and the quality really went downhill. Errors that never should have gotten past QA. Either they weren't checking or were intentionally shipping with killer bugs.
One release the license said you couldn't use it to make a long list of products that would compete against Borland, like spreadsheets or databases. They rolled back that provision a little later.
Then releases every couple of months.
I just gave up them, they had burned the tremendous good will originally generated by Turbo Pascal, which, it should be mentioned, was created originally by Anders Hejlsberg.
Borland bought the company for less than the VCs had invested, cut the price to $99, advertised it, sold it by mail order, and made it a hit for a couple years.
Several of the key execs at Analytica went to Borland and then to Microsoft; some of them are fairly famous now. I don't know anything about the limos or the lawsuits.
I heard Kahn talk in early 1985, and the Analytica founders made fun of him, for selling his product through mail order when everyone knew you had to go through BusinessLand and ComputerLand.
Same colleague had some vocal criticism of `gdb` as a debugging tool, and the state of Linux-based debugging tools as a whole, with claims that "Borland's were much better, and Visual Studio (not VS Code) being one of the few development environments with a quality debugger".
I'm not sure how fair that assessment is, I've found `gdb` to be a helpful tool, though I've never used Visual Studio.
In 1982ish in Germany I was programming my Apple II in Applesoft Basic and UCSD Pascal. UCSD was 3 floppies, I had a 2 floppy system so for certain steps one had to physically swap floppies.
I attended an Apple User Group In Frankfurt and somebody demo'ed Turbo Pascal 1.0 on their Apple with the Z80 add-in soft card under CP/M. Everybody was amazed with the speed and integration. I bought a copy on the spot, received it maybe 3 months later as it had to shipped from the US. By that time it was on version 2.0. I had bought the Z-80 card in the meantime and switched all software development to Turbo-Pascal.
Delphi was super good as well.
We have only gone backwards since those days..
Another thing happened around that time, as the memory size and speed and number of desktop computers multiplied. Software broke out of the 640 kb limit, so feature sets went bonkers. This made it extremely challenging to deliver products with a very low price and very low support cost, two pillars of Borland's success. C++ came along, to develop which MS could afford a 9-figure price.
All of this put a lot of pressure on Borland and everyone else. Total profits for the software industry were lower than total profits for Microsoft. Borland and many others could not find a way and ran to the exits.
I know they had Windows IDEs but lets be honest, just like Wordstar, Lotus 123 and a bunch of others they were way too slow to move to Windows in the industry shake up that was Windows 95.
A while later the same mag gave away a copy of Delphi. That really opened things up. I found it was more accessible and was quickly making all kinds of stupid windows forms apps and sharing them with friends.
So, no insight into what went wrong but the name Borland has very positive associations for me, and it's safe to say their products played a role in the course my life took.
I also wonder what Phillipe Kahn is up to: https://en.wikipedia.org/wiki/Philippe_Kahn
He does get a few things wrong though, like open source. The best bits focus more on the 80ies.
The thing I remember most: They had some guy (short, with very long hair) that did demos for them. Live and without a net. He was good, and a good crowd pleaser. I hope he's doing well today.
[1]: https://en.wikipedia.org/wiki/Borland#Inprise_Corporation_er...
Microsoft poached dozens of key staff with 7 figure signing bonuses.
Also, ISTR some anticompetitive thing with Windows APIs, but the poaching was decisive.