A community of quality

Hey Drunken Bat Dude,

Is something going on with you? I was reading through your last post, and I recognize some of the behaviors you pointed out in myself, but the drunk I know would not have made me feel stupid while making his point. Just my opinion, take it for what it's worth.

Mark F.

I actually got two emails like this, and after a little sleep and some coffee, and now looking over that last post, there is probably some truth to them and I should take my lumps. I was certainly a little more acerbic in what I'm banging out than I often am. I meant everything I said, but given a second shot I'd probably word some of it quite differently, as if I'm making people feel stupid I'm letting people down, including myself. In deference, I proffer these excuses:

  • I'm stretched more than a little thin lately.

  • A few of the things I'm working on have me frustrated to a level I rarely reach, yet I have to sit on quite a bit of it, and it wouldn't surprise me if stuff eeks out around the edges.

Let's just say I've become somewhat obsessed with the current quality of Mac OS X, and Apple hardware in general, but for right now am keeping it to the quality of what is going out on discs. I've been devoting a lot of resources into digging into what's going on, enough that I'm already backed up on the chats again. Not full-on Deconstructing Maui X-Stream obsessed, but it's getting close.

I think most real users know, in our heart of hearts, that Mac OS X has been misfiring quite a bit lately, and that 10.4 was almost a total misfire in terms of actually using it. It doesn't mean we're going to switch, it doesn't mean we've given up, it just means we know something is wrong.

You can like the idea of XHTML/JavaScript/CSS apps and still know Dashboard was a complete misfire, even if your only clue is that they're bolting on major functionality in a .2 release. You can like the idea of building webkit into your apps while knowing the quality of what you are building your app around isn't at the level it should be.

Severe, extreme wonkiness like this doesn't happen by accident, whether it is going on at Apple or Microsoft or anywhere between.

Easy, guys.. I put my pants on just like the rest of you - one leg at a time. Except, once my pants are on, I make gold records.

Some of what I'm finding out -- while doing my best to verify through multiple sources -- is that Apple has some people in key positions (think VPs, etc.) who are committing the cardinal sin of not listening to the UI or software engineers. Marketing has their ear, and in some worst-case scenarios, no one does, and whatever they happen to subjectively think is neat is the way it is.

You don't think Spotlight starting a search a millisecond after you've typed one character, and are still trying to finish typing what you want searched was rubber-stamped by any type of usability engineer, do you?

I'm still sifting through and connecting the dots, but more than one of these managers appears to be have come over from Microsoft, and most of what I'm hearing makes sense because my experience leads me to believe when things go this wonky its rarely about the engineers, and some of what I'm hearing also helps explain why some aspects of the system are so solid and others are as flaky as anything Microsoft put out on their worst day.

I'll talk to guys about what they're seeing in say, Core Image, and they'll bitch about some things sure -- some even major -- but they're generally in love, even if they think there are bugs that shouldn't be there that more testing would have found.

Then we'll talk about Webkit, and they'll go on about how much of a timesaver it is to have an engine built in, but that it's responsible for 95% of their application's crashes and 25% of their time goes just to working around its bugs. They can see the value in what is there, they are just not amused at the quality of the implementation. I'm just using these as examples for now, but you get the idea.

Since I mentioned it's rarely about the engineers, you may well be confused how the person actually coding something wouldn't be held responsible by myself, and a good example would be a movie I saw recently: Fantasic Four.

Now, without being on the set, I can tell you:

  • This wasn't a good movie. It was just bad, and while it raked in some cash -- quite possibly due to a huge marketing budget -- no one will remember it as time goes by.

  • A ton of people involved in the making of this movie really gave their all, and poured everything they had into it.

A lot of people can work very hard on something, using a lot of resources, only to have it turn into clusterf**k because of the poor decisions, priorities and demands of a few whether they be marketing or just a manager who thinks his subjective taste is better than a usability study.

The problem is that if you bought your ticket even though it sucked, Fantastic Four is the bar to meet for the sequel, and if you play with the numbers you might even find you're able to pump up the marketing for the sequel while scaling back the quality. This is what managers and accountants do, and there is value in it.

Unfortunately, after awhile, if people keep going and they keep sorta sucking, a general malaise sets in and superhero movies start to bomb, and then superhero movies won't get made for another decade whether they're good or not.

There can be too much cowbell

Back in Heading Over the Cliff While Whistling, I said:

I've written blurbs about this here and there throughout my posts, but the bottom line is that there's a huge elephant in the room when it comes to Mac OS X: The UI is going to hell in a hand basket and everyone is just averting their eyes...

See, here's the rub -- it's gone well past the anal pixel-pushing designers now. Just about every Mac developer I've talked to believes the Mac OS X interface is in serious trouble.

You may not think the Mac UI is or was in trouble, and that's fine as I'm not asking you to agree with me or concede any points. However, as far as I'm concerned, what is going out from Apple that's being called user interface is becoming a joke to anyone I care about.

Their reputation for interfaces is becoming synonymous with fashion and prettiness, not usability. As far as I'm concerned, users shouldn't have to settle for two out of three, especially Mac users.

Now, Tiger may be running like a complete dream for you, and, well, that's great and I don't begrudge you it, because bugs don't really work that way. However, it doesn't change that the problems are there, and that they're real, and that I had to complete the last interview on a Linux box because 10.4 was whacking out when it came to text due to a known and nasty bug.

I'm here to tell you that as above, just about every single developer I know now thinks the quality of the code that is coming out of Cupertino often just isn't where it should be. As mentioned earlier, this is spotty with some areas being solid and others being quicksand.

I know many, many Mac developers and talk to them more often than they'd probably like. Since many of you aren't developers, and can't really see what these guys are dealing with, and most of them have to be very careful about what they say publicly.

