Slashdot Mirror

← Back to Stories (view on slashdot.org)

Mac OS X Panther 10.3 Reviewed

Posted by simoniker on from the like-it-like-it-love-it dept.

JigSaw writes "OSNews posted a (constructively) critical, but also favorable review of Mac OS X Panther 10.3. The article discusses the new features, what works great and what's still sour, and it also includes a plethora of screenshots." The review's conclusion suggests Panther is "...a worthy operating system, easy to use, easy to set up, easy to get pleased by it. It just works."

3 of 401 comments (clear)

  1. fix outstanding bugs? by SuperBanana · · Score: 3, Insightful

    Will it fix the massive bugs introduced into Bluetooth that have yet to be fixed?

    How about the problems with remote filesystems? Put your powerbook to sleep with any volume mounted, even read-only with no files open, and you'll basically have to restart(not even a umount -f will unmount the volume) because almost every app will show a spinning pizza of death.

    How about the bug that exists in most G4 powerbooks, where changing the volume level too quickly under "heavy load" causes the balance to shift?

    Every OS X release has been rather half-baked, although Apple is certainly doing better now than with 10.0 and 10.1...but it's still irritating that several bugs which affect me on a day to day basis will require dishing out another $100+, when I just bought a $3,000 laptop 2-3 months ago(my fourth powerbook, eighth mac, btw.)

    --
    Please help metamoderate.
  2. Re:Another 'I dont understand' by MarcQuadra · · Score: 4, Insightful

    I can still run HyprCard 1.4 (released in '87, I believe) on a brand-new G4. That says something. That's an app compiled for a DIFFERENT ARCHITECTURE goddammit!

    My dad runs ClarisWorks 3.1 on his G4, and that app is at LEAST a decade old.

    If developers write apps that aren't up to spec or link against stuff that Apple doesn't promise will be there next year I hardly see how it's Apple's fault.

    When the 68040 came out it crashed TONS of apps because developers were using self-modifying code that got mangled in the (then new to Mac) L1 cache. Apple had been telling folks for YEARS not to write code like that because it would bite them later, but some didn't listen.

    I think the responsibility lies MOSTLY with the application developers who want you to buy a new copy of their product whenever Apple releases a major update.

    --
    "Sometimes, I think Trent just needs a cup of hot chocolate and a blankie." -Tori Amos on Nine Inch Nails
  3. Bloatware? by 2nd+Post! · · Score: 3, Insightful

    Isn't it hard to accuse Apple of bloating the OS when every release gets *faster* and *more* efficient?

    Or the features are *more* effective?
    Like better Samba, and thus Windows, networking? Or better printing? Remote volume protocols? Etc?

    --

    GPL Deconstructed