Products
Features
YouTube Video Summarizer
Summarize YouTube videos
Web & PDF Highlighter
Highlight web pages & PDFs
Chat with PDF
Ask any PDF questions with AI
Ask AI Clone
Chat with your highlights & memories
Audio Transcriber
Transcribe audio files to text
Glasp Reader
Read and highlight articles
Kindle Highlight Export
Export your Kindle highlights
Idea Hatch
Hatch ideas from your highlights
Integrations
Obsidian Plugin
Notion Integration
Pocket Integration
Instapaper Integration
Medium Integration
Readwise Integration
Snipd Integration
Hypothesis Integration
Apps & Extensions
Chrome Extension
Safari Extension
Edge Add-ons
Firefox Add-ons
iOS App
Android App
Discover
Discover
Ideas
Discover new ideas and insights
Articles
Curated articles and insights
Books
Book recommendations by great minds
Posts
Essays and notes from readers
Quotes
Inspiring quotes collection
Videos
Curated videos and summaries
Explore Glasp
Glasp Story
How we grew from 0 to 3 million users
Glasp Newsletter
Weekly insights and updates
Glasp Talk
Interview series with great minds
Glasp Blog
Latest news and articles
Glasp Use Cases
Learn how others use Glasp
Build & Support
Glasp API
Access Glasp's API for developers
MCP Connector
Connect Glasp to Claude & ChatGPT
Community
Glasp Reddit Community
Students
Student discount and benefits
FAQs
Frequently Asked Questions
AboutPricing
DashboardLog inSign up

Why Did IBM Stick with EBCDIC Over ASCII?

May 8, 2018
by
Computerphile
YouTube video player
Why Did IBM Stick with EBCDIC Over ASCII?

TL;DR

IBM opted to use their proprietary EBCDIC character code rather than adopt ASCII to maintain market competitiveness and compatibility with existing systems. This decision had the unintended effect of locking users into IBM hardware, complicating interactions with ASCII-based technologies. Ultimately, IBM did move to ASCII for its UNIX servers, but the legacy of EBCDIC's limitations persisted.

Transcript

IBM was thinking of launching the 360 series computers that will be byte addressable in the early sixties there was a well-known committee that decided the character codes we used today the ASCII committing American Standard Code for information interchange early sixties IBM approved variet they even had delegates on the board so then the embarrass... Read More

Key Insights

  • 👨‍💻 IBM's decision to continue using their own character codes had both commercial and technical motivations.
  • 💋 The compatibility issues caused by using AB stick instead of ASCII locked users into using IBM machinery.
  • 🛟 IBM eventually adopted ASCII for their mainframes, particularly with the introduction of IBM Discovery Unix servers.
  • 💋 The cumbersome transition from AB stick to ASCII caused difficulties with character mapping and interconversion.

Install to Summarize YouTube Videos and Get Transcripts

Explore YouTube Video Summarizer or Get YouTube Transcript Extractor

Questions & Answers

Q: Why did IBM decide to continue using their own character codes instead of adopting ASCII?

IBM chose to use AB stick for commercial reasons, as transitioning to ASCII could have led to compatibility issues and potentially lost market share to competitors.

Q: What were the implications of IBM's decision to continue using AB stick?

The decision to use AB stick created compatibility issues with ASCII-based systems and locked users into using IBM machinery. It also hindered the adoption of standard character codes.

Q: Did IBM eventually transition to ASCII for their mainframes?

Yes, IBM eventually adopted ASCII, especially when they introduced IBM Discovery Unix servers. However, it took some time for them to fully embrace ASCII across their systems.

Q: How many versions of AB stick did IBM have?

IBM had six versions of AB stick, each with its own mapping of characters and code positions. This caused further compatibility challenges when trying to interconvert characters between AB stick and ASCII.

Summary & Key Takeaways

  • In the early 1960s, IBM planned to launch the 360 series computers, which would be byte addressable. However, their existing character codes based on BCD posed compatibility issues.

  • IBM chose to continue using their own character codes known as AB stick due to commercial considerations, as transitioning to ASCII could potentially lose them a significant market share.

  • This decision had unintended consequences, as it locked users into using IBM machinery and caused compatibility issues with ASCII-based systems.

  • Eventually, IBM did adopt ASCII for their mainframes, particularly when they introduced IBM Discovery Unix servers.


Read in Other Languages (beta)

English

Share This Summary 📚

Summarize YouTube Videos and Get Video Transcripts with 1-Click

Download browser extensions on:

Try YouTube Summary with ChatGPT & Claude or YouTube Transcript Generator

Explore More Summaries from Computerphile 📚

What Was the Tiltman Break in Codebreaking? thumbnail
What Was the Tiltman Break in Codebreaking?
Computerphile
Network Address Translation - Computerphile thumbnail
Network Address Translation - Computerphile
Computerphile
Error Detection and Flipping the Bits - Computerphile thumbnail
Error Detection and Flipping the Bits - Computerphile
Computerphile
What Makes Time Zones So Complicated? thumbnail
What Makes Time Zones So Complicated?
Computerphile
Mainframes and the Unix Revolution - Computerphile thumbnail
Mainframes and the Unix Revolution - Computerphile
Computerphile
What Is Superfish and How It Enables Attacks? thumbnail
What Is Superfish and How It Enables Attacks?
Computerphile

Summarize YouTube Videos and Get Video Transcripts with 1-Click

Download browser extensions on:

Try YouTube Summary with ChatGPT & Claude or YouTube Transcript Generator

Apps & Extensions

  • Chrome Extension
  • Safari Extension
  • Edge Add-ons
  • Firefox Add-ons
  • iOS App
  • Android App

Key Features

  • YouTube Video Summarizer
  • Web & PDF Summarizer
  • Web & PDF Highlighter
  • Chat with PDF
  • Ask AI Clone
  • Audio Transcriber
  • Glasp Reader
  • Kindle Highlight Export
  • Idea Hatch

Integrations

  • Obsidian Plugin
  • Notion Integration
  • Pocket Integration
  • Instapaper Integration
  • Medium Integration
  • Readwise Integration
  • Snipd Integration
  • Hypothesis Integration

More Features

  • APIs
  • MCP Connector
  • Blog & Post
  • Embed Links
  • Image Highlight
  • Personality Test
  • Quote Shots
  • Open Graph Checker

Company

  • About us
  • Our Story
  • Blog
  • Community
  • FAQs
  • Job Board
  • Newsletter
  • Pricing
Terms

•

Privacy

•

Guidelines

© 2026 Glasp Inc. All rights reserved.