I guess this is where I call in some of the trust I've hopefully earned over the life of the site when I tell you much of the stuff they are having to work around is stuff they should not be having to work around. It's not the end of the world, it's just not nearly where it should be.

Teh Shiny

To go back to stuff seeping at the edges, part of the problem is that I'm really angry right now at myself, and I'm angry at you, and I'm angry at the Mac community as a whole for letting it get this bad. In some ways, we've let Apple wear down our will to thinking this is just what something like the Finder is -- the best it could or should be. We often forgive too easily while asking too little.

We bought the ticket, and console ourselves with the fact that Jessica Alba looked choice, but there is no getting around that as a whole its not fully baked.

I count myself at the forefront there. I installed Tiger and saw how badly implemented features like Dashboard and Spotlight were, and how flaky the system as a whole was, but I kept thinking it'd all be fixed with a point release or so. I didn't talk about a lot of it, because it often seems like there is such little point when the communication with Apple is all one-way.

It has become increasingly difficult to even say what is wrong, both because so much is wonky and because what it means to be Mac-like has been co-opted so severely by whatever marketing thinks will look shiny. It's lost much of its meaning, aside from the shiny.

The Mac used to be about the user interface, but when that got sucked into shiny-land rather than usable-land or even the dare-I-dream-usable-and-shiny-land, people stopped caring so much about usability. It used to be about making things harder on the computer so its easier on the user, but it isn't like someone can back up their computer by dragging one drive to another anymore, because it would be hard for the Finder to be able to handle that.

It used to be about quality, about shipping when it was ready, and now it'll just get fixed in a few revisions afterwards -- hopefully. Ship-it-then-fix-it is not the Mac way.

In for a penny...

Another problem is that -- if you couldn't tell -- I haven't really counted myself as part of the Mac community for a long time. A foot in, sure, but not my full weight.

This mostly occurred during the end of the Amelio days and the beginning of the OS X days, where I just couldn't tell what the Mac community stood for anymore, and I'll be damned if I'm going to line up behind something just because it's in front of me.

However, the truth is that I really give a damn about the Mac, even as I've taken technological mistresses. I care, and because I do I'm a part of something whether I like it or not even if I don't know what it stands for.

When you look at the underlying architecture of Mac OS X, there is beauty and elegance there that can't be dismissed and shouldn't be given up on -- the effort just needs to be applied so that beauty and elegance carries all the way up through to everything we're using, from the APIs to the Finder and all the way to Spotlight and Mail.app.

While I may have problems defining what the Mac community stands for right now, or even what the Mac stands for right now, the base denominator of the Mac for me has always been quality, not different. It's not enough to not be Microsoft, or not be what everyone else is using, or to ship first. That's the community I'm choosing to be a part of, and I guess hoping exists, so I'm not out on my own.

I'm telling you this because it's going to be the major focus of the site for the foreseeable future, and I want you to know why I'm going to be talking about the things I'm going to be talking about, and to even give you the opportunity to bow out if Mac OS X is just where you need it to be. No hard feelings on my end, but do please say goodbye to The Cow before you leave.

However, personally, I just can't identify a bigger problem on my radar than what I've just gone over, and I think its important.

You're thinking it

Let's be honest, Apple isn't like other companies to us, and the fact that we even use the term community in the way we do shows it off quite well. When there are problems, there is a tendency to try to handle them internally, within the community, because you don't want the outsiders to know about the dysfunction in the family. Much better to sweep it under the rug so the neighbors aren't talking about us at dinner.

As a Mac user, we sort of have to deal with this, because it's there and we can't get away from it. I don't have any problems telling someone to stay away from a particular model of Dell laptop because its known to have severe issues, yet my first instinct is to shy away from telling someone who is interested in a Mac just how many problems the iBooks or Powerbooks or iMac G5s are having.

In both examples you'd be helping out your friend by warning them away from a potentially bad purchase, but we hesitate because in the latter example we'd be harming Apple in addition. We don't want to talk about a lot of things because it's hard to talk your friend into switching when you are going over just how lame so many aspects have become.

It's much easier to just not talk about the problems, or gloss over them, or sweep them under the rug, or to say "Mine works fine, must be something strange on your system", because hey, even if it is a real issue of course it'll be fixed in an upcoming point release soon. After all, all software has bugs, you can't expect miracles, and at least you aren't having to deal with spyware and warez.

Apple is a big company, and can take care of themselves. They can take it, and really they have to. If we don't talk about this stuff, and apply pressure, there is zero impetus for change and improvement. It has to be a public issue.

I'm convinced the software engineers at Apple know there are problems, but some of the people above them don't, and many of the people above them surely don't, and this is actually a case where there is little they can do from the inside without pressure from the outside.

Towards Mac OS 10.5

One day, I want to be able to show off the Finder, rather than skipping past that part of the demo as fast as I can, or feeling like I have to apologize for it. I want to be able to show them how to get their email without having to suppress a gag reflex, and I want usability engineers to be able to point to what's great about the OS X interface instead of what's pretty and why something is usability nightmare.

I want developers spending more time making Mac applications rock instead of having to write code to work around bugs in the APIs, which seem to only get more plentiful with each release.

That's my goal.

As we head towards 10.5, accomplishing it may not really be possible, but it wouldn't be the first time our eyes were bigger than our plate, yet we choked it down with help. Leopard may well end up hurtling itself towards the cliff, but if we're really yelling this time it might hear us.

yummy alcohol posted button Posted by drunkenbatman
    August 01, 2005, at 02:59 PM


Comments (48)




Post a comment



Anonymous comments are allowed, but please enter something for a name.

And do endeavor to appear sane.









Remember personal info?