Need card #287 · Relevance High · Status New

Pain points in modern Pascal development

Updated 10/1/2026, 22:08:38

Problem

Developers find that Object Pascal/Delphi lacks flexibility in variable scoping, suffers from cluttered legacy namespaces, and needs better modern tooling—especially for compiling to web platforms—while many former Pascal users are eager to return but lack clear migration examples.

Pain points

Questions to verify

Evidence

quote · @匿名
I used to have object pascal as my main language, and it has a lot in its favour. But when I go back to it I find two things drag it down. Pre definition of variables. I would like to be able to define variables on first assignment and scoped to the begin/end in which that happens, I don't think there is a good remaining argument to keep them above the statements. The namespace is cluttered with legacy usage, making the many years of advancement require odd. Combinations of prefixes. I still think there is a scope for a light fork that changes the name to distinguish it and starts the RTL afresh using the decades of hindsight and improvements.
quote · @匿名
I bought Delphi ages ago, but never got very far with it, which I regret.I'd love to be able to take it up again, and this document looks very promising for that, esp. paired with:https://wiki.freepascal.org/pas2jswhich I now see is supported in Lazarus.If someone has an example graphical project which compiles to an HTML page w/ JavaScript using the above, I'd love to see it and a detailed set of build instructions and notes on installing the needed toolchain and deployment. (as a note, i'm currently working in flet.dev using Python which allowed me to get a small prototype up-and-running, but i'm still looking into self-hosting and doing something more complex)
quote · @匿名
Photoshop 1.0 was written mostly in Object Pascal with some 68000 assembly language; source code is available:https://computerhistory.org/blog/adobe-photoshop-source-code...

Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.