AI summary by TwinMind
Why You Can't Name A File CON In Windows
Tom Scott
8m 3s
Windows File Naming Restrictions
- Cannot name files/folders "con" in Windows 10
- Also restricted: com0-com9, lpt0-lpt9, prn, aux, nul
- Applies to all file types (folders, .txt, .jpg, etc.)
- "Con" is legitimate name variant (Cornelius, Conrad, Connor, Konstantinos)
Historical Origin - MS-DOS Device Files
- Restriction dates back to MS-DOS (1980s)
- Device files: clever system for program-hardware interface
- Programs could treat devices like files instead of learning each device's protocol
- Device drivers handled hardware communication complexity
- Examples:
- CON = console (keyboard/screen)
- LPT1 = parallel port #1 (printer connection)
- COM ports = serial communication
- Command line usage:
dir > lpt1would print directory listing - Early MS-DOS had no directories - everything in single file heap
- Device names had to be globally reserved
Technical Implementation
- Programs reused existing file read/write code
- Device driver intercepted calls to reserved names
- Output redirected to appropriate hardware instead of disk
- New hardware required only new drivers, not program rewrites
- File extensions stored differently in early systems
Microsoft's Backwards Compatibility Philosophy
- Direct lineage: MS-DOS → Windows 3.1 → Windows 10
- Can still find Windows 3.1 file dialog in Windows 10
- Few modern PCs have parallel ports, but Microsoft maintains support
- Policy: shouldn't need new printer for new computer
Backwards Compatibility Examples & Challenges
Excel Leap Year Bug
- Excel still thinks Feb 29, 1900 existed (it didn't)
- 1900 not leap year (divisible by 100, not 400)
- Bug copied from Lotus 1-2-3 competitor in 1987
- Maintained for 30+ years in formal specifications
- Fear: fixing might break critical spreadsheets worldwide
Gaming Industry Contrast
- Video games: limited backwards compatibility
- PlayStation 1 games don't work on PlayStation 4
- Emulation possible but economically questionable
- Remastered versions sold instead
- Must emulate bugs along with features
Microsoft's Approach
- Can open 30-year-old Word documents today
- Companies stick with Windows for workflow continuity
- Some users still need legacy software/hardware
- Original manufacturers often defunct
Industry Balance: Apple vs Microsoft
- Apple: frequently drops old program support
- New macOS versions break old applications
- Hardware changes (headphone jack removal)
- Different philosophy on innovation vs compatibility
Design Philosophy
- Users want "mixture of novelty and familiarity"
- Too much change: breaks workflow, users leave
- Too little change: users get bored, move on
- Backwards compatibility helps find balance
COVID-19 Context
- Video normally filmed at Center for Computing History, Cambridge
- April 2020 recording constraints
- Green screen substitute maintains visual consistency
- Metaphor for backwards compatibility preserving functionality
