Why iPadOS Lacks a Calculator and Windows NT’s Formatting UI Has Stayed Unchanged for 30 Years

The article explains how product‑team decisions at Apple and Microsoft led to the absence of a built‑in calculator on iPadOS and a three‑decade‑old disk‑formatting UI in Windows NT, highlighting the lasting impact of temporary design choices.

Java Tech Enthusiast
Java Tech Enthusiast
Java Tech Enthusiast
Why iPadOS Lacks a Calculator and Windows NT’s Formatting UI Has Stayed Unchanged for 30 Years

iPadOS calculator omission

When iPadOS was first released, Apple engineers initially tried to copy the iPhone calculator app to the iPad. Steve Jobs judged that the UI would look awkward on the larger screen and instructed the product team either to redesign the calculator or to omit it. The team chose the latter, so iPadOS ships without a pre‑installed calculator and users must obtain one from the App Store.

Windows NT disk‑formatting UI legacy

In 1994, Microsoft engineer Dave W. Plummer—known for work on Windows Pinball, the Windows calculator, ZIP extraction, and product activation—was asked to create a user interface for the Disk Management tool in Windows NT. At that time Microsoft was porting large portions of Windows 95 code to the NT kernel, and the two operating systems used different file‑system formats (FAT, NTFS, etc.). Plummer listed every option a user might need when formatting a volume, including:

File‑system type (FAT, NTFS, etc.)

Volume label

Cluster (allocation unit) size

Compression flag

Encryption flag

Other advanced attributes

Using Visual C++ 2.0 and the resource editor, he built a dialog that presented those options in roughly the order a user would select them. The UI was intentionally simple and “good enough” for immediate use; Plummer acknowledged that it was not elegant, but it satisfied the functional requirement.

The resulting dialog has remained virtually unchanged for three decades and is still present in modern versions of Windows. An additional artifact of the original design is the arbitrary 32 GB limit on FAT volumes, a decision made during that early implementation that has persisted as a compatibility constraint.

Both cases illustrate how early product decisions—driven by aesthetic concerns at Apple and a “good enough” engineering mindset at Microsoft—can become long‑lasting defaults in software ecosystems.

Windows NT format UI screenshot
Windows NT format UI screenshot

Code example

往
期
推
荐
1、
佩服!无所不能的朝鲜黑客
2、
为了让更多新手快速体验 Java,多年来 Java 偷偷做了这个改进
3、
神经网络≠玄学,终于有人来讲数学原理了(文末送书)
4、
为什么国外JetBrains做 IDE 就可以养活自己,国内不行?区别在哪?
5、
七种分布式全局 ID 生成策略,你更爱哪种?
6、
Linus Torvalds:你的代码好恶心
点
分
享
点
收
藏
点
点
赞
点在看
Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

software historyUI designproduct decisionsWindows NTiPadOS
Java Tech Enthusiast
Written by

Java Tech Enthusiast

Sharing computer programming language knowledge, focusing on Java fundamentals, data structures, related tools, Spring Cloud, IntelliJ IDEA... Book giveaways, red‑packet rewards and other perks await!

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.