Java's Critical Pre-Stage Fix
Java's success hinged on a three-day fix before its big debut.
1Java's Humble Beginnings
Java started as a failed attempt in the set-top box market and required a major rewrite before its big conference debut. Today, Java is widely used in large enterprise applications.
2Sun Microsystems' Decision
In 1994, Sun Microsystems considered abandoning the Java project. Tim Lindholm was hired to fix Java's virtual machine runtime.
3FirstPerson and Oak
Lindholm started working at Sun Microsystems' experimental subsidiary, FirstPerson. A language and runtime called Oak was developed.
4Pivot to the Web
The Oak project shifted focus to the then-nascent web. An engineer working on the Mosaic browser suggested the World Wide Web as Oak's new target.
5The Birth of Java
Oak was renamed Java in early 1995. Web developers were discovering the limits of HTML, and Java quickly gained popularity.
6Threading Model Issue
Java's threading model was fundamentally broken. System interrupts were issued while the SPARC processor was executing an instruction, causing unrecoverable errors.
7Critical Fix
Lindholm solved the issue with Java's threading model, ensuring the system worked correctly. This fix was critical for Java's success.
8SunWorld Conference
Java was introduced at the 1995 SunWorld conference, the precursor to JavaOne. This conference marked Java's major success.
9Java's Legacy
Java is still widely used in large enterprise applications today. The critical pre-stage fix laid the foundation for Java's success.
Original article: www.theregister.com - Articles — Java'nın Sahne Öncesi Kritik Düzeltmesi