3 ms·

I think what you’re forgetting is that a lot of people thought the iPhone would fail because it didn’t have a keyboard, and at the time smartphones were going m

• sho_hn 3y ago
  > Apple committed to their own approach. That is exactly what I'm arguing. > This is just bollocks. WebKit was forked from our KHTML, even if it definitely had significantly deviated by 2007, and particularly UX-wise Mobile Safari definitely had many fantastic ideas. I didn't mean to be dismissive of it, it was more to point out that they also don't create in a vacuum, even their successes.
  • SllX 3y ago
    On the subject of WebKit, what you said is bollocks for two reasons. 1. You are conflating the rendering engine with the browser. Safari on Mac and iPhone uses WebKit as a core technology—really the preeminent core technology—but they are not WebKit and WebKit is not Safari on either platform. 2. Similarly, WebKit is not KHTML and KJS. WebCore and JavaScriptCore are forked from KHTML and KJS—and Apple did not and to my knowledge has never downplayed that nor denied it—but a fork of a project that sees significant new development work becomes a new project and takes on an identity of its own. By the time the iPhone was released, WebKit had been in development inside Apple for 6 years; and public knowledge since its announcement and Safari’s public beta for 4.5 years. KHTML and KJS deserve and I believe actually receive their due respect, but it is wrong to say Apple did not develop their own web browsers.
    • sho_hn 3y ago
      You know what, I'll go ahead and agree you are right. These are well-argued points, thanks! Let's say I was a bit hyperbolic there. That said--in support of "not in a vacuum", and against myth-making.
      • SllX 3y ago
        > That said--in support of "not in a vacuum", and against myth-making. Apple knows what they owe to open source software: https://opensource.apple.com/releases/ https://opensource.apple.com/releases/