Slashdot Mirror


Apple Releases - Doing Less, Faster, Is Better?

gralem asks: "There is some frustration in the OS X community about Apple's release of updates. Apple has basically been releasing updates to OS X every 2-3 weeks. The updates aren't ground-breaking. They don't add all the features the users expect (CD burning ended up being only from within iTunes, instead of system-wide). They also don't fix all of the known bugs of the system. But I think Apple is doing the right thing by keeping lots of updates flowing. I haven't seen anything 'broken' by the updates, and each time the system runs faster and smoother. Does it matter that OS X is such 'new technology' as far as Apple is concerned, as opposed to W2K and Microsoft's update schedule?" Keeping the updates flowing is one thing, but forcing users to update every 2-3 weeks? That might be a bit too much. I don't know much about OS X, but if the upgrades system can be configured to the users taste, and said configuration done in a user-friendly way, then maybe monthly updates might not be a bad thing ...

"I can't remember how long Microsoft took to release W2K service pack 1, but I know there is still no service pack 2. Even Linux kernel (stable) releases are not commonly in the 2-3 week range. So is Apple doing the right thing to get SOMETHING out there? Or are they disenfranchising their user base by coming out with too little too fast?"

An embellishment to the above: as long as there are tools to tailor the upgrades of a system to the user's specific desires, who cares how often providers update their own packages? Such an updater would check the upstream package catalog and apply multiple criterion on each updated package which would determine if that update is applied. I would suggest that the two basic criterion one would apply for updates would be severity and duration. Couple this with forced inclusion and exclusion lists and an administrator would be able to configure the system to apply only those packages that they need upgraded at the appropriate time, and quite possibly without the need of administrator intervention (depending, of course, on how much the administrator trusts the upstream).

With such a system in place, who cares how often Apple, Red Hat, Debian, Microsoft or <insert vendor here> updates their software packages? You'll have what you need, as often as you need it.

How difficult would it be to adapt the existing updating systems to serve this purpose? Is someone close to putting this into place, now?

