Hacker News new | ask | show | jobs
by pjmlp 921 days ago
More than that, what killed Pascal on the PC was Borland leaving the small devs market.

What ate Delphi's lunch, besides Borland's mismanagement going enterprise prices, was Java and .NET.

And even so, there is enough user base to keep an anual conference in Germany, and regular articles on development magazines like .NET and Ct.

2 comments

Borland did a lot of thrashing around that point. They were a great language company, but they wanted to be Microsoft. At one point they had their own spreadsheet (which was pretty good, but DOS only) and their own database manager. And some of their language products were weird (Turbo Prolog, which, so Prolog people tell me, wasn't quite Prolog).
I see the same pattern in JetBrains now, with Kotlin being their Delphi, trying to put it everywhere, instead of building on the strenghts of JVM/ART.

Everyone had their Lotus competion product on those days, Excel still wasn't the winner.

When Turbo Prolog came to be, every Prolog was a bit different. Even a decade later trying to write portable Prolog code between SWI and SICStus wasn't properly easy.

>More than that, what killed Pascal on the PC was Borland leaving the small devs market.

Correct. My memory is vague on this, plus I don't know a lot about it, but I think people were even creating commercial shrink-wrapped software in Turbo Pascal, in its heyday. And of course in Delphi too, later.