In the absence of that, Pascal’s creators and commercializers invented follow-on languages, including the most successful thread via Hejlsberg as we’re discussing here: Object Pascal -> Delphi -> C#/.NET—with a brief detour to J++, which I don’t know enough about to understand if it belongs in this sequence.
As for your sequence, from someone that was around back then, .NET and C++ only exist as you know it thanks to Sun's lawsuit regarding Java language and runtime extensions introduced in J++.
Then an internal research language originally named Cool, became C#, the language extensions in J++ were made into C# features (events, J/Direct, COM interop), Windows Foundation Classes became Windows Forms, and J# was released in .NET 1.0 as transiton technology.
Had it not been for the lawsuit, Ext-VOS (.NET codename) would have been released with J++ instead.
https://web.archive.org/web/20190111203733/https://blogs.msd...
Follow the linked paper for Ext-VOS, aka COM+ Runtime, aka .NET.
Microsoft would revisit this COM+ Runtime a decade later with WinRT,
https://arstechnica.com/features/2012/10/windows-8-and-winrt...
Can’t wait to read the VOS paper.
Not Pascal but it comes from that tree.
Given Niklaus Wirth pursue for minimalist systems programming design since Oberon, I doubt he was a big fan of Ada83, let alone Ada2022.
So it wasn't for lack of standard per se.
Though Borland had some commercial success, I remember Pascal mainly as a teaching language.
Ada also was widely used in aerospace/military applications, though not sure it's still used for anything new today.
C, for example, doesn't have strings. It has pointers to memory that might contain characters and, if you are lucky and the stars are aligned, a zero to mark the end. I'll never understand how C strings were accepted as a string representation and not the mad source of bugs and insanity that they are.
1972 was definitely not a good year for C standardization bodies. I blame that guy Ritchie and his audacity to hack a language on a whim. Even his GitHub page is empty (or misattributed).
UNIX and C would never had taken off as they did, had they been sold just like VAX/VMS or MVS.
I think we didn't even have bookmarklets at that point—the browsers supported them, but we didn't know that.
Hem hem,
It's still called RoR though.
I am going to swipe at most dynamic type-unsafe languages: most developers think they are easy to write. And they are compared to type-safe. But the overall difficulty of actually maintaining a project over time and over a revolving door of coders far exceeds the difficulty of using a type-safe language to begin with.
The compiler is your friend. All the compile time error messages are runtime errors you don’t have to look for.
I get why PHP was adopted. A bunch of new coders on the web reaching for an “easy tool”. Not experienced enough to feel the slow encroachment of suck embracing them. It’s really kind of sad. We could have had better languages. Pascal in both the back and front end.
For a historical perspective, the original Delphi code was written by Jan Barendregt. After his death, I was the only person to have his source code -- where most of the comments are in Dutch:).
https://entwickler-konferenz.de/en
Then there is still FreePascal, Mikroe Pascal and RemObjects Pascal to chose from.
And now also Micron, which re-added Pascal features to Oberon (https://github.com/rochus-keller/micron/).
The project is rather cool.
Here's a page from the book I was reading in 1993: https://imgur.com/a/7UWdGgS
For reference, ZX-Spectrum has 48Kb of RAM out of which 8Kb is video memory, so unusable.
Then you have to load the Pascal compiler into the remaining 40k of RAM. Allocate some RAM for stack and environment variables for the editor where you write your program, plus space for the actual program. Then compile your program into the same 40k of space. And run it, using heap and stack memory from which memory space? You guessed right, same 40k.
To recap, on 40k of RAM you had back then: - The Pascal compiler - The Pascal source code in text form - The Pascal executable form in machine code - The Pascal data/memory. Of which, recently in a "tech demo" of automated tests, one colleague said "unfortunately we only have a very limited amount of RAM to be able to do basically anything [that's why the product is a mess with no tests]. Only 32Gb per machine".
One of my first programs was a Tetris clone, because ZX-Spectrum BASIC was slow as molasses. All on top of only having tape for storage so if I fucked up a pointer (I don't think Pascal had the concept of access violation back then but I sure discovered it on my own skin), it would take 5 minutes to load the Pascal compiler + some backup copy of my Tetris game, hopefully not from a month ago and hopefully I remember what I changed. Lots to discover and have "fun" with.
About a year later I did find a compiler for BASIC and it turned the unplayable BASIC code for Tetris I wrote in the 9th grade into a totally playable Tetris game, without the need to learn another language and paradigm (pointers!) but the damage was done. Ignoring a year of databases, in 12th grade of computer science class, I got introduced to C and from then on, here I am, 30 years later, doing C++ in finance for an S&P 500 company.
It morphed into Delphi. The reason that it's not that successful anymore is that it was deeply tied to Windows (even if there were half-arsed Macintosh ports).
And then the Internet taking off happened.
And suddenly you had gigantic companies built on PHP/JavaScript/Linux (like Facebook), on open-source software (Google) and Pascal/Delphi got also attacked by actually portable stuff, like Java, which some of today's biggest companies were built on (like Amazon).
So on one hand Linux and it's myriad of open-source languages and on the other hand Java (which is what it is but it is portable) and then JavaScript in the browser.
Nowadays tens of billions of devices, including many servers powering the entire world, are running Linux. While Pascal/Delphi was that language you'd run on DOS and half-arsedly ported to Windows: not a winning proposition.
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.
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.
https://en.wikipedia.org/wiki/Macintosh_Programmer%27s_Works...
The lack of a good web platform has been mentioned but also there wasn't really any Unix heritage and on Windows the .NET platform and C# killed the advantages Delphi had over Visual Basic 6.
I was a Delphi developer for a bit and most of us moved to Java if we wanted to stay if Microsoft platforms.