You are assuming that I am criticising the Pascal language or Lazarus/FPC developers but that's not my case.
In retrospect that sounded more harsh than I meant it, I'm not criticizing you, nor your ideas. Such schemes (in application languages) certainly have merit. I merely point out that the overlap with the combined Lazarus/FPC project's direction is very low (except for that COM support is getting better and better).
I also didn't mean to send you away or anything like that. It was merely meant as a "don't hold your breath", and maybe encourage you to look for some other language or embedded interpreter for in-application uses.
The decline of Pascal is not a matter of lacking new converts, but existing users choosing other languages, not because they are superior but because the developing environments suit their all round needs better.
I don't agree. I mainly think users chose development systems due to their attachment to large IT vendors, not based on merits of language and environment in itself. The big problem there is that Borland/Embaradero simply is not in the Microsoft/IBM/Oracle/Apple/Google league.
And the OP is right, Borland/Embarcadero messed it up, or a lot of the team left Borland for Microsoft to go and develop C#.
Borland/Embacadero messed up a lot, that's for sure. However that doesn't necessarily mean that if they hadn't, the outcome would be vastly different. I think it would mostly been gradually different (exactly
the same situation, with some more life in the Delphi platform. But certainly not more dominant or on equal footing with MS offerings)
The sign of times in the early 2000s was simply that major IT vendors wanted more control over their developers and did that by offering own toolchains. Mostly to better steer the direction of their targets, and as a conduit to the developers (read: to sell additional products, think about e.g. SharePoint server, SQL Server etc). That had two effects: they could give their own toolchain preferential treatment, and it made life harder financially for 3rd party vendors (they had to invest more to keep up, while their user bases were decimated), while the major vendors partially wrote of the toolchain expenses on the "main" business.
Ideally you would want to use the same language for everything everywhere, but if your preferred language works only as a compiler then it gets frustrating, but that is not the fault of Lazarus/FPC developers or Embarcadero for that matter because those tools were developed to serve application developers needs.
I'm also not really sure with that statement. Yes, I don't want to use TOO many languages since that makes life hard. On the other hand, as soon as adding compatibility for targets that I rarely use start to influence my main target in a negative way, I often prefer splitting development environments and codebases (IOW not one codebase for all).
Simply because the main business brings in the bacon, and while more targets is nice, usually the newer targets are either temporary or a side business.