Set Password Activation Time in Snow Leopard
In Snow Leopard, you can now set an amount of time after your Mac goes to sleep or engages the screen saver before it requires a password to log back on. In Leopard, the option was simply to require the password or not. Choose among several increments, between 5 seconds and 4 hours, from System Preferences > Security.
Series: MacHack '99
Adam Engst reports on the ultimate Mac geek get-together
Article 1 of 3 in series
Every so often, I feel like a total idiot. I've been reporting on the Macintosh industry for over nine years, and for the first few years, I vaguely knew there was a developer event called MacHackShow full article
Every so often, I feel like a total idiot. I've been reporting on the Macintosh industry for over nine years, and for the first few years, I vaguely knew there was a developer event called MacHack. At some point, MacHack was explained to me, and as I made more contacts in the industry, an ever-increasing number of people invited me to attend. I always demurred, begging off on the grounds that I wasn't a programmer, or that I couldn't justify travelling to yet another conference, especially one in Detroit, which holds no external attractions like relatives in the area. Last year, I even helped in a small way to find loaner machines for the conference's public machine room; this increased the pressure to attend this year's conference, and I finally gave in.
What a mistake I've been making! MacHack is, quite simply, the most fun a serious Macintosh geek can have legally.
Identification -- Describing MacHack is like summarizing a zany movie - no retelling can capture the essence of the event. Still, let me attempt it.
A defining characteristic of a geek is the confluence of personal and professional interests. The Mac geek lives and breathes the Macintosh, checking email first thing in the morning, using a Macintosh at work all day, debating recent industry events with friends at dinner, playing games, making Web pages, or even writing programs at night. The details vary by individual, of course, but many people fall squarely into this category. For those folks, it's tremendously enjoyable to be surrounded by peers, Macintosh geeks of roughly equivalent experience and knowledge. Conversations amongst Mac geeks range widely and hop nimbly between Macintosh topics, unhindered by any need to differentiate between RAM and hard disk space or explain every Internet reference.
Many of us have had a taste of such an event, though it's usually limited to an evening user group meeting or a brief dinner party. But if a user group meeting is a taste, then Macworld Expo ranks as a light supper - the thousands of attendees make significant interaction with other Macintosh users difficult. There's also a sense at Macworld that someone else is cooking, and we're all guests who must maintain a certain distance and formality. In comparison, MacHack is a ten-course feast prepared in front of the several hundred diners by talented volunteer chefs who then remove their chef's hats and join in the exuberant gastronomic celebration.
In short, MacHack is a conference of the geeks, by the geeks, and for the geeks. Started 14 years ago by Gavin Eadie and some colleagues at the University of Michigan, MacHack became independent in its second year and continues to be organized by a volunteer committee made up of members of the Macintosh community, ably aided by the staff of Expotech, who handle the logistical details. The committee finds a keynote speaker, organizes sessions, designs the t-shirts, and generally ensures that MacHack will happen yet again, while Expotech handles registration, conference materials, coordination with the hotel, and ordering hundreds of boxes of pizza.
MacHack is a developer conference, and there's little question that developers find it tremendously useful. Where else can you ask a question of the best Macintosh programmers in the industry and get an immediate answer or spark a debate between the hotshot programmers and wizards from Apple's Developer Technical Support division, some of whom also attend? That said, I'm not a programmer at all, and I enjoyed myself tremendously. Pondering why, I realized that for non-programmers, two things must be true. You must be a serious and outgoing Mac geek conversant with current technologies, issues, and events, and you must be willing to participate.
In my case, participation came in the form of giving a session entitled "Hacking the Press" (which I plan to convert to a TidBITS article). I also let myself be rooked into offering a technical journalist's perspective in a session on industry terminology, and spent time helping a 12-year-old girl find the necessary software to use an old Connectix QuickCam to create her hack for the Hack Contest.
Education -- My brief donation of time and expertise finding software on the Internet was nothing compared to what many others at MacHack did for the younger attendees. Collectively referred to as "yoots," the student attendees ranged from a seven-year-old girl to a college student interning at Apple. Everyone encourages and helps the students, 50 of whom attended this year and 19 of whom worked on hacks for the Hack Contest. For instance, AppleScript was a popular language for many of the yoot hacks, and AppleScript guru (and author of the AppleScript editor Scripter) Cal Simone lent his expertise to a number of the students.
This emphasis on education is one of the most attractive traits of MacHack, because it spreads expertise among the community and also to future generations of programmers. Perhaps even more important is the example set by the generosity of the older programmers - these kids are seeing people helping one another regardless of age or knowledge. All that's required is a desire to learn and participate.
Hacks -- I've referred to "hacks" several times already, and the hacks are an important aspect of MacHack. A hack, for the purposes of the conference, is a program that makes the Mac act in previously inconceivable ways. Hacks may modify standard Macintosh windows, replace the Mac's graphics with ASCII characters, or, in the case of one that didn't succeed this year, attempt to coerce the Mac OS to run on a 240 by 240 pixel monitor. Occasionally a hack may even become a commercial product, as with Leonard Rosenthol's Finder-based Web bookmark utility CyberFinder. Hacks are seldom polished, since they're usually created in the 72 hours before the Hack Contest, and they generally aren't useful. The goal with a hack is to perform a technical feat that will impress the other programmers, not to write finished code with a sophisticated interface. This year's entries in the Hack Contest were innovative and entertaining, and I'll cover them in detail in a separate article.
Thoughts -- Of all the conferences I've attended over the years, MacHack stands out as the most unusual. A few examples:
Time loses all meaning. Although some programmers stay up almost the entire conference, I wimped out every day between 3 AM and 5 AM, and got up sometime between noon and 3 PM. I found after a day or two that looking at my watch was pointless. Normally when you see that it's 1 PM, you think, "Hmm, maybe I should have lunch." At MacHack, you can glance at your watch, see that it's 6 PM, try to remember if you've eaten breakfast yet, and decide that it's less important than talking to someone about future Mac OS directions. To get a feel for how time passes, read Dave Johnson's chronology of MacHack 1996.
Everything caters to the programmer lifestyle. The keynote starts the conference at midnight. Free soda is provided at all times, and it's tricky to find any that doesn't have caffeine; Jolt Cola (with all the sugar and twice the caffeine) is always available. Except for the final night, when most people go to a late movie and come back to an ice cream social, boxes of pizza arrive every night at midnight. The conference's contract with the hotel reportedly states that the housekeeping staff won't knock on any doors before noon. This year, that fact wasn't properly communicated, and the first morning the housekeeping staff walked in on groggy geeks who had forgotten to put out Do Not Disturb signs.
Although MacHack has a full program of useful sessions, MacHack's focus is the hotel lobby. Picture a standard hotel lobby with small tables and chairs clustered around them. Then imagine four or five PowerBook G3s on each table, plugged into that table's Ethernet hub and power strip. People drift in and out of the lobby constantly, and a free chair is all the invitation you need to sit down, plug in, and start chatting with whomever is at the table. No one bothers to use a modem to dial out to the Internet, since the conference always has a dedicated Internet connection (256 Kbps ISDN this year) and internal Ethernet network.
Everyone at MacHack is technical, and the standard marketing and PR fluff that goes on at other conferences has little place at MacHack. No one at MacHack will try to sell you anything, and the attendees appreciate the low-key corporate sponsorship that helps cover the costs of the conference. Discussions take place at many different levels, and if you find one that's over your head, you can listen in and try to learn something or move on to another conversation.
Most conferences plan their locations carefully; witness the way Macworld Expo has moved to New York from Boston to focus on the New York media market. Other professional conferences pick exotic locales where attendees can happily golf or play tourist instead of attending the conference. MacHack remains in a hotel outside of Detroit where the only places you can walk to are a pair of fast food joints and a CompUSA. The point of MacHack is to be at MacHack, not to venture outside. Housing almost everyone in the same hotel helps this focus; no time is wasted commuting from and to other hotels or coordinating places to meet.
This year's keynote was given by Andy Ihnatko, a long-time Macintosh columnist and the self-described "42nd Most Popular Personality in America." Andy's keynote turned out to be essentially two hours of unparalleled Macintosh stand-up comedy. The MacHack organizers videotaped the keynote and hope to be able to make it available for sale, since any Macintosh fan will appreciate the humor. Andy also garnered serious points from the attendees by being one of the few keynote speakers to stick around for the entire conference and only the second to submit a hack in the Hack Contest.
There's a certain joy in the air at MacHack that's difficult to describe. Everyone understands that they're at MacHack to have a good time. The conference might prove extremely useful in other ways - ranging from job hunting to general education to being able to talk with an Apple DTS engineer for an hour about a specific problem - but fun is paramount. As one programmer whose code many of you have used put it, "It's my vacation. And it's a business expense."
Emulation -- It would be easy to recommend that everyone should go to MacHack, but that would ruin MacHack because the conference can't get much larger without losing its charm. Recognizing this, the conference organizers put a cap on attendance and, although they didn't quite hit it, they came close with 289 attendees this year. So for next year, when MacHack will once again be held near Detroit, from 22-Jun-00 to 24-Jun-00, I would encourage developers and serious Mac geeks with technical bents and outgoing personalities to attend.
The people who have organized MacHack have created something truly special, but I don't think it's necessarily unique. Other niche groups, from desktop publishers to database developers to independent consultants, could all learn from MacHack's example and create their own conferences that focus on letting the attendees interact with one another, rather than trying to shuttle them around between sessions like high school students. The best way to understand the secrets of what makes MacHack special would be to experience it firsthand, especially as a volunteer helping behind the scenes.
Article 2 of 3 in series
Most often, the primary news items that appear in the press after MacHack are the results of the Hack Contest, run by the MacHax Group at MacHack every yearShow full article
Most often, the primary news items that appear in the press after MacHack are the results of the Hack Contest, run by the MacHax Group at MacHack every year. The reason is simple - the results of the Hack Contest give the world a glimpse into the creativity of the Macintosh programmers when unfettered by reality, utility, or stability. Hacks generally aren't stable, useful, or even usable - they're just impressive feats of technical prowess. In fact, if a hack could be construed as having some utility while being demoed at the Hack Contest, someone in the audience will derisively yell, "Useful!" And if the programmer dips too far into promotion, the audience may reply with jeers of "Marketing!"
Since I first attended MacHack this year (see "MacHack: The Ultimate Macintosh Event" last week in TidBITS-487), I can't compare this year's Hack Contest to previous ones, but it was certainly a unique experience for me. The producers of the Hack Contest queued up a vast number of hilarious QuickTime movie clips to fill bits of time in between demonstrations, while contestants feverishly loaded new hacks onto the computers hooked to the projection systems. Also keeping the audience alert and happy were goodies thrown from the stage: the basic rule was to stay attentive or risk getting whacked upside the head by candy, a software package, a stuffed iMac, or one of the many basketball-sized inflatable plastic balls from Netscape that bounced around the entire conference.
Top Five Hacks -- This year's top five hacks had little in common, although there was no doubt which was going to win: Lisa Lippincott's Unfinder, which provides an Undo command in the Finder for non-destructive actions such as moving files, was a shoo-in for first place. Lisa had been one of the first to demo, and as she finished her introduction, moved a few files, and chose Undo from the Finder's Edit menu, the crowd gave her a full-bore standing ovation (after a few catcalls of "Useful!"). I hope Lisa's hack shames Apple into adding the feature to a future version of the Mac OS. It wouldn't be the first time a hack contest entry led to improvements in the Mac OS.
The prize for the best hack is the coveted Victor A-Trap, a large rat trap whose name has been modified to be a perfect pun. First, it's made by the Victor Corporation and goes to the winner. Second, it's named "A-Trap" (the R and T in RAT are excised with an X-Acto knife) after the initial character of the hex values for trap addresses used by programmers to patch the Mac OS. The contest organizers also get a kick out of coercing the winners into prominently displaying a large rat trap for friends and coworkers to see. For me at least, it also seemed a slight nod to the concept of building a better mousetrap.
Eric Traut's Out of Context Menus application took second place by providing a set of contextual menu items that aren't normally provided for Finder windows, including Gaussian Blur, Compress, Duplicate, and Slide (all of which visually modified the contents of the window). A more involved command, New Game, required the creation of Left Paddle and Right Paddle folders in the window first, after which choosing that command caused the folders to play a game of Pong. Eventually something caused a problem, so Eric chose Restart from the contextual menu, seemingly restarting the Mac OS within only that window.
Ed Wynne's DesktopDoubler came in third place. DesktopDoubler essentially fooled a PowerBook G3 into thinking it had a second screen attached, but went one step further than most virtual screen utilities by fooling the Mac OS into thinking a second monitor was attached instead of virtually enlarging the existing monitor or faking a larger desktop. As a result, the Monitors & Sound control panel saw the second screen, so you could arrange it however you wanted. DesktopDoubler also put a menu bar and certain desktop items like the Trash on the secondary screen. Movement between the two screens was accomplished by moving the mouse pointer between them.
Fourth place went to Jorg Brown and Ned Holbrook for MacJive, a politically incorrect extension that caused all text in every application on the Mac to be translated into fake ghetto-speak. A variety of these translations exist as CGIs through which you can run Web pages, but seeing the entire Macintosh interface so translated increased the effect. For MacJive, Jorg and Ned won a large frozen turkey, in part, I suspect, just to see how they'd attempt to get it home.
Filling out the top five was Paul Baxter's PatchMaker, a programmer's tool that took care of the basic support code necessary to create each of 1,258 68K and PowerPC patches, enabling the programmer to concentrate on the hack itself. Like Unfinder, PatchMaker garnered some cries of "Useful!" from the audience, and at least one person was considering writing next year's hack using PatchMaker to get started.
More Hacks -- Although the above five hacks took home top honors, other hacks deserve public recognition (and I'll probably make some mistakes here, due to taking notes in the wee hours).
In a successful attempt to avoid "Useful!" cries, Leonard Rosenthol and Miro Jurisic wrote Mactive Desktop, which used Microsoft Internet Explorer, Netscape Communicator, or iCab to put live Web pages on the Macintosh desktop, much like the Windows Active Desktop. Also truly useless was Bill Hubauer's "CD-ROM Drive You Crazy" which caused the CD-ROM trays on Macs elsewhere on the network to move in and out. Jesse Donaldson and Katherine Smith entered ReaderMouse, which used speech synthesis to read the word under the mouse pointer, reportedly performing OCR on the pixels on the screen.
Richard Ford, previously Apple's Open Transport product manager, showed HUF (Hotline User Frustrator), a hack that made use of the PacketShaper, a neat device made by Packeteer, the company where Richard now works. Responding to complaints that Hotline users were flooding MacHack's 256 Kbps Internet connection with downloads, Richard set the PacketShaper to restrict Hotline users to 300 baud, then showed real-time graphs of how his hack had improved network throughput for other protocols. Another popular Internet hack, Geo Killer from Mark Lilback, automatically closed those annoying pop-up windows that appear when visiting Web sites hosted by GeoCities; it could be configured to close pop-up windows from any site.
Apple DTS's Andy Bachorski continued a theme from last year, when he wrote a version of BrickOut in MacsBug. This year, he used BBEdit to write ASCII Invaders, a version of Space Invaders. He created the screen display by making a special font, and handled the animation entirely through text manipulations in BBEdit.
Keynote speaker Andy Ihnatko also stayed with the kind of hacking he had shown in his keynote. Using an ADB/IO device and some custom AppleScript scripts, Andy wrote Skinner Cubicle (a takeoff on the Skinner box used in behavioral research). The basic idea was that sometimes you need to provide positive or negative feedback to cubicle dwellers; one script caused a motorized candy machine to dispense a piece of candy, and another fired a toy dart gun.
Finally, several people showed Y2K-related hacks, the most amusing of which prevented the Mac's clock from ever ticking over to midnight on January 1st. Instead, every time it reached 11:59:59, it reset to 11:59:00. Good thing we won't be needing that one.
Yoot Hacks -- The student hacks ranged tremendously in sophistication, which wasn't surprising, given that the youngest entrant was seven year-old Rachel Green while several other contestants were in their last year of eligibility for yoot status, as defined by graduation from college. Rachel's hack used AppleScript to make two icons chase each other around the screen. On the other end of the spectrum was Avi Drissman's Balloon Preview, which used QuickTime to preview images and movies in help balloons that popped up when he pointed at the files. Ned Holbrook's CD Namer was also quite sophisticated; when you inserted an audio CD, CD Namer automatically figured out which CD it was, looked it up in an Internet database, and filled in the disc and track titles.
Other yoot hacks were quite impressive, including Lucius Kwok's Prose Posse, which rewrote text files based on word proximities, and a three-person yoot hack called Altered States, which could apply a number of garish effects (especially garish at 2:30 AM) to windows. Ben Furnas's The Creep hack implemented a simple dialog box-based network chat client using program linking.
One yoot hack made its way into MacHack legend. Matt Linden's AppleScript-based "Is it a folder?" hack was supposed to identify either files or folders selected in the Finder. If you pointed at a folder, it said out loud "This is a folder." and displayed a dialog box containing the same words. Unfortunately for Matt, a bug caused it to display the same dialog box when he clicked a file, though the spoken words correctly stated that "This is not a folder." Unable to believe his code wasn't working, Matt tried and tried to get his hack to work, pointing at numerous different files. The sleep-deprived audience found this hilarious, and badges labeled "I am not a folder" appeared the next day, and Steve Kiene of MindVision made a t-shirt that proclaimed, "I am a folder and I've got the documents to prove it!"
AltiVec Hacks -- A perk of attending MacHack was that Apple sent a few prototype G4-based Power Macs for the developers to hack. The PowerPC G4 is essentially a souped-up G3 with the AltiVec vector processor, an addition to the chip that radically speeds up certain types of code. Most of the AltiVec hacks, including AltiVec expert Doug Clarke's "42," showed code running both normally and with the AltiVec processing turned on. In one instance, using the AltiVec instructions ran 188 times faster, although Doug said speed increases of 2 to 4 times were more likely with minimal work.
Other Platforms -- A couple of hacks ran on top of Mac OS X Server, including one called Blue Box Spy, which let you see what was happening in the Blue Box (where the Mac OS was running) even when the Blue Box was hidden. Andrew Stone also entered a hack that provided a graphical interface to a chat-based poker game. The most serious Mac OS X hack was entered by Apple engineers who wrote a Mac OS X device driver to enable a Mac running Mac OS X Server to use a Windows Theater TV tuner they'd just bought at CompUSA. And for those who want to get used to the NeXT interface early, Jonathan "Wolf" Rentzch wrote Carbonized Menus, which hid the normal Mac OS menu bar and replaced it with NeXT-style floating menus.
A few Palm OS hacks were also shown, including an impressive one from 3Com/Palm's Steve Lemke and Jesse Donaldson that not only created a remote control that controlled a PowerBook's CD-ROM drive via infrared, but also used a serial connection to display on the Palm's screen a DVD movie playing on a PowerBook. Steve and Jesse awarded the best Palm hack to Andrew Downs, for his P1 Preview, which simulated the Finder on the Palm.
Getting the Hacks -- You can buy a CD containing all the hacks for $20 via the MindVision online store at the URL below (profits go toward next year's conference). The MacHack Web site also lists the hacks and includes the top five for download.
Article 3 of 3 in series
Judging from much of the email we at TidBITS receive, many Macintosh owners desperately want to provide feedback to Apple about the Mac OS, Apple's advertising, Macintosh hardware specifications, hardware color choices, and almost anything else related to AppleShow full article
Judging from much of the email we at TidBITS receive, many Macintosh owners desperately want to provide feedback to Apple about the Mac OS, Apple's advertising, Macintosh hardware specifications, hardware color choices, and almost anything else related to Apple. In one respect, Apple should be flattered - the fact that Macintosh users care enough to want to offer their ideas and opinions is impressive. But Apple is a huge company and has no official channel for users to pass on their feedback. The zeitgeist of the industry does filter into the company through indirect means; stories in the press, friends of Apple employees, comments from Apple dealers, the occasional transmission from outer space, and so on.
Part of the problem is simply Apple's size. Even if there were an email address to which you could send comments (the previous attempt at this, <email@example.com>, appears defunct), it would be difficult for anyone to distribute comments to the appropriate departments, much less the proper people within those departments. Apple has too many employees and too much turnover and movement for anyone to direct feedback effectively.
As much as Apple may not have effective ways of soliciting or managing user feedback, the company does listen, at least sometimes, to Macintosh developers. Apple's Worldwide Developers Conference (WWDC) offers one forum for that, but Apple's goal at WWDC is as much to evangelize Apple technologies as to accept feedback on those technologies. But there is another way.
Bash Apple -- A long time ago at the MacHack developers conference, there came to be this event called "Bash Apple." As the oral tradition relates, a bunch of developers were sitting around at MacHack bashing on Apple for some stupidity or another. After a bit, one person in the group, a new Apple employee named Jordan Mattson, said, "Look, I'm a nobody at Apple, but I'll write all this stuff down and when I get back, I'll see if I can find someone appropriate to tell it to. No promises, no guarantees." And he did, though it was unclear if his efforts had any effect back at Apple. That was immaterial, though, because the developers had had a chance to vent at someone from Apple and, feeling much better, they stayed up the rest of the night writing hacks so useless they produced awe and admiration among the other developers at MacHack (for this year's hack contest details, see "The MacHack Hack Contest 1999" in TidBITS-488).
The developers so enjoyed having someone at Apple to vent to that they did the same thing the next year, and the year after that. These sessions became formalized under the rubric of "Bash Apple" and grew to include numerous Apple engineers, many of whom had been independent developers in previous years. Jordan even became immortalized in the MacHack argot in the phrase "It's Jordan's fault," and though of course essentially none of Apple's problems actually were Jordan's fault, he continued to play. The sessions continued to provide a forum for frustrated developers to let off steam, but equally important, they gave Apple folks ammunition to take back and say, "Look, it's not just me saying this - 200 developers are also ticked off about it."
Apple Handshake 1999 -- In recent years, Bash Apple (saddled this year with the horrible moniker "Apple Handshake Session") has evolved to the point where a senior Apple person fields questions and criticisms from developers, backed up by various other Apple folks in attendance. This past MacHack in June (see "MacHack: The Ultimate Macintosh Event" in TidBITS-487) was no exception, with Apple's vice president of Mac OS engineering, Steve Glass, fielding most questions with assistance from other Apple employees. For instance, in response to a question regarding whether Apple planned to release any more Appearance themes, Apple evangelist Tim Holmes stated unequivocally, "As I've said numerous times in numerous places, there is no future for themes. None, nada, zip, zero," and sat down, only to bounce to his feet a second later to reiterate the more carefully phrased, and officially blessed version, "Apple Computer has no plans to offer additional themes, either now or in the future, but the company reserves the right to change its mind, blah, blah, blah."
Every now and then during the session, important bits of information either became public or were emphasized. For example, Steve Glass was adamant about how he was clamping down on shipping independent components of the Mac OS separately from full Mac OS releases. He felt that shipping different versions of Open Transport, for instance, separately from the Mac OS itself made for configuration and testing nightmares; plus it could cause problems for users who were mixing and matching components in combinations that Apple hadn't tested. In addition, in response to another query, Tim Holmes made the important point that although Mac OS 9 will have multiple user support in the sense of both individual and shared preferences, the feature is aimed at home and small office users, not large installations with many users.
For the most part, though, I got the impression that developers weren't entirely happy with the session, perhaps because even though they were talking with an Apple VP, he wasn't able to be concrete about much. Steve Glass could and did respond to issues surrounding Mac OS 8.x, since that's his team. He was also able to offer standard industry platitudes about concerns that either were outside his field (Mac OS X, hardware) or that undoubtedly are not yet even decided at Apple. Trade-offs, resource allocation, ship time, investigating the issue now... all of these meaningless phrases came forth at one time or another. But what should he have said? The problem with those industry platitudes is that they're often true - there are trade-offs between offering individual component releases versus unified system releases; Apple does have to pay attention to how they allocate engineering resources to future projects versus maintaining backward compatibility to System 7.x; and so on. In short, Steve Glass was incapable, through no fault of his own, to offer any sort of official assurances about how, for example, Steve Jobs may have traded his soul and a total lack of commitment for Java 2 for Apple's recovery. Even if Steve Glass knew that Apple had decided to ignore Java 2, he wouldn't break the news at MacHack.
Top Ten Developer Issues -- In the last few years, the organizers of MacHack decided to create a list of the top ten developer issues, rightly believing that it would be easier for the press to write about than a two-hour Q&A session. The list, voted on by the gathered attendees, was an attempt to collect and prioritize the concerns held by the Macintosh development community. Here then is a slightly edited version of this year's list, with links to relevant TidBITS articles where possible.
1) MacsBug support: The MacsBug debugger is a critical Macintosh development tool. Developers need Apple to dedicate engineering resources to this tool and to new ones like it. If you're interested in what it can do for you, check out Geoff Duncan's three-part series on MacsBug.
2) Greater stability and easier debugging: Developers need increased reliability and greater ease in debugging software on Mac OS. Apple has done a good job of improving stability since System 7, but more stability is always welcome.
3) Mac OS X look and feel: Developers want Mac OS X to look like a Macintosh, not like a Unix workstation. We touched on this topic with "Mac OS X or Mac OS NeXT?" in TidBITS-483.
4) Documentation improvements: Developers need technical documentation to be available sooner, and to be more complete, accurate, and accessible. Although our "Death of Documentation" article focused on user documentation, many of the issues are similar.
5) Better mouse and keyboard: Developers believe that high-end Macs need a better standard mouse and keyboard with a full set of keys. Smaller is not always better with keyboards. Amazingly, the new Power Macintosh G4 does not include an improved keyboard and mouse.
6) Machine differentiation for support needs: Developers need Macs to be more clearly marked because support staffers need to identify users' machines easily. I raised this issue at the session and was gratified to see that developers shared my concern. See "Macintosh Model Implosion: What's in a Name?" in TidBITS-485.
7) Extending the OS: The "patching" mechanism for extending the Mac OS in unplanned ways is important for many reasons, including providing disability access. Developers need a similar mechanism in Mac OS X.
8) Cleaning up Mac OS: Developers believe that Mac OS would benefit from being further cleaned up. Removing vestigial code from the OS would improve memory footprint and performance, including faster booting.
9) Java: Developers need a clear direction on Java. A commitment from Apple regarding support for Java and Java 2 would be greatly beneficial.
10) Release discontinued development tools as open source: Many developers still rely on tools that Apple no longer supports, like MPW. Releasing such tools as open source would allow developers to maintain and improve the tools they find essential.
Tracking the Feedback -- One aspect of this year's Bash Apple session that was missing was a recap of the previous year's Top 10 list. It's instructive to see both how Apple has responded to items on the list and how developers' opinions of what's important changes from year to year. I'll be sure to see how this year's list fares at MacHack 2000, by which time we might have various new Macs, Mac OS X, and inconceivable policy changes from Apple.