13 of 173 comments (clear)

  1. Re:Faster is better, but... by garcia · · Score: 4

    seems like it is bettr for it to be brken then, who teh hell would want it beeping all teh time?

    seriously, I don't considering the spell checker not beeping as something bring "broken".

  2. Opinion from a MacOS X user by HeghmoH · · Score: 5

    I use MacOS X as my mostly main OS these days. I still shuttle into 9 from time to time, but X is starting to replace it for me. 10.0.0 was not good enough to be my main OS. On my G3/300 (160M RAM), X ran too slowly. By 10.0.3, it's reasonably snappy. It's not great, but it's usable. I'm really happy with their constant updates. They aren't profound, but the OS gets faster with every one, and little things keep getting fixed. I'd rather have it this way than one big update every six months. Updating is easy. I start the update, then I go and do something else on the computer, and a while later, I hit restart. Boom, updated. If you don't want to update, nothing forces you to. If you do want to update, it's simple.

    --
    Mod down posts with a "Free Mac Mini/iPod" sig, they're spam!
  3. Updates on YOUR schedule by Dredd13 · · Score: 5
    I don't know much about OS X, but if the upgrades system can be configured to the users taste, and said configuration done in a user-friendly way, then maybe monthly updates might not be a bad thing ...

    Updates can be configured to happen on whatever schedule the user chooses... daily, weekly, monthly, manually, whenever.

    Most of the present day OSX users are power-users, though, so they're either doing it manually when they find out about updates, or they've got it set to check for updates daily.

    1. Re:Updates on YOUR schedule by iso · · Score: 4

      it also seems that updates roll in earlier changes you may have missed. for instance if if you didn't install 10.0.2, 10.0.3 was 15Mb. if you did install 10.0.2 then 10.0.3 was only 500Kb.

      the updates aren't extremely fine-grained (ie. all "system software" always comes in one update and there's no way to pick-and-choose the bits) but some things are separated, like the updated Epson Printer Drivers, so you can opt to not installs those parts if you don't need them. all updates are optional as well, and nothing is done 100% automatically without the user at the very least ok-ing the components to be installed.

      it's not perfect yet, but all in all i'd say that it's a great system they've got going. as for the frequency of the updates i don't see this "frustration" talked about in the article. in fact the vast majority of Mac users i've talked to love the frequent updates.

      really though it sounds like these people bitching about the system are those who have never actually tried it themselves!

      - j

  4. software updates. painless. by option8 · · Score: 5

    "Keeping the updates flowing is one thing, but forcing users to update every 2-3 weeks? That might
    be a bit too much. I don't know much about OS X, but if the upgrades system can be configured to the users taste, and said configuration done in a user-friendly way, then maybe monthly updates might not be a bad thing ... "


    the software updates in OS X (and in 9.x as well) are done automatically by the system, tho the default configuration is to check the software updates servers periodically in the background, then ask the user which updates that are available he wants to download and install

    the process is amazingly apple-like: painless and transparent, at most requiring a reboot (with system-level component updates. things like itunes are finished when the download uncompresses)

    it's also user configurable to go ahead and get every update as it appears, or none at all - requiring the user to click a button to manually check for updates.

    this is the kind of thing that a lot of systems are aiming for, including, among others, Red Hat's update agent, which i think falls farthest from the mark. not to criticize RH, but it's the only other example i have on my desk at the moment with which to compare. i know the W2k update agent works well anecdotally, but its little balloon popups are really annoying...

    my point? did i have one?

  5. Microsoft update release schedules by macpeep · · Score: 4

    I'm also not sure when SP1 was released but SP2 *just* appeared today so the article intro is slightly incorrect. Also, remember that Microsoft do provide other updates than just service packs - that's what the whole "Windows Update" thing is for.

  6. Non-proprietary formats? by yerricde · · Score: 4

    non-proprietry formats such as MP3

    MP3 is NOT non-proprietary; it's patented. The token non-proprietary free audio standard isn't MP3; it's Ogg Vorbis.

    --
    Will I retire or break 10K?
  7. I'm sick of these double standards by kinnunen · · Score: 5
    We* use distributions that come with literally thousands of programs. We complain when Microsoft adds a couple to their new OS/Distro.

    We call Windows bloated at 400MB, but when someone points out that distro X takes 7 CD's, we defend that distro

    We're happy to use software that updates several times a month, some update daily. When Apple releases two patches in one month, we say their forcing people to update against their will or something.

    *Yes, I know this doesn't apply to every single reader.

    --

    1. Re:I'm sick of these double standards by squiggleslash · · Score: 4
      We* use distributions that come with literally thousands of programs. We complain when Microsoft adds a couple to their new OS/Distro.
      Microsoft doesn't do "distros", it does OSes, and it forces users who buy its OS to buy (pay for), install, and run additional applications that having nothing to do with running an operating system. Examples include Internet Explorer, a web browser designed to prevent users from looking at third party products, primarily Netscape, Outlook Express, an email client, designed to prevent users from looking at many other third party, and standards compliant, email packages, MSN Messenger, an IM client designed to prevent users from using AOL IM, Windows Media Player, a streaming media player, designed to prevent users from looking at RealPlayer, or worse, non-proprietry formats such as MP3, and many others.

      The specific intent of Microsoft's 'add-ons' is to avoid choice. By forcing the users to install this software, it becomes inefficient and potentially destructive to the stability of the system, to install third party competitors. And in all of these cases, the third party products are seen as threats, either because they encourage reliance on companies outside of MS's control, such as Real and AOL, or because they encourage use of commodity protocols (see the Halloween documents).

      How is this different from the distributions that come with literally thousands of programs? Answer: Other than, possibly, mailx, which is too low level to count, I haven't come across a single distro that forces users to install equivalents of any of the software above. And if they did, they would almost certainly be installing software that is under the control of third parties, and usually they offer choices of different ways of doing similar things.

      The latest RedHat gives you at least 4 different choices of graphical web browser. You can choose between a list of email clients as long as your arm. You can use IRC and ICQ, commodity protocols based IM systems if you want to - most distros have them all, supported through many choices of client. And if you choose not to, download AIM or Y! Messenger - they wont be forced to share memory with other IM packages you never chose to install. Want streaming media? If mpg123, or kmpg, or XMMS, or XMovie, or any of the other tools doesn't quite cut it, you don't have to install them anyway and keep them in memory when you download RealPlayer 8.

      In short, there's no comparison. Microsoft is forcing you to install software you don't necessarily want, in order to cripple the competition.

      We call Windows bloated at 400MB, but when someone points out that distro X takes 7 CD's, we defend that distro
      Mr Apple? Meet Mrs Orange. Mrs Orange, Mr Apple.

      We call Windows bloated because it takes up several hundred megs for a usable install for the latest versions. With XP, incidentally, that figure rockets to 1.5G. We say that Linux isn't because a basic, usable, Linux system can be squeezed into half of that, and that's including a whole lot Microsoft wont give you. Like a C compiler, for installing third party Unix applications.

      Microsoft Windows would take up considerably more than 7 CDs if someone, like the SUSE people, tried to track down every single distributable application in the world that's available for Windows, and put it in the default install set for Windows. Fortunately for the world, nobody's been idiot enough to do that.

      We're happy to use software that updates several times a month, some update daily. When Apple releases two patches in one month, we say their forcing people to update against their will or something.
      Actually, scroll to the top and you'll find the question is the exact opposite, to whit:
      An embellishment to the above: as long as there are tools to tailor the upgrades of a system to the user's specific desires, who cares how often providers update their own packages? Such an updater would check the upstream package catalog and apply multiple criterion on each updated package which would determine if that update is applied. {...} How difficult would it be to adapt the existing updating systems to serve this purpose? Is someone close to putting this into place, now?
      The question is is there a way to make it easier for regular updates, such as the ones Mac OS X users are suffering, to occur without as much inconvenience as they cause now?
      --
      --
      You are not alone. This is not normal. None of this is normal.
  8. This is the right thing to do... by xFoz · · Score: 5

    If the goal is to ship OS X with every machine Apple sells starting this summer, now is the time to get things straight. If that means "updates on Friday" then send them. Do it before it's flung unto the masses.

    Personally, I'd rather have a bunch of close together updates then the monolithic updates that non-OS vendors force these days. For example the last releases of Photoshop and Illustrator had a disastrous effect on my business. The artists couldn't deal with the sweeping changes made by Adobe.

    Finally, I imagine that it's easier for engineering and QA get their jobs done by shipping micro updates. Especially since there are so many different parts of this OS.

  9. Re:Nobody is forcing you to upgrade by baptiste · · Score: 4
    But if you can schedule when the upgrades occur - who cares - becuase for everyone saying I only need them monthly there will at times be IT guys screaming for the patch yesterday.

    --

  10. Updates by macgorilla · · Score: 4

    I like the fact that Apple is releasing upbeats on a regular basis; it shows they are listening to feedback/ You don't have to update your system when the updates are posted; you can install them at your lesiure, which is cool. Mac OS X is a very a ambitious operating system and frequent tweaks are not unexpected. The original Mac OS was tweaked continiously for 17 years.

  11. In many situations, it's never too often! by melquiades · · Score: 5
    Think of the massive media panic that follows on the heels of ever newly discovered Virus of the Apocalypse. Millions of people are out there wondering where to download the update for Outlook and how to install it...in fact, many of the novices are wondering whether they are even using Outlook.... A scheme like Apple's, done right, could stop a lot of these viruses in their tracks.

    If I can get a painless, nearly-transparent bug or security fix the moment it's ready for prime time just by clicking "update", I'm a happy camper. I'm puzzled by this assertion that every two weeks is too much.

    An update scheme such as OS X's should meet the following criteria:
    1. No configuration or install necessary to use auto-update
    2. User can customize the auto-update schedule, make it manual, or simply disable it completely
    3. There is a clear explanation of when an update is available, which software it affects, and what features it adds/improves/fixes
    4. User has a choice about whether to download/install an update when it's available
    5. Updates are painlessly self-installing
    6. Updates are well-tested and don't break existing software

    I'm using OS X as my primary OS, and so far, Apple has done an absolutely outstanding job with 1, 2, 4, 5, and 6. Only #3 is week -- the only explanation you see when an update is available is "OS X 10.0.3". You have to install the update then try to divine what's changed. If Apple fixes this problem, they'll have a killer mechanism that Linux distros would do well to study.