• 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.
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.