They refuse to even have Pascal like enumerations, rather pushing that stupid iota/const boilerplate without any of the nice features that Pascal enumerations had in 1970's.
Rather take C# when given the option.
• Extremely fast compilation (even if at the cost of throwing away generations of optimizations)
• Strict, somewhat impoverished type system
• Simple but pragmatic module system (Go has packages, OP has units)
• High focus on integrated tooling (e.g. built-in assembler/linker)
• Safe strings and dynamic arrays built into language
• Built-in reflection and a runtime that often makes use of it
I would argue that if you gave ObjectPascal a C-ish syntax and added built-in concurrency and GC, it would look and feel more like Go than anything else.
Yes, OP has enums and ranges and Java-style interfaces, but those are minor details.
> Extremely fast compilation...
> Safe strings and dynamic arrays built into language
Even Lisp and PL/I have these ones, we really lost focus with C's adoption.
> I would argue that if you gave ObjectPascal a C-ish syntax and added built-in concurrency and GC, it would look and feel more like Go than anything else.
That is C++ Builder.
I have used all Borland products starting with Turbo BASIC 1.0, moving into Turbo Pascal 3.0 and then all TP versions, Turbo C++ 1.0 all the way up to the last Turbo C++ for Windows 3.1 version.
Delphi up to Delphi 5, and the accompanying C++ Builder releases.
Go is really nothing like Object Pascal, nor in features, nor in spirit.
It is a mix of Limbo with Oberon-2 method syntax, from UNIX folks that were always quite against Pascal, none of the authors is fond of Object Pascal, and it shows.
Evne in its heyday, Borland's Pascal-based products were not that big in the developer tools market. Delphi was a huge hit in Europe, but in the US, they were dwarfed by Microsoft. So Pascal's influence is a bit like that Brian Eno saying (paraphrasing): “Only 30,000 people bought the first Velvet Underground album, but everyone who bought it started a band.”
Part of Borland's fall was betting too much on client/server database stuff at a time when the web was happening. They renamed themselves Inprise and marketed a suite of technologies called MIDAS which nobody remembers anymore. You used Delphi to build database GUIs on top of MIDAS and, say, Oracle. I don't know what they were thinking. They also did a Linux version of Delphi called Kylix which was just using Wine (!).
Even so, I suspect ObjectPascal would have failed eventually. A language tied to a GUI toolkit, without a standard spec, or a cross-platform open source implementation, just couldn't last forever.
I held onto Delphi far after it was evident that it was a dying language. I actually did a ton of my work in the 1990s and early 2000s doing non-GUI stuff in Delphi, including web backends and commercial games, which I suspect was not that common. ObjectPascal actually worked wonderfully as a server-side language. It was a strict, statically typed language, it had modern constructs like classes and threads, it was natively compiled, very fast, had a terrific interactive debugger. In many ways a perfectly fine alternative to C++ at the time, including for game development — I made my own bindings for DirectDraw, DirectSound, and so on.
At the time — say, around 2000 — I didn't find the alternatives compelling. Java was dead slow and didn't offer anything language-wise. Languages like Python were also slow and were not type-safe. But there came a point when Linux had just taken over, and ObjectPascal wasn't a viable option anymore.
Today, the closest thing in spirit to the ObjectPascal language isn't C#, I think, but Go.