Technology
Java's Cover
paulgraham.com
Technology
6 min read → 55 sec
An essay uses hacker intuition to judge Java by its outward signals, arguing that hype, committee design, corporate motives, and bureaucratic appeal often predict weak technology.
Java looked unlikely to succeed because its outward signals matched past bad technologies
Hackers must judge by signs, there are too many languages to learn them all
2 / 15
Java's strongest warning signs were hype, committee design, corporate control, and appeal to bureaucracies
3 / 15
Real standards do not need heavy promotion
C, Unix, and HTML showed this
4 / 15
Technologies pushed for ulterior motives often serve strategy more than technical merit
Java served Sun against Microsoft
5 / 15
Java was designed to stay easy for C programmers, not to push language design forward
6 / 15
Strong languages inspire love, but Java lacked the devotion seen around C, Perl, Python, Smalltalk, and Lisp
7 / 15
Many smart programmers used Java from pressure by funders, customers, or management, not free choice
8 / 15
Good programming languages usually come from small groups
Committee-designed languages have a bad record
9 / 15
Java appeared bureaucratic, with many protocols instead of getting out of the programmer's way
10 / 15
Sun presented Java as grassroots and open-source, but it remained controlled by a giant company
11 / 15
Large organizations prefer languages that limit damage by mediocre teams, while hackers want power
12 / 15
The people most captivated by Java were suits, big-company programmers, and job-seeking undergrads, not admired programmers
13 / 15
Languages built for hackers and their creators usually win, while languages built for large organizations usually lose
14 / 15
15 / 15
Carouse
Turn any article, video, or podcast into a carousel you can browse in 30 seconds.