Apple's Safari browser is already 13 years old!

Apple's Safari browser is already 13 years old!

In 2003, Apple released Safari, the "fastest web browser ever built", for the Mac. Four years later, it brought a new mobile browser experience to the iPhone. The emergence of Safari seemed to lag behind the development of HTML. The years of war between Microsoft and Netscape/Mozilla gave rise to corresponding browser engines and imposed certain restrictions on the emergence of new competitors.

[[161702]]

Jobs said: "We've built the first all-new browser in many years, bringing innovation back to the field."

Return to open web standards

Launching its own browser has won Apple important influence with users, increased the interest of other browser manufacturers in providing support for the Mac platform, and given Apple greater control over the direction of Web standards.

Apple not only launched its own browser application, but also developed a unique WebCore browser engine (based on a branch of the existing KHTML open source project) to compete with Microsoft's Trident and Mozilla's Gecko.

The company is committed to opening up complete web standards, rather than the proprietary web extensions favored by Microsoft, to allow developers to be more consistent and fair. In 2008, WebKit became the first browser engine to fully pass the Acid3 rendering test.

Owning this key technology allowed Apple to adopt HTML5 as an open option ahead of the curve (web apps and videos require proprietary middleware such as Adobe Flash or Microsoft Silverlight).

One of the core features of HTML5 is Canvas. Apple contributed this patented technology for free to accelerate the development of the open network, which obviously also cost Microsoft and Adobe a certain price.

[[161703]]

Safari on iPhone (2007).

A large open source project

Safari's WebCore and JavaScript core libraries (both derived from KHTML) have always been open source. In 2005, Apple announced that it would open the entire browser implementation to the community. The resulting WebKit allowed other manufacturers to quickly launch their browsers.

Nokia made an effort and brought WebKit to its mobile platform, while Google launched the Chrome browser for Windows platform, taking precedence over Mozilla's IE replacement.

Apple initially maintained a port of Safari for Windows PCs, but eventually discontinued the project as Google and other developers took over the maintenance of WebKit on the Windows platform.

In 2007, Apple launched the Safari browser for the first generation iPhone, which used the same WebKit engine and supported multi-touch interaction.

Jobs said: "We wanted to have the best web browser on a phone, so we picked the best browser in the world, Safari. We put it on the iPhone - it's the first fully usable browser on a phone."

Since Apple subsequently brought WebKit to the Android platform, the browser engine led by Apple soon had an overwhelming competitive advantage over the PC desktop platform and dominated the mobile browser market.

<<:  New Wi-Fi technology is available that's better suited for smart homes

>>:  11 Predictions for Web Design Trends in 2016

Recommend

iOS 15 has 7 new features that older iPhones can't use

However, some of the best new features of iOS 15 ...

How to find accurate drainage methods?

There is a cruel fact: the online traffic dividen...

Reverse time and rejuvenate! Is the Turritopsis immortal?

References: 1. "On the list of longevity ani...

The first choice of Feng Shui spiritual objects for entrance examinations

June is approaching and the feeling of summer hea...

Do you know the real reason why lithium battery performance deteriorates?

Lithium-ion batteries are now widely used in mobi...

Is soup a kind of "junk food"? How can we drink soup scientifically?

Soup is a nutritious and nourishing dish on many ...

Dynamic zero-clearing & social zero-clearing, what is the difference?

Mixed Knowledge Specially designed to cure confus...

How to make the "user retention analysis model" more useful

Operations personnel often use user retention ana...