Why did Borland ignore the Macintosh market?

Original Article ↗ Hacker News Discussion ↗

Borland and the Macintosh Market

  • Several commenters note Borland did ship Mac products (e.g., Turbo Pascal for Mac in the mid‑80s) but exited relatively early.
  • Consensus: Borland prioritized DOS/Windows because that’s where the developer volume and corporate money were; the Mac market was “tiny” by comparison.
  • One view: as a relatively small company, Borland lacked resources to maintain full parallel toolchains for a niche platform, so only Pascal made it over.

Mac Market Size and Where Macs Were Used

  • Strong agreement that, through the 80s–90s, Macs were niche versus IBM‑compatibles:
    • In the US: common in education, desktop publishing, graphic design, multimedia, some CAD and science/medicine, but rare in general business and home use.
    • Outside the US (especially Europe/Eastern Europe): described as “nonexistent” or “zombie platform” outside creative and high‑end publishing houses.
  • Multiple timelines from schools: Apple II dominance → mixed Apple II/Mac/PC → PC labs only, with a small Mac presence for specialized use.

Developer Tools and Ecosystem

  • Many posts praise Borland’s tools (Turbo Pascal, Delphi, C++ Builder) as highly productive, especially for GUI/RAD and component-based development.
  • Early Borland was seen as hobbyist‑friendly and revolutionary on price ($49–99), undercutting “business‑class” compilers; later Borland moved up‑market and became expensive.
  • On the Mac side, THINK C/THINK Pascal and later CodeWarrior are widely remembered as the de facto standard, often preferred over Apple’s own MPW tools.
  • Mac OS and early apps had strong Pascal roots, but serious Mac software typically mixed Pascal or C with substantial assembly.

Why Borland Focused Elsewhere

  • Main reasons cited:
    • Much larger PC/Windows corporate developer base and upgrade revenue.
    • Mac’s limited, geographically uneven market and high hardware prices reducing volume.
    • Porting complexity: very different GUI APIs, reliance on assembly, and small payoff.
    • Internal issues: mergers (e.g., Ashton‑Tate), management missteps, and strategic drift into “enterprise” tooling reduced capacity to chase smaller platforms.

Apple’s Later Turnaround (Contextual)

  • Several commenters stress that Apple’s current strength is not indicative of its 80s–90s position; it nearly failed and was revived via NeXT/OS X, iMac, then iPod/iPhone.
  • This retrospective makes Borland’s lack of deep Mac investment appear rational given the information and economics at the time.