Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Utilities (Apple) Businesses Software Apple

No More Mac Tweaking? 792

netphilter writes "Apple is trying to "close the operating system to tweakers" according to this story on Wired. The addition of the BSD kernel and the command line left me thinking that they were trying to open the OS a bit more to tweakers, not close it. I'm not a Mac user, but I have been thinking about trying out OS X. However, if Apple is trying to CLOSE the OS (contrary to the impression that I had) then I'm not going to waste my time." Jamie adds: life may be harder for them, I guess, but many developers are still tweaking Mac OS X.
This discussion has been archived. No new comments can be posted.

No More Mac Tweaking?

Comments Filter:
  • Good (Score:2, Funny)

    by Anonymous Coward
    I closed my apartment to tweakers, and suddenly my stuff stopped disappearing!
  • by coene ( 554338 ) on Tuesday October 01, 2002 @02:04PM (#4368380)
    You've seen the commercials and all the marketing dollars they are putting into this campaign...

    Apple wants people who are looking for a computer that just plain works. They are going after the "as long as it works I dont care about X, Y, or Z" crowd, which is (for the most part) completely opposite the Slashdot crowd.

    As always, the real tweakers will find a way to do what they want with their computer. Its not a big deal...
    • by dconder ( 79190 ) on Tuesday October 01, 2002 @02:10PM (#4368427) Homepage
      Yes, but this is the same company looking to make itself accessable to artist, etc, who want to display their creativity. Now they are going to lock it down so that everyone's Apple looks the same?
      A lot of the standard computer interfaces -- hierarchical menus, contextual menus, even Aqua itself -- were dreamed up by people working in bedrooms or back offices, now they want to curtail this?
      • by foobar104 ( 206452 ) on Tuesday October 01, 2002 @02:19PM (#4368496) Journal
        Yes, but this is the same company looking to make itself accessable to artist, etc, who want to display their creativity. Now they are going to lock it down so that everyone's Apple looks the same?

        I know a lot of artists; I sort of move in a circle of friends who are all artists of one kind or another. Know how many of them like tweaking their Macs? None.

        See, to the creative person, a Mac is just a tool. It's like a paintbrush or a typewriter or a videotape deck. Nobody wastes time and energy rearranging the buttons on their tape deck, or changing the way their pencil works. It's a tool, and you use it so you can get the real art done.

        The tool should be effective, simple, and reliable, in that order.
        • by Anonvmous Coward ( 589068 ) on Tuesday October 01, 2002 @02:27PM (#4368575)
          "I know a lot of artists; I sort of move in a circle of friends who are all artists of one kind or another. Know how many of them like tweaking their Macs? None."

          I'm not sure I agree with that. I had an artist friend that was always monopolizing the Mac in art class. Much to our dismay, he set the system font to a font he created by hand. Unfortunately, I don't know many people with Macs so I can't really comment on more than that one guy. [i]"One example doesn't reflect the whole world"[/i]. The thing is, his art was his passion. He found an avenue to express himself on that machine and he did. I know quite a few non-Mac artists that have done all kinds of fun graphic stuff to their computers. (i.e. customized Winamp Skins, etc...)

          Am I right and you're wrong? No, I'm not saying that. In composing this post I realized that there may be a difference between your artists and mine: Are your Mac friends using Macs where they work? If so, I'd say there's a big difference.

          The computer you use for work benefits from not being messed with too much. You never know when you'll get a new computer and have to start over. You never know when somebody else will want to use your computer. And you [i]certainly[/i] never know when a tweak could corrupt and endanger your machine.

          Apple may have a point. If they're smart, though, they'll leave the door open so that people who want to sweep in and do their tweaks can do so easily. I've done lots of UI tweaking on my machine (heh it's fun watching other people use my computer) and the benefits have been enormous. I'd hate to have my workflow disrupted.
          • by emil ( 695 )
            And you [i]certainly[/i] never know when a tweak could corrupt and endanger your machine.

            While I've never used it, Mac OS X is based on BSD UNIX, and enjoys protected memory and filesystem permissions when configured properly. Any GUI tweaks that do not involve root authority should not impact other accounts or system hardware. It is quite common for UNIX users to create separate accounts to run untrusted apps, and this can be done with moderate to high confidence on patched systems. Unless a root exploit is involved, the worst a rogue app can do is trash your account (fork bombs excluded).

            I realize the fear that many Mac users have of applications that crash the system. Under UNIX, this propensity is greatly reduced if not eliminated.

        • by Speare ( 84249 ) on Tuesday October 01, 2002 @02:33PM (#4368640) Homepage Journal

          The best of the artists I've met love to tweak the tools, whether it's a new pencil, brush, table, welding iron, or computer. That's how new techniques are developed, how inspirations become expressions.

          Who said, "The reasonable person adapts to his environment. The unreasonable person tries to make their environment adapt to themselves. Thus, all progress is made by unreasonable people."

        • by mttlg ( 174815 ) on Tuesday October 01, 2002 @03:10PM (#4368935) Homepage Journal

          Nobody wastes time and energy rearranging the buttons on their tape deck, or changing the way their pencil works. It's a tool, and you use it so you can get the real art done.

          And just what are you supposed to do when the tool has a slight problem that makes it a pain to use? Think of how simple a pencil is, and now think of how many different kinds of pencils there are. If an artist doesn't like the way a pencil works, he can get a pencil that works better or change the one he has. Now scale that up to the complexity of an OS (much more complexity, very few choices). If I don't like having my screenshots come out as PDFs in 10.2 (TinkerTool could change this in 10.1), what are my options (besides going back to 10.1)? The truth of the matter is that nothing will be the best choice for everyone. I want my tools to be customized for how I work; I don't want some idiot in Cupertino deciding how I want to get things done. It seems like Apple is aiming for the market share of Linux and the user satisfaction of Windows, but still falling short on both counts...

          (Note to moderators with the reading comprehension skills of a turnip (no offense to turnips): the above is not a troll or flamebait, it is just an honest description of the frustration that comes from watching your favorite tool do little things that really piss you off sometimes.)

        • What kind of artists do you know? According to your thinking, all artists should be buying brushes at Wal-Mart, since a brush is a brush, just a tool. They'd all buy #2 Ticonderoga pencils there as well since sketches are always done with the point of the pencil. That's all there is to art, right? Fine line drawings and paintings done with a 4" nylon brush?

          Every painter I've met spends time tweaking their brushes before use. After buying a new brush, they shape it, trim it, thin it out, whatever they think they need to make that generic tool a specialized tool.

          Sketch artists have a variety of pencils of different hardnesses and thicknesses. Most carry around sandpaper or knife to shape the points to suit their needs.

          Photographers are probably the best example of tweakers- they have a half dozen lenses and a slew of filters. Half of photography is the subject material, the other half is getting the camera set up properly. Ever heard of breathing on the lense to soften the image? There's a pretty good tweak.

          Mac users tweak just as much as anyone else. Any graphic artist using MacPaint? Or do they have PS and a couple hundred plugins? Where did those plugins come from? From tweakers of course. Why is PS the premiere graphics program? Because Mac users have been prodding Adobe along, asking for tweaks to the program they couldn't make themselves.

          Zen artists were known for dipping their hair into ink, slopping it on a sheet of paper, and turning that slop into an image of a flowing river. Dipped a chicken's feet in ink, let it walk across paper, and turned those prints into falling leaves. Can you call a chicken effective, reliable, or simple? It produced art nonetheless, because the ARTIST knew how to create. Art doesn't create itself if you have the right tools, the Artist creates with or without the right tools.

          • by dbrutus ( 71639 )
            I suggest that you look inside some program bundles. There's a great deal *more* tweaking capability available than previous versions of the Mac OS allowed.

            Speaking as an admin whose first mac was an original SE in 1987, I can tell you that Apple has always had people messing around with their undocumented internals and they've always punished them. They don't want people to get the idea that it's safe to muck around in the internals because if any significant dependencies develop, they lose their portability.

            Why was the 68k->PPC transition so smooth? Because for the several years prior, Apple was doing exactly the same thing, changing their undocumented code around so that people wouldn't create a large installed base of code using undocumented APIs. Or, if they persisted in that foolishness, to create the expectation that every major OS upgrade was likely to cause a temporary break in this code until they re-did the reverse engineering to make it work again.

            With Interface builder and the package standard for software, software is becoming more, not less modifiable. You used to have to download ResEdit to mess around with a dialog in an app, now you can open up the nib in Interface Builder and fairly easily add options, menus and commands. You can even add entirely new languages as the strings are supposed to be kept seperate. That creates an entirely new category of software tweaking as people can add Romanian or Urdu whether the original app maker has a clue about these languages or not.
      • by Mr. T ( 115438 )
        The thing is, I think Apple is trying to keep people from making the interface look like crap. Notice that the three screenshots (given as examples of the way older versions of Mac OS could be tweaked) looked absolutely atrocious, at least in my opinion.

        People can come up with some pretty awful "themes" - just browse a Winamp skin gallery sometime. I remember coming across some really window manager themes when I was using Linux, as well. In fact, I would go so far as to say that the majority of user-created temes look really bad.

        Another thing is that when you've got a "theme" that rearranges buttons on a window, you'rw got a real interface problem. You mentally memorize the locations of buttons on a screen (for instance, to minimize a window), but all the sudden you have to "re-learn" the position, and when you switch the theme again, you're back to the old way. Consistency is very important in design - it's one reason I stopped using Enlightenment in favor of a WM that kept the position of buttons the same.

        Now, some people are going to disagree with me, and that's fine. If you really must tweak things, use Linux or something along those lines. I think it would be nice if Apple allowed some level of access, while still retaining the same look and feel. Remember, though, Apple's hallmark is achieving quality through control of the OS, hardware, etc., and I can't say I don't blame them.
    • by PythonOrRuby ( 546749 ) on Tuesday October 01, 2002 @02:12PM (#4368445)
      While I don't doubt that there are some people who dig into the core of how their interface of choices works,and try to change it, I think there are probably a lot more Slashdot readers who are interested in having a system that stays out of their way, and "just works".
      • Actually I would guess that /. has more than its share of "tweakers." Besides, if Apple's interface is so good then why do people want to change it? Clearly there is at least a small market for people who want to tweak their OS X interface. If Apple wants to write those folks off, that's their business, but it doesn't particularly make me want to Switch.

        • by jtdubs ( 61885 )
          The problem is deeper than letting people that want to "Theme" their interface do so.

          It also lets application writers theme their applications. Then every application can look different than standard, people create their own widgets and hack the pull-down menus and the whole Mac uniformity is lost.

          The great thing about Macs is that, by and large, all the applications look the same, feel the same, and work the same.

          Apple probably isn't willing to sacrafice this uniformity to let bad application programmers write bad applications. Yes, you heard me correctly. BAD APPLICATIONS. Every study EVER DONE in User Interfaces maintains that uniformity is good. Writing your own custom widgets, hacking pull-down menus or title-bars to work differently than standard is ALWAYS BAD.

          Justin Dubs
          • If these non-standard applications are so bad then why doesn't Apple simply let the market take care of them? After all, no one wants to pay money for a piece of software that makes their computer harder to use. You apparently are very happy with the default interface to your Mac, but apparently not everyone feels the same way that you do.

            It's Apple's software, they can do whatever the heck that they want with it. They might even be correct in thinking that most people want less flexibility instead of more flexibility. However, it appears to me that Apple is dismissing one of their more vocal (and loyal) userbases by locking out these "tweakers." I don't care what Apple thinks, that's bad business. After all, these tweakers spend money on Apple hardware too, and if they are unhappy they might switch to something more flexible. Most Apple users are already under some pressure to be compatible with the rest of the world (ie. run Windows). Apple can't really afford to create friction between them and their most outspoken users. Opening up the APIs necessary to change the look and feel of the desktop won't hurt anyone if most Mac users are (as you propose) looking for uniformity. If Mac users are truly looking for uniformity then applications that tickle these APIs will be unpopular. No one will use them, and they won't matter in the slightest. It appears to me that Apple is afraid that these changes will become popular.

            It's a pity really. Apple's obsession over hardware control is what has relegated them to a secondary position in the market, and their obsessive control over the interface is not going to help them in the long run either.

      • Look, we're not just talking whole-sale enlightenment reworking of the entire UI--they won't let me change the darn system font! Frequently I've felt quite a bit of eyestrain on my ibook, and I'd have loved to have resized the font a little bigger. That's all! Forget changing key shortcuts, themes, sounds, forget all of that, I just want to be able to read the screen without squinting!
  • by Sc00ter ( 99550 ) on Tuesday October 01, 2002 @02:06PM (#4368393) Homepage
    This only has to do with messing around with the Aqua interface.

    Yes, it's still lame, but they're not trying to close off the whole OS..

    • by krog ( 25663 ) on Tuesday October 01, 2002 @02:36PM (#4368668) Homepage
      One of Mac's biggest goals and strengths since 1984 is a clean, consistent interface between applications. I'm glad that Jobs et al have continued to strive for that, because once you lose a consistent interface (hmmm... Xaw/Motif/Qt/GTK/FOAD/etc) you will never, ever get it back.
      • ``One of Mac's biggest goals and strengths since 1984 is a clean, consistent interface between applications.''
        Yes, that's why they were cracking down on the efforts to make Aqua skins for the various widget libraries that X apps use. Now they have GTK,Qt,Xaw,Motif, _and_ Aqua.

        ---
        fee fie foe foo
      • They had a clean consistent interface before, even if the overall OS wasn't too stable. The problem here is that any customization is virtually impossible. They're ramming their ideas about how a UI should look down our throats- not only how it behaves, how it's laid out, but how it *looks*. Why the fuck won't they let me turn off antialiasing at least?
        • Much of the way the OS *looks* is indeed customizable. Many of the visual elements are stored as PDFs or TIFFs within the various OS components. Editing them is painless.

          As for anti-aliasing, chances are that this is an integral part of the PDF engine. My guess is that providing two paths through the Quartz display system, one that enabled anti-aliasing and one that did not would have required to many resources. Or, if that's the way it was previously, it may be that maintaining two paths was taking up too many resources. Either way, if you want a look at how anti-aliased fonts would look in OS X, open an app that uses font sizes below what you have your "General" system preference set to stop anti-aliasing below. Don't know about you, but it looks pretty damn ugly to me. Character spacing is totally whacked and formatting is totally horked. Overall, it gets pretty unreadable.

          Maybe they should allow you to tweak the anti-aliasing, maybe not. Either way - this particular story is just a pissy Wired journalist on a slow news day. That's my opinion, but I'm stickin' to it.
      • Umm, wait. (Score:5, Interesting)

        by molybdenum ( 150049 ) on Tuesday October 01, 2002 @03:23PM (#4369033)
        One of Mac's biggest goals and strengths since 1984 is a clean, consistent interface between applications.

        You mean applications like iChat, Calculator, Address Book, and some others?

        Apparently, it's okay for Apple to break any consistency in their UI based on some ridiculous rule such as this (paraphrased):
        If the application is used to interact with a digital device, or if it replaces some other familiar real world device, then the brushed metal theme is appropriate.
        Now, it may just be me, but how does this help the user in any way? From my experience, the brushed metal apps have slightly different conventions. Lists of items have striping (see iTunes), buttons that modify those lists are at the bottom of the window (iTunes, Address Book), etc. Essentially, there is a whole separate set of conventions that the user has to learn in order to deal with these programs.

        How's that for consistency?

        Ben
        • Re:Umm, wait. (Score:5, Informative)

          by gig ( 78408 ) on Tuesday October 01, 2002 @07:34PM (#4370609)
          Single-window apps like iTunes are the exception to the rule about interface consistency across applications. When you're working on documents with Dreamweaver and Photoshop, you want the windows to be the same as you manipulate your data and move back and forth seamlessly between windows regardless of which app is making them, but when you click on iTunes, you want to see a jukebox, not dozens of windows, one for each song or album. When you run Disk Utility, you don't want separate windows for each attached device, you want a central interface for selecting devices and testing and/or erasing them. Still, single-window apps respect drag-and-drop, and show Dock icons, and use the menubar ... all these things are optional on Mac OS X, but developers do them because Apple has made it easy and because users like it and are willing to pay for it.

          It's up to the developer how they want to write their app. They can also port a UNIX or Java app really easily and hardly change a thing, so to say that developers can't do what they want on the Mac now is strange. Some apps install X Windows and run just like they're on any other UNIX; some Java apps can be started by downloading them from the Web and then approving their launch locally.

          What Apple has with Aqua is a very plain and simple GUI language that they encourage you to either adopt entirely or else completely ignore. If you adopt Aqua entirely, your app will be a single icon that doesn't need an installer and that will just plain work when it's launched by 99.999999% of the users who encounter it. You can create a really elegant app that is a great Aqua citizen and it will be easy to use and people will pay for it and be very happy with it. Or, you can install X Windows, or ship a command line app, or whatever, and you won't have much of an impact on people who are attracted to Aqua apps for the ease-of-use that comes with their consistency.

          One thing this article doesn't mention is that you can do all kinds of things to the display with Quartz. Rather than focusing on changing out bitmaps like on earlier systems, you can alter the way the system looks by applying a graphics filter to the whole lot when it's composited. If you check out an app called Black Light on Mac OS X it can change the way the display looks quite significantly using Quartz. To argue over getting into the System folder to put in substitute bitmaps is old-fashioned on Mac OS X. The window server is doing stuff with the bitmaps it has, not just showing them ... it's scaling and transforming them and compositing multiple layers of 32-bit graphics. Plenty of room for developers to make interesting stuff, but it won't necessarily be a port of Kaleidoscope.
      • Dude, if you buy a computer, you should be able to do whatever the hell you want with it. I can understand why Jobs and the people at Apple want a consistent interface experience, but if I fork out $100 for MacOS X and decide I want to change the window decorations, I should be able to do it.

        It is kind of like web design. Web artists go to a lot of trouble to make their web pages look a certain way, but if I tell my browser to use a custom stylesheet it won't look the way it was intended. That is my prerogative, though, because it is my browser.

        So basically, MacOS X still has a nice consistent user interface. If somebody buys a Mac and doesn't mess with the default settings, the desktop will be familiar and look the way it was intended. Jobs and Apple have accomplished their goal. There is no reason for them to prevent customizations if somebody decides they don't want a consistent interface, if they don't want their desktop to look like every other Mac desktop on the planet.
        • So, install XFree86 and tweak the hell out of it. No problem :)

          Seriously, though - computer hackers may know that changing a theme could have unpredictable affects or know what exactly all is encompassed when a theme is changed. But, Joe Average user may just like the way a theme *looks* without realizing any further ramifications. This creates problems as installing themes and tweaks isn't limited to folks who know what's going on. Support becomes an issue not only for Apple, but for all the companies that develop apps for OS X. Office v.X has a very specific set of interface elements that integrate very closely with the way Aqua looks and feels. If Aqua is changed dramatically, then Office v.X may become more difficult to use, causing a problem for MS support.

          Maybe one person would only want to change the color of the menu bar, maybe someone else would want to change the size of window decorations - well, all this would start making Apple's relatively simple APIs, unduly complex. Apple's trying to walk a fine line between providing the necessary flexibility in the OS to not curtail other's creativity, but also making the standard APIs easy enough to use that companies developing apps, games, add-ons, etc. can get in and bring a profitable utility to market ASAP. All the while trying to keep their own internal development, documentation and support costs to a minimum.

          Its not just about allowing or disallowing tweaks. Its about a good deal more than that.
      • I agree there is nothing wrong with this. Those sample screens looked worse than the worst offenses done with WindowMaker and themes on X.

        The only argument for this is false. It says that some of the tweaks encourage innovation. In fact, if you have ever tried to design such toolkits, you would know that such abilities to tweak are a complete roadblock to innovation. If somebody relies on the fact that they can change "how a menu item draws" they necessarilly have locked into the interface the idea that there is a "menu item" and that you "draw" it. In the real world this means the menu items are probably rectangular, fixed size, and that the data needed to draw them must be available before the menu "pops up".

        This is difficult to state exactly, but I don't think people realize just how big of a hinderence this is to innovation. The best equivalent I can think of is filesystems, in the early days (pre 1970) there were record-based file systems with huge libraries to index and retrieve the records. The result was that it was very difficult to store new types of data, to implement new filesystems, and even the copying of a file from one device to another required the largest piece of software (pip) on the system. Then the seek/read/write type of file appeared, and the first systems that used *only* these files almost immediately supported enormous disks, networks, and communication and storage of files on almost any medium. The end result is that the systems with this "primitive" interface completely took over from the "fancy" systems and every single innovation in data storage and networking has been made possible because of this low-level interface.

        I think the same thing is need in the GUI and we are nowhere near it yet. But congratulations to Apple for trying to force the current GUI interface into a library interface and getting it out of the system.

  • Maybe, they just testing this out. I really don't see it as a big deal, but if people are really that upset about it (which I havn't heard until the wired article) and cause a big enough stink, I'm sure apple will release some api's. I have OS X at home, and I havn't had an itch to change much of anything.
    • Testing this out? They aren't doing anything. They're updating their UI APIs as they see fit. Something they're allowed to do.

      Did Kaleidoscope work when System 7 was replaced with MacOS 8? No. Do you know how these program work? They patch traps and do other funky-ass stuff deep in system memory because the old OS had no protection. All of the old UI hacks were just that: hacks that shouldn't be expected to be possible on a new, completely different OS.

      Besides, it's a new OS with a constantly changing under-the-hood series of libraries. If you're building your life around those changing, you have a big surprise coming.
  • OS tweaking (Score:5, Insightful)

    by andyring ( 100627 ) on Tuesday October 01, 2002 @02:06PM (#4368395) Homepage
    While some of the tweaks in previous versions of the MacOS were interesting and intuitive, I personally feel that OS X opens more possibilities than it closes. Granted, it may be tougher to modify the general look of the OS, but with it being a BSD-based OS, opportunities aboud to the extreme as to what you can do with the OS, both as it applies to the basic GUI and the rest of the OS. Before Apple had the functionality to put the Dock elsewhere on the screen, other people quickly and easily discovered how to do it. People quickly wrote drivers for various hardware (such as wireless cards), and other tweaks (like a hack allowing you to share your ethernet or PPP Internet connection via AirPort with other computers) before Apple included this functionality.

    As a very long time Mac user (1985-ish) and day one OS X user (from the beta version on), I think Apple has done a wonderful job with X, and I for one am not complaining if I can't make my menus or windows look a little differet.

    More power to ya, Steve Jobs, keep up the good work.

    • Re:OS tweaking (Score:3, Informative)

      by spankalee ( 598232 )
      Actually, most of these features were already there, Apple just hadn't created a user interface to change the settings. That's why most of these hacks were easy.

      The same is still true with SMB file sharing and the firewall. Because their based on standard Samba and ipfw there are numerous configuration options, but to keep it simple (or to reduce development costs, or just get it out the door) Apple's control panels aren't that powerful. Third party tools unlock the potential, but they don't create the features.

      I think Apple will eventually support interface modifications, but not until their OS matures and their user base grows. Locking out 'tweakers' has to more of a limitation and less of a liability for Apple to go for it.

      One major issue I think could be holding them back is that right now most OS X themers replace graphics in the /System folder. This means the theme is applied to every user. I'm sure in a multi-user OS Apple would rather have the theme apply to just a single user, but they're not going to spend their time on that now and it's better for them to try and lock it out than dilute their 'image' branding and possibly confuse users on multi-user systems.
  • UI != OS (Score:5, Insightful)

    by Anonymous Coward on Tuesday October 01, 2002 @02:07PM (#4368401)
    Correct me if I'm wrong, but it sounds like Apple is trying to close access to UI tweaking, not the OS.

  • by word munger ( 550251 ) <dsmunger@@@gmail...com> on Tuesday October 01, 2002 @02:07PM (#4368406) Homepage Journal
    What the article talks about isn't tweaking... It's cosmetic changes to the user interface. Apple isn't preventing users from doing useful things like modifying printer drivers, or creating time-saving macros.

    Keeping a standard user interface makes it easier for people to move from computer to computer. There's nothing that irks me more than working on a different computer at the office, and some wiseacre has removed the menus from MSIE.

    Besides, most Kaleidoscope interfaces were ugly as sin....

    • by trb ( 8509 )
      Keeping a standard user interface makes it easier for people to move from computer to computer. There's nothing that irks me more than working on a different computer at the office, and some wiseacre has removed the menus from MSIE.

      If a GUI is flexible enough to allow the user to have a Salvador Dali melting widgets look and feel, it should also be able to provide a way to get the standard look and feel back with a simple command.

  • by BitGeek ( 19506 ) on Tuesday October 01, 2002 @02:07PM (#4368408) Homepage

    Ok here's the deal: There are private APIs in OSX. They are undocumented and marked that way- these frameworks are in the private- frameworks folder.

    Apple isn't deliberately breaking peoples products, it is changing internal APIs.

    Many of these APIs start out internal and when they are ready for prime time, become public, supported, documented, standard APIs.

    Until then, you use one and it doesn't work in the next rev, its your own damn fault.

    And this is the right way for things to be- OS X is far more theme friendly than any other OS- hell the graphical eliments are all easily accessible pdf or tiff files and easy to replace. Want a different looking dock? Trivial. Want a different looking login window? no problem.

    But the areas where things can cause instability in the OS should not be left wide open for people to change in an uncontrolled manner.

    Quicktime has an API for skinning it. MAYBE Apple will release one for OS X, but if they are smart, they won't.

    Standardized controls are what makes OS X much easier for newbies to use than other operating systems.

    Let people change the look of their computer, but not the feel. That's the right strategy and the one apple seems to be following.
    • Double standard? (Score:3, Insightful)

      by Osty ( 16825 )
      Ok here's the deal: There are private APIs in OSX. They are undocumented and marked that way- these frameworks are in the private- frameworks folder.

      Apple isn't deliberately breaking peoples products, it is changing internal APIs.

      Can you say "double standard"? When Microsoft has undocumented, private, internal APIs, everyone cries "Foul!" and accuses them of hiding these APIs from developers. When they then change those internal APIs, everyone again cries "Foul!" and accuses them of breaking these internal APIs intentionally. But when Apple does this, it's okay? I guess I just don't get it.

      • Not quite. (Score:3, Interesting)

        by InThane ( 2300 )
        If Apple was selling a skinning program that allowed users to change their desktop appearance, and there were skinning apps in direct competition with Apple's apps, then yes, this would be a similar situation, especially if Apple's skinner continued to work, and the third party apps didn't.

        However, Apple isn't in competition with the 3rd party developers - it's just not supporting them, either. It's a choice that I personally think will end up shooting Apple in the foot - but in no way is it the same as the "hidden API" stuff that was going on at Microsoft
      • by BitGeek ( 19506 ) on Tuesday October 01, 2002 @02:25PM (#4368559) Homepage


        You're talking about two different situations. Just go to your mac in /System/Library/PrivateFRameworks and you can see all the private frameworks.

        Private is a lable-- it means "Don't use this, it may well change".

        What microsoft did was make the OS react different ly to different programs that were accessing published APIs. Microsoft was making its APIs not fit the specification, and it was providing hidden hooks into its OS.

        The private framworks are there for everyone to see-- you're just told that they will change. When they do, you don't get to cry foul.

        When microsoft releases a new product that breaks your own product that was using the public apis, then its legitimate to cry foul.

        The difference is microsoft was making it so products could only work if they approved them.

        Apple is merely saying "you're responsible if you use these, they will change".

        Yeah, that's a double standard. Nope.
      • by ivan256 ( 17499 ) on Tuesday October 01, 2002 @02:28PM (#4368581)
        Can you say "double standard"? When Microsoft has undocumented, private, internal APIs, everyone cries "Foul!" and accuses them of hiding these APIs from developers.

        You're right, you don't get it. The difference is that Microsoft uses undocumented APIs in their products that are sold outside of windows, while other application vendors don't get the benifit of those APIs. Apple's undocumented APIs are internal to the OS, and they don't use them in software that they sell in competition with third party application vendors. If an API is undocumented because it's internal to the OS it's OK, but if it's undocumented to give you an edge over other application vendors then it's wrong.
    • Look, the use of undocumented APIs goes way back to the earliest days of DOS. People use it, then the manufacturer has to either continue supporting it, or break it. Unless there's a valid technical reason to break it ... (sake for the sake of change breaks a LOT of things).

      Maybe Apple should have looked at the flame wars RedHat provoked with their attempt to create a "common" user look-and-feel between KDE and Gnome.

      People think - and rightly so - "It's my computer, I should be able to do whatever I want with it."

      Regards...

      • "Maybe Apple should have looked at the flame wars RedHat provoked with their attempt to create a "common" user look-and-feel between KDE and Gnome."

        I think they did and happily realized that they just didn't need to bother with such fuss. They already have a common look and feel and are quite happy with it, thank-you-very-much.
    • But the areas where things can cause instability in the OS should not be left wide open for people to change in an uncontrolled manner.

      Why? These people aren't modifiying the shrink-wrapped boxes Apples sells in the store. They're modifying their own machine as they see fit.

      This has nothing to do with stability. It's all about dictating to people how they can use a product they own by adding arbitrary restrictions.

      Standardized controls are what makes OS X much easier for newbies to use than other operating systems.

      Newbies aren't the ones doing this. Give your head a shake.

      Let people change the look of their computer, but not the feel. That's the right strategy and the one apple seems to be following.

      Why is it reasonable for a company to restrict the way we use the product? This isn't Apple designing a product to be consistent, this is Apple locking down an existing product that people are using is a way that they didn't anticipate, because the creativity these users are demonstrating angers them.

      "Think Different" indeed. Try "Think the way we want you to think.".

    • Total speculation (Score:5, Interesting)

      by cryptochrome ( 303529 ) on Tuesday October 01, 2002 @03:07PM (#4368918) Journal
      Exactly. OS X is still very much under construction - many regard 10.2 as the first version that is truly ready for primetime. I think the code behind the interface may actually be in a stronger state of flux than the rest of the system - consider the changes necessary to get to an incredible interface enhancement like Quartz Extreme from the intolerably slow one in 10.0! Nor is Apple's tweaking likely to stop here. I've heard at least one rumor that they are working on another iDevice (not a pda, but not a computer apparently) capable of running cocoa apps with only a simple recompile. Such a device would certainly involve substantially altered interface code, which could use standard or stripped down .nib files.

      Obviously I can't verify the veracity of the rumor, but I can make these observations: 1) By keeping those APIs private, Apple is quietly trying to keep people from messing with what they consider low-level code that they probably have plans for, and 2) based on that assumption Apple is probably not concerned about themers like Kaliedescope, but major commercial programs messing with that code within an application a) thus shooting themselves in the foot with major revisions to/new versions of those APIs and potentially abandoning the platform b) lazily foisting distinctly counter-intuitive non-apple interfaces designed for another platform, or c) interfering with the proper functioning of other programs.
  • by ErnstKompressor ( 193799 ) on Tuesday October 01, 2002 @02:09PM (#4368418) Homepage
    Wired has truely become a worthless source of factual information...

    "For example, the API that allows for custom menus and icons on the right side of the top menu bar, next to the clock, prohibits all but Apple-approved menu items. "

    Funny, I'm running Jaguar and have both LaunchBar and FuzzyClock running just fine in my menu bar...

    I can't speak for all menu-apps but I don't think this article really speaks the truth.

    • I think what this refers to is that third party apps that use the toolbar are relegated to something of a second class citizen status, and lack some of the capabilities of Apple-sponsored toolbar items.

      For instance, my Proteus icon doesn't stay on the toolbar if Proteus isn't running, and I can't easily rearrange it on the toolbar by dragging while holding the Apple key down. I can do this(or remove the icon entirely) with the system-related icons approved by Apple(modem status, volume, resolution).

      As a disclaimer, I am still using 10.1.5, so I can't speak for 10.2.
  • I wonder if this is in response to the recent tweaks to change the put back the Smiley Mac [macupdate.com] at boot?

  • The article's focus (as is to be expected from a pseudo-technical publication like Wired) is on tweaking to the UI -- theming the desktop to that the shiny candy buttons appear in your favorite flavor, changing the font in dialog boxes, making menus sticky so they don't fly back when you release them.

    The more substantial performance hacking involving BSD kernels and command-line shell prompts and so forth seems to be a completely different subject altogether.
  • Enough already (Score:5, Insightful)

    by Golias ( 176380 ) on Tuesday October 01, 2002 @02:13PM (#4368449)
    Damn, I am so sick of so many people, especially on /. say "I would totally buy a Mac if it weren't for nitpick $FOO."

    Nearly everybody must realize by now that such statements are usually a load of shit. Most of you will never buy a Mac, or switch to a Linux desktop, no matter what, because Windows is all you know, and all you care to know. You don't want to invest the added cost of a Mac (or the added effort of Linux) to discover if their virtues are worth it. You are lazy and groping for excuses.

    Just fess up. You don't like Macs, you don't want a Mac, you will not buy a Mac. That's fine. Use whatever the fuck you want, just stop with the constant whining about features that you (or some underpaid web journalist) think are missing from the platform.

    • I would argue that most of the web journalists who whine about tech issues (or most issues) are overpaid, rather than underpaid. Even if they don't get paid.

  • Well, Macs do call themselves "addicts," so it's no surprise that amphetamines have become more popular...

    Wait, that's tweeking, not tweaking. Nevermind.
  • My take (Score:5, Insightful)

    by Auckerman ( 223266 ) on Tuesday October 01, 2002 @02:14PM (#4368458)
    I'm sorry, but this is rubbish. The skin resource file for OS X (even 10.2) is understood and people continute to "skin" 10.2 (Keildoscope author not with standing). The same 3rd GUI apps for OS 9 are available for for 10.2. I've talked to people who hide their dock and use OTHER apps with other functionality. So there is no Apple sanctioned "Appearance Manager" in 10.2. Frankly, I would say, Apple only grudging supported the Appearance Manager, after pulling their own skins from 8.x after the beta process.

    The problem is that no developer has steped up to plate to make a good PreferencePane for Skining and Icon changing. There is a difference between saying it's not possible and noone has bother to make a good app to do it.

    I would go with the latter.
  • by Mars Saxman ( 1745 ) on Tuesday October 01, 2002 @02:14PM (#4368463) Homepage
    It's easy to customize the interface when the system provides a mechanism for patching any system call and offers no memory protection. You can hook yourself right into the UI code and do whatever you want. Of course Apple doesn't want to support this sort of thing anymore: it practically guarantees instability. INITs were always hard to do correctly, and I'm glad to see them go even if it does mean it's harder to customize the UI.

    I don't blame Apple for messing with internal API calls. If I were in their shoes, I'd deliberately break anything that used undocumented calls in every release. This keeps hack developers on their toes, as they are forced to upgrade their OS and re-test their hacks for every release; there's no more of this "well, it worked back in 1987 on my Mac SE, so it should run fine on my G3 using OS 9.1" crap Mac users have been living with for so many years. It also preserves Apple's ability to change the OS implementation internally; if they leave undocumented APIs static for too long, developers will start to take them for granted and users will complain when Apple breaks them. Better to break them on purpose and prevent anyone from getting too comfortable.

    -Mars
  • by SirSlud ( 67381 ) on Tuesday October 01, 2002 @02:14PM (#4368466) Homepage
    Thats a misleading article.

    They don't want you messing around with the functionality of the widgets. You know what? I agree with them.

    Esp. since you can run other window managers under Darwin (uh .. right?), you still have choice.

    And this article says nothing about them trying to prevent the kind of 'tweaking' most Wintel users use - namely, performance, setup, etc.

    I don't have any problems with Apple trying to kill utilities that tweak the UI. There's still choice, and there wasn't in OS9.

    As for Jobs saying, "Themes are dead", is he [deskmod.com] on [deviantart.com] crack [customize.org]? Or by dead, does he mean, "They're dead, because I killed them on this platform."?
  • redesign (Score:5, Funny)

    by carpe_noctem ( 457178 ) on Tuesday October 01, 2002 @02:15PM (#4368469) Homepage Journal
    You know, apple.slashdot.org should redesign the graphics on their site, just for spite. ;)
  • ugh (Score:2, Insightful)

    by khuber ( 5664 )
    This is the OS I'm supposed to like more than Linux?

    No thank you!

    -Kevin

  • so wrong (Score:4, Insightful)

    by geek ( 5680 ) on Tuesday October 01, 2002 @02:16PM (#4368484)
    I'm sorry but that article is so speculative. I didn't see any facts, at least no obvious ones.

    The interface is based on plists and pdf files, there is no way to stop tweaking. Apple tweaks things and breaks things that developers do with each new build but thats only because OSX is still evolving. In 3 years the interface will more or less be stable on Apples side.

    Besides tweaking the UI is pretty lame. It works the way it is, it's attractive or people wouldn't be trying to copy it right and left. Don't people have more important things to do than make their UI look like a Star Trek terminal?

    I started on Linux back in 1996 and I fell victim to the UI nightmares of the time. I spent countless hours tweaking my UI, much to the dissmay of my employer at the time who noticed I had a different window manager everytime he came over to my cube. Needless to say my productivity went to hell in a hand basket and I lost a lot of respect from the other folks in my department. This was all in some frantic attempt to make my OS usable. Apple has eliminated this altogether allowing me to actually get work done while using an attractive UI. Why someone would want to degenerate the OS into a hacked useless WindowMaker like experience is completely beyond me. However since most people who do this are kids I suspect they dont have anything better to do anyways. More power to them, just dont degrade Apple for making the OS useful for the rest of us.
  • OS 6-9 vs OS X (Score:5, Interesting)

    by Sargent1 ( 124354 ) on Tuesday October 01, 2002 @02:20PM (#4368514)
    I've used computers running MacOS from 6 through X. One thing that always made me cringe when I started up a pre-OS-X Mac was the sight of all those little extensions loading away, piling one on top of the other into a giant pyramid. Sometimes things worked okay, but often they didn't. The MacOS extensions were reminiscent of the old TSR programs under DOS -- when you had a bunch of them, things became flaky.

    Given Apple's desire to have a more stable OS, not to mention their rigid UI approach, is it really that surprising that they don't want to go down the old Extensions road?

    While I'm sympathetic to those who want to tweak OS X, my teeth are set on edge by the phrases chosen by those who are reverse-engineering the hidden APIs. "They're stifling innovation!" Translation: "They're not letting me do what I want to do!"

    Were Apple breaking documented and open APIs, then you'd really have something to get up in arms about. As it is, if you're using undocumented APIs, expect them to change. You're going to be in the same land that all of us TSR writers of the 1980s were in: you'll have to modify your code each and every time a new OS version ships.
  • by Have Blue ( 616 ) on Tuesday October 01, 2002 @02:21PM (#4368523) Homepage
    Apple has always tried to maintain control of the GUI; they publish the HI guidelines and provide standard controls to keep the UI uniform, standardized, and consistent across apps and machines. Of course they aren't happy about utilities that change this interface around. Remember, one of the biggest pieces of criticism leveled at Linux and one of the biggest reasons commercial development hasn't taken off is that the GUI is a moving target: There are too many different window managers, versions of window managers, and theme options to present a stable platform for interface design. Apple knows that have exactly ONE gui is a very good thing; look especially at the mention of tech support issues. You may not care about that but Apple's target audience does and therefore Apple has to.

    And besides, we're making mountains out of molehills here. Apple gives you a built-in shell and a free IDE, and you bitch about not being able to put icons in the menu bar?
  • Big Deal (Score:4, Insightful)

    by wazzzup ( 172351 ) <astromacNO@SPAMfastmail.fm> on Tuesday October 01, 2002 @02:22PM (#4368527)
    The only people worried about this are the ones that like skins on media players so you have no freaking clue where the minimize button is. They are also the ones that code web pages that change the color and style of your browser widgets for no apparent reason other that the fact that they can. They also bitch when companies like RedHat take the next step in unifying the desktop experience to help Linux move forward to greater acceptance.

    A consistent UI is a good thing people.

    Besides, why is everybody aping about how pretty Aqua is if all they want to do is change it and muck it up?
  • Huh? (Score:4, Informative)

    by Wyatt Earp ( 1029 ) on Tuesday October 01, 2002 @02:23PM (#4368534)
    "Before 10.2, the API had been reverse engineered and was being widely used by shareware developers. WeatherPop, for example, used it to show the current weather, while Homeland Alert shows the U.S. government's level of terrorist alert. These utilities were broken by the Jaguar update. Unsanity recently released a utility, Menu Extra Enabler, to restore them. "

    Not true.

    I've got both WeatherPop and Homeland Alert running on 10.2 and 10.2.1 without Menu Extra Enabler.

  • by udecker ( 251844 ) on Tuesday October 01, 2002 @02:30PM (#4368614)
    This article is all fluff. You've got the one guy who wrote kaleidoscope complaining that the UI now has closed API's. In fact, if a user wanted to change their interface, the pxm resources can be easily edited with resources [versiontracker.com] available.

    Not only this, there are several themes available.

    The complaint here is that although Darwin is open source, (with most of the core components of the OS), the window server is not. Being a UNIX system, however, you can make a new one if you cared to. Simply running strings from the command line can pull most API functions out of a binary, so emulating them would be a tast, but not an impossible one.

    From the beginning, Apple has discouraged used from using elements in the Aqua theme file (extras.rsrc) which are copyrighted by them. However, a full replacement of that resource file that contains no Apple IP can't be pulled by Apple.

    Please don't listen to this argument that the OS is closed to tweakers. It's different now to tweak things, but you certainly can.

    See? A Titanium [geocities.com] theme, a Rhodium [mac.com] theme, a Gunther [violentlyfriendly.com] theme, a Totally Aqua [mac.com] theme.

    Hey, even a tool [geekspiff.com] to make them.

    Quit complaining.
  • Christ (Score:3, Insightful)

    by Jobe_br ( 27348 ) <bdruth.gmail@com> on Tuesday October 01, 2002 @02:32PM (#4368628)

    Some slap-happy journalist at Wired interviews a few folks and makes a broad statement about Apple being anti-tweaking. Talking about APIs not being open - hell, many of the OS 9 APIs weren't open, people just had ResEdit to tweak the hell outta things - big difference!

    Apple's lawyers may turn the other cheek, but its engineers have taken a more active approach. To prevent interface changes in OS 10.2, known as Jaguar, the software prevents programs from taking up certain bits of screen real estate. For example, the API that allows for custom menus and icons on the right side of the top menu bar, next to the clock, prohibits all but Apple-approved menu items.

    Aww, c'mon. Let's not rehash this. What the hell is an "Apple approved" menu item?!? Its not like a developer has to get an "Official Apple Menu Item" seal for his app or anything - just that previously there were multiple APIs for placing something in the menubar, now there is one definitive API. Big deal!

    Apple isn't losing any users, at least not ones that will spend $$ (after all, Apple's a business - they care about the Mac culture, yes, but they care more about the $$). Professionals that use Macs want stability. So many of the hacks for OS 9 would demote the stability of the OS to the ranks of Win9x or worse. Combining hacks would be even worse. Heck, even legit plugins for things like Photoshop could wreck your system. Apple knows this, so they're trying real hard to develop a system that provides what will hopefully become 'legendary' stability.

    Keep in mind, also, that Apple may be keeping its private-APIs private, not only to prevent instability from encroaching on the system, but also to prevent competitors (read: Microsoft) from easily stealing enhancements made to OS X. Obviously Microsoft can also steal an idea and reimplement it, but Apple doesn't have to make that easy on them. I understand that having the API isn't equivalent to having the source, but defining an API isn't exactly a piece-of-cake, either. It takes a lot of careful thought and a tremendous amount of time to develop a stable API and corresponding documentation.

    Musta been a slow news day at Wired.

  • by hyacinthus ( 225989 ) on Tuesday October 01, 2002 @02:34PM (#4368647)
    There's an irony in the Wired article praising the alterable nature of old System 7; one of the reasons why using System 7 was such a pleasure was that nearly all of the applications looked much the same and used the same interface elements. The readily available tools for constructing interfaces, notably ResEdit, tended to enforce uniformity as well. Yet appearance and behavior _were_ alterable, although it wasn't easy. I wasted a few months playing with custom WDEFs and CDEFs myself--with effort and trickery, you could do almost anything, but it was a great way to crash the system too.

    The main thing about System 7, though, was that it didn't really _need_ much modification. Oh, there were some useful little add-ons--toolbars like the Control Strip which floated above all other windows, menubar additions, Apple Menu tweaks. But mostly, the system was just fine the way it was, until Apple started fucking with it--the introduction of the "Platinum" (or Copland, or "Aaron", or whatever) look is when Apple jumped the shark, in my opinion. I played with Kaleidoscope for a bit, but I never used it for more than a few days, partly because it rendered the behavior of the system somewhat unpredictable (you never knew when some application's interface might not look really strange with Kaleidoscope enabled), partly because making the system look _pretty_, as in "ain't this a wonderful screenshot?" pretty, also makes it more difficult to use.

    But for whatever reason, many people think that the ability to set your system font to 48-point Wingdings and your window frame colors to be yellow and purple is the ultimate freedom. Hence the Enlightenment window manager, for example. Lots of fun to play with, great for amassing an album of pictures of people's desktops, but good and useful? Not really.

    Having a locked-down interface isn't necessarily bad. The BeOS interface (remember BeOS?) was even more closed than Apple's (either System 7 or MacOS X), but since it was spare, functional, and worked reasonably well, most BeOS users, including myself, didn't really mind.

    The trouble with Steve Jobs's obsession with preserving the Aqua look is that the Aqua look stinks. Not as badly as it used to, but the Dock is still an abomination, everything still takes up too much room, and if you're running a system at all limited in capacity (a 2nd-generation iBook in my case), the GUI's performance is irksome and slow. The beauty of System 7 was that it looked good whether you ran it on a Mac Classic or a PowerMac 8500. But Jobs's attitude seems to be, "Well, you should just buy a faster computer if it's slow, and a bigger monitor if it takes up too much room. Get with the program." (Ironic, considering that Apple is notorious for providing packaged systems with not enough built-in memory and small monitors.)

    hyacinthus.
  • by SensitiveMale ( 155605 ) on Tuesday October 01, 2002 @02:43PM (#4368720)
    There are dozens of themes out and more are released every week.


    There are at least 3 different programs to change themes; Duality4, MetamorphX, Chameleon.


    There already is a program to change system icons, Candy Bar.


    There is another coming, Xpression.


    There are a myriad of menu items, dock enhancements, window enhancers, custom menu builders, and just great all around utilites that enhance and extend the OS.


    The thing to remember, and what everyone forgets, it that Classic Mac OS was a mature OS that people had years to hack and discover. OS X is new enough that Apple is still changing APIs.


    Mac OS X is a very customizable OS and Wired is showing very little research and fact checking in thier article.

  • by al3x ( 74745 ) on Tuesday October 01, 2002 @02:53PM (#4368794) Homepage
    Discussions of interface issues often make for hot news items and even hotter discussion, but are they really relevant?

    I appreciate the even-handed approach of your article, balancing the frustration of tweakers with the reality of developing a stable, attractive, and easy-to-use operating system. But, as a student looking towards Human Computer Interaction as a specialization and immersed in the literature of the field, it's safe to say that no interface will please 100% of the audience. Those out to tweak endlessly fall into a minority that no interface designer can possibly account for without going insane, just as a scientist can't possibly account for all the potential variables and random factors in an experiment.

    In the artificial, "closed system" of interface design, the people with the free time and inclination to endlessly modify are always going to be unsatisfied. Is this newsworthy? A number of application developers have put out tools that enhance and work with OS X to rave reviews. There are a number of successful interface tweaks out there (my iBook has a fully transparent dock, for example). And, as someone who used to theme and skin, figuring out how to modify a closed program is part of the fun.

    I won't stick by Apple 100% on all of their decisions like some Mac users (after all, I've spent the last 6 years in Linux/*nix). But I will say that if you're going to do an article that more than suggests to Apple what to do and where to go, there are far more pressing issues than letting skinning nuts with too much free time make Aqua look like rusted clockwork, or whathaveyou.

    Just my $.02.
  • by ColdForged ( 453024 ) on Tuesday October 01, 2002 @03:43PM (#4369153) Homepage
    ... about what developers wanted/needed access to in new versions of the operating system (yes, I know that this article is really about UI tweaks, but figured I'd offer a perspective on what the topic of the post implied). I attended one of the Apple WWDCs (World Wide Developers' Conference) when I worked for the now defunct (well, "assimilated into the NAI universe") Dr. Solomon's Software on Virex, an anti-virus application for the Mac. When OS X was announced, we were decidedly worried about how we were going to get access to the file system areas that we needed to hook in to to intercept file opens and closes, along with other similar things. During a particular mixer, where Apple engineers and architects were around to sip beer and eat free food, we talked to the main architect and engineers of the file system team and had a great dialogue about what we needed and how best we could get it. They were interested to hear how we had worked around so many disgusting parts of the OS 7, 8 and 9 systems, and were honestly quite horrified to hear what was required in certain circumstances :). But, customers want to be protected from viruses in every possible way they can access files, so we had to do it.

    Traditionally this is a pretty tough thing to do, even in the best of times. Under OS 8 and 9, we had a hell of a time keeping the on-access scanning parts working with each new release of the OS... they would change behavior in AppleTalk functionality, asynchronous hooks, or whatever and POOF!, what used to work just fine now times out on accesses to remote volumes.

    The Apple guys were very open to trying to give us more reliable, sanctioned access to the file system hooks that we needed to have. Unfortunately, Dr. Solly's was soon thereafter assimilated by NAI and I was not able to work on the product anymore, so I don't know what they eventually did with the OS X product.
  • Themes vs. Usability (Score:3, Interesting)

    by fsck! ( 98098 ) <.moc.liamg. .ta. .redle.bocaj.> on Tuesday October 01, 2002 @03:53PM (#4369224) Homepage

    If anyone out there has a good explanation as to why a themable interface is more powerfull or easy to use than a consistent, static interface, I would love to read it.

    Personally, I think themed interfaces are the worst idea since... well I can't think of anything that comes close. For an interface to be usefull, and trusted by it's audience, it has to be predictable.

    Why does my music player look completely different than my web browser or my word processor? I guess it kinda looks cool in a screenshot by itself. But I embrace computers in my life to get stuff done, rather than to post slick screen shots. Exploring and customising a new computer or software package can be fun, but for most people it's not the end goal of having a computer.

    I can see how some OSX users on older hardware would like to be able to turn off text smoothing and gain a little speed. UI options for hardware compatibility or for people with low vision are fine, but "themes" as we think of them today have to go.

    Themes basically exist for two reasons (warning: opinions)

    • Lack of concensus amoung the developers about what looks "pretty."
    • Users who want different packages from different vendors to have the same look and feel (although themes don't usually bring a "feel" with the "look").

    In other words, UI designers lack leadership, and users crave consistency.

    A few years ago, it was practically impossible to sit down at a friends X11 workstation and know what any of the keymappings were or how the menus worked, or even start a program. It's gotten much better now with most people using either KDE or Gnome, but massive improvements are needed before free software will be as easy to pick up and use as OSX and Windows are.

    RH's choise to theme KDE and Gnome similarly was inspired, as are Steve Jobs' comments on themes. Thanks guys, keep it up!

  • by angelo ( 21182 ) on Tuesday October 01, 2002 @04:06PM (#4369350) Homepage
    He had his mac tweaked out, and tried constantly to change something about its configuration, that he never got his 'art' done.. his 'art' consisted at throwing filter after filter in photoshop onto a photo (usually something along the porn lines) at low res until it 'became' art or something. I called it crap. You can tweak all you want, but you are missing the point of 'just works'
  • Misses The Point (Score:4, Insightful)

    by johnos ( 109351 ) on Tuesday October 01, 2002 @04:16PM (#4369428)
    The thing is that Apple has done something remarkable here. They have put Unix on the desktop of ordinary users. The flexibility and extensibility of this OS is beyond belief. They haven't dumbed down Unix, they have transformed it. My kids can set up an Apache server in about five minutes. They can't do that with any other OS.

    I use Windows, Linux and Mac every day, and like them all. But objectively, OSX is light years ahead of anything else. IMHO, that is. It will take another year or two before this becomes clearly apparent.
  • by dutky ( 20510 ) on Tuesday October 01, 2002 @04:31PM (#4369534) Homepage Journal
    the article is pure, sesational, bullshit. While life is a bit harder for the tweakers who were counting on the Appearance Manager API (which got 'Steved', along with lots of othe crap from the darkest days of Apple), there is still lots of themeing and tweaking going on: at least as much as there was in the early days of classic MacOS (back around 1984-1986). Things will get more interesting as the Cocoa APIs mature and folks get more familiar with them.

    For the moment, however, there are a few malcontents that had a lot invested in the old way of doing things (the Kaliedescope folks) and just want to raise a stink because their sacred cow has been gored. The fact that Wired is giving them an audience simply underscores their journalistic calibre.

    Anyone who really wants to customize the appearance of their OS X windows and controls can still do so. In fact, it is far easier in OS X than it was in classic Mac OS: In OS X, many of the window and control theme elements are stored as simple PDFs or TIFFs, somewhere in the /System hierarchy. All it takes to modify the appearance of things is to replace those PDFs or TIFFs, and, possibly, edit a .plist or two. Compare this to classic, where you had to write a bunch of code to insert your custom PICTs, MDEFs, CDEFs, and WDEFs into the system at runtime, and it's hard to see what anyone is griping about.

  • by g4dget ( 579145 ) on Tuesday October 01, 2002 @04:42PM (#4369584)
    "Whereas Apple pioneered the completely customizable system, they are now headed in the other direction, trying to close most APIs that deal with the interface,"

    This sounds like making lemonade out of lemons. The Macintosh was "completely customizable" because it was a real-mode operating system. People could hack into its data structures from user programs whether Apple wanted them to or not. To bring at least some order to the madness, Apple added some APIs.

    For Apple, opening up the APIs that "control the placement, function and look of windows and menus" was a necessity. It wasn't something they "pioneered" either: X11 had those APIs designed into it from the ground up. That's why, for better or for worse, you can use dozens of toolkits seamlessly on the same screen, pick your window manager and lots of accessories on X11 as you like.

    For years, one of the big attractions of the Mac was the ability to customize the operating system. Users could completely overhaul the machine's interface, sometimes to the point where it was entirely idiosyncratic.

    Mac evangelists can't have it both ways. Either they like end-user customization or they don't.

    Out of the box, X11 desktops like Gnome, KDE, or Motif are as consistent as Macintosh, but X11 allows extensive end-user customization, it allows applications written with completely different toolkits to work together, and that's designed in, easy to use, and open.

    But that's not Apple's philosophy: Apple wants to bring a standard, simple user experience to the Macintosh, and having people "tweak" the UI interferes with that. That's another possible point in the GUI design space, and there is nothing wrong with that philosophy.

    But you can't have a GUI that offers both the possibility of, and support for, tweaking and simultaneously doesn't offer it. Apple has made the valid choice of trying to prohibit tweaking in OS X. That will appeal to many schools, universities, and IT managers. But it will also not appeal to many other users.

    Ultimately, Mac zealots have to learn the painful lesson that engineering and design consists of tradeoffs: it's impossible for a single product to be the best at everything. A company can design products that are bad at everything, but here is no "best personal computer", "best user interface", or "best operating system".

  • by ianscot ( 591483 ) on Tuesday October 01, 2002 @04:53PM (#4369668)
    Pretty classic bit of modern journalism. Our news channels cast anything as a radical conflict. If a reporter gets an assignment, job one is to identify a conflict, and job two is to categorize all sources in terms of which artificially-polarized side the source belongs to.

    Look at our primary sources here:

    "Apple is uptight about (changes to the interface)," said Brian Wilson, business manager at Unsanity, which has created a number of OS X interface utilities. "But at the same time they haven't given us any grief. We've had neither help nor hassle."

    Sounds like a draconian regime of not caring much, doesn't it?

    "It's the end of an era," said Greg Landweber, co-developer of Kaleidoscope, one of the most popular Mac customization tools ever created. "Under the old Mac system, doing these little interface tweaks was really easy. You could change almost anything. Now, you can't change the way they work, only their appearance."

    Greg Landweber's take, then, is that you can change the appearance, you just can't move the functional elements to completely different locations. Did anyone really use the Kaleidoscope themes that had the window buttons on the side? Those are the ones that just hit the rocks.

    I took delivery on my 17" iMac last Friday. Believe me, there's no shortage of tweaks to the UI. I'm running a handful now. If Apple's making noise just now, it's just to emphasize that tweakers are there only at Apple's discretion -- always the case, right?

    Just another overstated conflict story where there really isn't much of a conflict, if you ask me.

  • by guttentag ( 313541 ) on Tuesday October 01, 2002 @05:19PM (#4369878) Journal
    A few weeks ago I received an email from an Apple exec in response to my Apple essay (see my sig). The exec (no, it's probably no one you've heard of) also asked what I thought of Mac OS X, so I sent a rather long reply which included:
    I love the stability and degree of control the underlying Unix provides. Looking back, I can't imagine how I got by without shell scripts, and I try to encourage others to discover them as well. Mac users like an easy-to-use interface, but they're also adventurous. They'll tackle any steep learning curve if the rewards are great enough, as long as they have their safe Macintosh UI on which to fall back.

    I also like the clean interface, though it would be nice if Apple supported the third-party themes users have been waiting to create since 8.5 whet their appetites. In some ways, it seems almost too clean, like a college dorm without posters or christmas lights.

    Over the weekend I received a response which included:
    many thanks for responding in such detail! i share many of your opinions and you mentioned a couple of things i wasn't aware of- much appreciation for that.
    So perhaps there's hope. :o)
  • by imacosx ( 612986 ) on Tuesday October 01, 2002 @05:23PM (#4369901)
    The story on Wired reports that changing the appearance of the GUI has become more difficult with Mac OS X. Isn't it a little extreme to conclude that the whole OS can not be tweaked. If Aqua may not be reconfigured as easily as some wish it to be, Mac OS X is a UNIX operating system, that runs many open source programs, including XFree86, Gnome or KDE. And I have as much fun tweaking Mac OS X than I have tweaking Linux that run on the same iMac, even if I haven't changed the appearance of Aqua yet.
  • Apple Menu (Score:3, Insightful)

    by Draoi ( 99421 ) <.draiocht. .at. .mac.com.> on Wednesday October 02, 2002 @10:54AM (#4373508)
    For example, the API that allows for custom menus and icons on the right side of the top menu bar, next to the clock, prohibits all but Apple-approved menu items.

    Really? Then what about ASM [sourceforge.net], which I cannot get by without ...?? BTW, yeah it works with Jag.

Understanding is always the understanding of a smaller problem in relation to a bigger problem. -- P.D. Ouspensky

Working...