They don't make 'em like that any more: Borland Turbo Pascal 7

Original Article ↗ Hacker News Discussion ↗

Nostalgia and TP7’s Strengths

  • Many recall Turbo Pascal (TP) and its Windows version as formative tools.
  • Praised for speed, instant compile–run cycle, and tight resource usage compared with contemporary C toolchains.
  • Text-mode IDE is remembered as ahead of its time: dual-monitor debugging, integrated debugger, and highly effective context-sensitive help.
  • Built‑in help was used as a self-teaching system: read an entry, copy the example, modify until understood.

Pascal vs C and Language “Seriousness”

  • Some argue C offered no real advantages over TP for DOS/Windows, and that TP was unfairly treated as a “toy.”
  • Others found Pascal’s type safety made low-level tasks (e.g., image handling) harder, preferring C’s pointer flexibility.
  • There is criticism of C macros, string handling, and pointer syntax, contrasted with Pascal’s stronger typing and modern extensions (OO, generics).

TP’s Role and Industry Context

  • One view: the article overstates TP’s influence on Windows adoption; platform dominance came from OEM bundling and DOS compatibility, with C overwhelmingly dominant.
  • Another view: there’s a long-standing, harmful bias against approachable tools even when they deliver business value quickly.

AI Assistants and Coding Skills

  • Some fear AI tools will erode developers’ skills, comparing heavy reliance on them to cheating on tests.
  • Others counter that this is an unproven worry and analogous to past resistance to IDEs, GC, and higher-level languages.
  • Proposed future skillset: directing AI and validating its output rather than hand-writing all code.

Performance, Systems Knowledge, and Software Quality

  • Debate over whether understanding CPU/memory is broadly important.
  • One side claims ignorance leads to slow, bloated software; another blames time-to-market pressure, understaffing, and weak management more than lack of low-level knowledge.
  • Concrete example: fetching entire datasets over the network and filtering locally vs using proper SQL WHERE clauses.

Delphi, Free Pascal, and Ongoing Legacy

  • TP’s lineage is seen in Delphi, Free Pascal, Lazarus, and even C#/TypeScript design.
  • Some describe Delphi as “zombie-like” today due to corporate churn and brain drain; others note alternative Pascal dialects evolving faster.
  • Notable real-world deployments (e.g., complex control systems) still rely on Delphi, though code quality is suspected to be mixed and refactoring support criticized.

Productivity Then vs Now

  • Some miss offline, simpler environments: fewer distractions, smaller systems, paper docs, and consistent UI toolkits.
  • Others with experience in both eras argue pre-internet development was not more productive; today’s instant search and richer tools reduce tedious reverse-engineering.
  • A side discussion notes modern development often feels like endless “side quests” due to complex stacks and online troubleshooting.

Modern Bloat, Java, and Electron

  • The article’s jab at “bloated Java” is contested. Several argue modern Java is fast and reasonably efficient, especially compared to Electron apps.
  • Java is still criticized for startup time and memory footprint; Graal native images help but constrain reflection/dynamic loading.
  • Electron and modern browsers are cited as heavy RAM users; explanations include high-DPI graphics, multi-layer compositing, large syntax trees (DOM), and interactive layout requirements.

TUI IDEs and Discoverability

  • Some wonder why TP-style text UIs with menus and panes aren’t more common today, especially to aid discoverability for tools like gdb or neovim.
  • A few current TUI tools are mentioned, but lack TP-like menubars and integrated feel.