Re:Introducing Safari Technology Preview
by crabasa on Thursday March 31, 2016 @06:00PM
(#11400908)
> First, Apple sells hardware
If you think that consumers are purchasing iPhones so that they can rock out on Safari and Mail, you are mistaken. A year ago over the App Store hit 100B cumulative app downloads:
Native apps drive hardware purchase decisions for consumers. That's the lesson of Windows Phone.
> Safari's engine is what Chrome has been based on, and for most of its life it has been one and the same codebase.
You misunderstand how a browser is constructed. Browsers are much more than just a rendering engine like Webkit. Chrome and Safari have different JavaScript engines, support different web standards (no WebRTC for Safari!) and are architected in completely different ways. You might find this a helpful place to start:
If you think that consumers are purchasing iPhones so that they can rock out on Safari and Mail, you are mistaken. A year ago over the App Store hit 100B cumulative app downloads:
http://www.statista.com/graphic/1/263794/number-of-downloads...
Native apps drive hardware purchase decisions for consumers. That's the lesson of Windows Phone.
> Safari's engine is what Chrome has been based on, and for most of its life it has been one and the same codebase.
You misunderstand how a browser is constructed. Browsers are much more than just a rendering engine like Webkit. Chrome and Safari have different JavaScript engines, support different web standards (no WebRTC for Safari!) and are architected in completely different ways. You might find this a helpful place to start:
http://arstechnica.com/information-technology/2013/04/does-w...