General Apple needs to speed up Safari development and updates

Discussion in 'iOS 9' started by Michael Goff, Jan 3, 2016.

  1. Michael Goff Suspended

    Michael Goff

    Jul 5, 2012
    Take a look at for a second. They're moving fast, they're changing things up at an insane speed at times. On a Mac, just throw Nightly on there and see just how much better it is to be able to run the latest build. Weeks and weeks pass by with no update to be seen on iOS, unlike OS X where you can just run the Nighly like I said.

    I'd like it Safari was updated on a monthly basis, and likely not tied to a version update, but that's not likely to happen.
  2. Elisha macrumors 6502a


    Nov 21, 2006
    How would we benefit? Any new useful features?
  3. Michael Goff thread starter Suspended

    Michael Goff

    Jul 5, 2012
    Excellent question!

    Let me give you a link to something WebKit added last month.

    That's just one example. I also stated this because WebKit is one very important thing. It dictates how fast Safari is, how it renders web pages, and how everything else does as well. We would benefit by having a smoother experience in just about everything that uses any sort of browser (Facebook, Twitter ... Whatever else you use).

    Also, I would argue that the browser is one of the most used applications these days.
  4. Rhonindk macrumors 68040


    Oct 3, 2014
    watching the birth of the Dem WTH Party
    Safari in iOS can use all the help it can beg, borrow, or leverage. Systematic updates like that would be a serious nice to have. ;)
  5. Michael Goff thread starter Suspended

    Michael Goff

    Jul 5, 2012
    They don't even have to do a lot. Just put the newest version of WebKit in there about once a month.
  6. MikhailT macrumors 601

    Nov 12, 2007
    I've been using Webkit Nightly for several years on OS X, it often goes through long period of instabilities. There was a period of nightly builds that crashed upon opening for me until it was fixed 2 full months later. The webkit devs focuses on adding brand new experimental features right away and then spend several weeks to clean up after it. So, no, don't compare Webkit Nightly against stable Safari that rarely has issues.

    Apple doesn't rush this because it risks the chance of crashing every single app that relies on the same Safari rendering engine. What Apple could do is:

    1. Split between Safari and webkit framework, the stable webkit framework remains the same like Safari on iOS right now for all iOS apps to use. Release a separate Safari app
    2. The separate Safari app should be in the App Store, ready to be updated any time Apple wants but there needs to be a way to revert easily in case things go wrong.

    Considering the amount of QA issues they've been having lately, I rather they focus on stability and not rush through things just because Webkit happens to be slightly faster.
  7. Michael Goff thread starter Suspended

    Michael Goff

    Jul 5, 2012
    In the year or more I used OS X, I used WebKit Nightly as my main browser and only had a handful of crashes.

Share This Page

6 January 3, 2016