<div id="popup_box_thanks" style="display:none" onClick="close_popup_thanks('popup_box_thanks', 'ts')"><br>Thanks for submitting your tip! All submissions are moderated by an editor before appearing online. We've reset the form so you can enter another tip. Or you can close the tip submission box. <div class="x_close" id="thanks_upper_right"><a href="javascript:void(0)" onmousedown="close_popup_thanks('popup_box_thanks', 'ts'); return true;">Close</a></div></div>
<div class="tbf_row"><div class="tbf_wide_extra_top not_bold">Please submit only technical tips that will help other TidBITS readers better use their Macs, iPhones, and related software and hardware. All product announcements should be sent to <a href="mailto:releases@tidbits.com">releases@tidbits.com</a>.</div></div>
<div class="tbf_left">URL</div><div class="tbf_right"><input type="text" value="" name="tip_link_url" tabindex="3"><span class="tip_description"><br>Enter the URL to a Web page that supports your tip.</span></div>
</div>
<div class="spacer"></div>
<div class="tbf_row">
<div class="tbf_left">Linked text</div><div class="tbf_right"><input type="text" value="" name="tip_link_label" tabindex="4"><span class="tip_description"><br>Enter the name of the page linked above.</span></div>
<div class="tbf_wide"><input type="submit" value="Preview Your Tip" name="preview_tip" onClick="fill_preview('tipbits_enclosure_preview', 'ts', this.form); return false;" tabindex="7"> <input type="submit" value="Send Us Your Tip!" name="submit_this_tip" onClick="handle_tip_submission('ts', '', this.form, 'tip'); return false;" tabindex="8"></div>
</div>
<div class="spacer"></div>
<div class="tbf_row">
<div class="tbf_wide"><span class="fine_print">When you submit a tip, you give us permission to use it. Read <a href="javascript:void(0)" onClick="generic_show_hide('tip_terms')">our terms</a> for more details. All submissions are reviewed before publication.</span></div>
<div class="tbf_wide"><span class="fine_print">Our terms: By submitting a tip, you agree to assign TidBITS Publishing Inc., a non-exclusive, worldwide, perpetual license to reproduce, publish, and distribute your tip in connection with the TidBITS Web site and associated products in any media. You agree that you created the content you submitted, and that you have the right to assign us this license. You give us permission to use your name, but your email address won't be publicly displayed or shared. We review all submissions before publication, and reserve the right to select which submissions we feel are appropriate for our readers and to edit those we publish.</span></div>
<div id="comment_thanks" style="display:none" onClick="close_popup_thanks('comment_thanks', 'comm')"><br>Thanks for submitting a comment! Please check your email for a link that, when clicked, will verify that you're a real person and cause your comment to appear immediately. <div class="x_close" id="comment_upper_right"><a href="javascript:void(0)" onmousedown="close_popup_thanks('comment_thanks', 'comm'); return true;">Close</a></div></div>
<div class="tbf_wide"><span class="fine_print">Our terms: We reserve the right to edit or delete any comment, so please post thoughtfully. We use your email address <i>only</i> to send you a one-time verification message confirming that you posted this comment. We also store your address to allow you to verify using other Web browsers in the future. For more info, see our <a href="http://db.tidbits.com/privacy.html">privacy policy</a>.</span></div>
<li><a href="/feeds/tidbits.rss" title="Subscribe via RSS" class="gettb">RSS <img src="/images/feed-icon-12x12.gif" width="12" height="12" border="0" class="nav_img" alt="Subscribe via RSS"></a></li>
<li><a href="http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=276986548" title="Subscribe to the podcast" class="gettb">Podcast <img src="/images/feed-icon-12x12_podcast.gif" width="12" height="12" border="0" class="nav_img" alt="Subscribe to the postcast"></a></li>
<li><a href="http://www.twitter.com/TidBITS" title="Get Article Updates via Twitter" class="gettb">Twitter <img src="/images/feed_icon_12x12_twitter.png" width="12" height="12" border="0" class="nav_img" alt="Get Article Updates via Twitter"></a></li>
<li><a href="http://www.facebook.com/pages/TidBITS/195314925519" title="Go to the TidBITS Page at Facebook" class="gettb">Facebook <img src="/images/feed_icon_12x12_facebook.gif" width="12" height="12" border="0" class="nav_img" alt="Go to the TidBITS Page at Facebook"></a></li>
<li><a href="javascript:void(0)" title="Sections" class="tabhead" onClick="return showhide('articleslist')">Sections <span id="articleslist_triangle"><img src="/images/nav_triangle_open.gif" width="9" height="9" border="0" class="navtriangle" id="articleslist_tri_image" alt="Click to show or hide the contents of this section."></span></a></li>
<li><a href="javascript:void(0)" onClick="return showhide('stafflist')" title="Staff" class="tabhead">Staff <span id="stafflist_triangle"><img src="/images/nav_triangle_closed.gif" width="9" height="9" border="0" class="navtriangle" id="stafflist_tri_image" alt="Click to show or hide the contents of this section."></span></a></li>
<li><a href="javascript:void(0)" title="Issues" class="tabhead" onClick="return showhide('issuelist')">Weekly Issues <span id="issuelist_triangle"><img src="/images/nav_triangle_closed.gif" width="9" height="9" border="0" class="navtriangle" id="issuelist_tri_image" alt="Click to show or hide the contents of this section."></span></a></li>
<li><a href="javascript:void(0)" onClick="return showhide('abouttidbits')" title="About TidBITS" class="tabhead">About TidBITS <span id="abouttidbits_triangle"><img src="/images/nav_triangle_closed.gif" width="9" height="9" border="0" class="navtriangle" id="abouttidbits_tri_image" alt="Click to show or hide the contents of this section."></span></a></li>
<div class="center_top">Thoughtful, detailed coverage of the Mac, iPhone, and iPad, plus the best-selling <a href="http://www.takecontrolbooks.com/?pt=TB-TAGLINE" style="color:yellow">Take Control</a> ebooks.</div>
<!-- begin centercolumn -->
<div id="centercolumn">
<!-- begin rightcolumn_container -->
<div id="rightcolumn_container">
<!-- begin rightcolumn -->
<!-- rightcolumn is embedded within centercolumn so featured text wraps around it -->
</div><!-- end tearoffbox_wide_container for watchlist items -->
<!-- begin tearoff box wide -->
<div class="tearoffbox_wide_container">
<div class="tearoffbox_wide_tips">
<div class="tip_display">
<div class="tips_sponsor_logo">
</div>
<h6>Access Street View in iPhone Maps</h6>
<p><p>Finding the Google Street View feature in the iPhone 2.2 version of Maps is tricky - there's no button for it. If you're viewing a map that you think might have a street view, drop a pin (tap the curled paper icon at lower right, then tap Drop Pin or Replace Pin if a pin is already being used). An orange person icon at the left of the pin's information line is dark and can be tapped if Street View information is available.</p></p>
</div>
<div class="tearoffbox_wide_bottom_tips">
<div style="padding-bottom:35px"><div class="tip_display" style="float:left"><p><br><a href="/tipbits/106">Link to this tip</a></p></div><div class="tip_display" style="float:right; width:150px">
<div class="tbf_wide_80" id="hc_rc_1438">To help us avoid automated posts and misuse of our site, please enter the words below.</div><div class="x_close_row" id="hc_upper_right2_1438"><a href="javascript:void(0)" onmousedown="HidePopupContent('hc_1438', 'hc', '1438'); return true;">Close</a></div>
<div class="featured_meta"><div class="meta_article">03 Jan 1994 | <a href="/article/2293?print_version=1">Print <span class="shift_up"><img src="/images/printer_icon.gif" alt="Printer-Friendly Version of This Article" border="0" width="9" height="10"></span></a></div></div>
<H2>The User Over Your Shoulder: The New Technologies Treadmill</H2>
<div id="article_box_1438"><P>For a mere $250 plus shipping, you can order from APDA (Apple's developer-support wing) a year's subscription to the Developer Mailing. Each month you receive a newsletter and a CD.</P><P>The CDs are filled with stuff that Apple wants to put into the hands of software authors. Some of it is established system software or beta-releases of future system software (recent CDs have included international systems, LaserWriter 8.1.1, System 7.1 and its Update 2.0.1, AppleScript, and Speech Manager). Some of it is reference documentation (all the old and new Inside Macintosh, and complete tech notes). Some of it is sample code and programming aids.</P><P>You don't have to be a real developer; anyone can subscribe (contact APDA at <<A HREF="mailto:apda@applelink.apple.com">apda@applelink.apple.com</A>> if you're interested). A lot of non-developers who do subscribe doubtless just crave the CDs. But just as fascinating is how the Mailing, including the newsletter, lets you look over Apple's shoulder as it pep-talks developers towards the new system technologies looming on the horizon. It occurs to me that if I were a developer I would doubtless need such pep-talks.</P><P>Even in the good old days (whenever they were), writing even a simple Macintosh application was no mean feat. There are many "managers" built into the system to help you, but they don't do the work for you, even when you're trying to do something that any Mac application needs to do. It's hard to describe, and I'm no expert, but I think it's fair to say that the interplay between what the system software does and what you do in order to achieve even the simplest task is weird. Something as rudimentary as putting up a dialog box, requires a certain level of sheer trickery. A task as common as maintaining a floating palette is so difficult via the standard high-level Window Manager calls that an article in a recent issue of Apple's develop magazine teaches you to hack your way completely around such calls.</P><P>These days, new "managers" and capabilities are cropping up at a perilous rate. Each requires the programmer to learn new skills. None can be trivially incorporated into applications; the complexity of the interaction between them all, and between them and your program, means the learning curve angles steeper as the programmer climbs. The problem is that if one wants to stay in business one must keep climbing, because a competitor is certainly going to incorporate the new features, and you'll be left behind if you don't as well - as Apple gleefully points out in the newsletter.</P><P>This makes me wonder whether Apple is doing the right thing. Perhaps I'm just an Old Curmudgeon, and I certainly wouldn't want to press my views: I'm not a developer, nor even much of a programmer. But in a quiet way, and perhaps for sake of argument, I'm curious as to whether all this pulling of rugs from under existing Mac applications can be good for the industry, and particularly for the users, of whom I am one.</P><P>Just consider a tiny bit of what is around the corner. With PowerPC, the basic bottom-level fact about Macintoshes, the use of the Motorola 680x0 processor, is about to go out the window. Everything has to be rewritten and recompiled if it isn't to be content with running in a mere emulator mode on the new, faster machines. With QuickDraw GX, the most basic act of showing text and graphics on the screen must be implemented in an entirely new way, and the printing and font models are going to change radically. In short, it isn't just a matter of new capabilities piled upon the old; the impending upheaval involves the underpinnings, everything that is most fundamental and long-standing in the Macintosh world.</P><P>Then there is the problem of many machines and many systems. Time was when Apple prided itself upon the mutual compatibility of its then-small line of Macintoshes. The system software cleverly sheltered your program from worrying about differences between the ROM of a Mac Plus and that of Mac II. But now there are rudimentary splits between the hardware and software platforms. System 7 lets you make all sorts of Toolbox calls that System 6 can't handle. These are much more convenient, and if I were writing a program for my personal use I would write it for System 7. But if you're a developer, unless you want your program not to run on many of the lower-end the machines, it must be two distinct programs in one, one making System 6 calls and the other making System 7 calls. The same is true of the hardware. Remember all the programs that broke when the Quadras appeared? My copy of ON Location still doesn't work if a StyleWriter II driver is the current Chooser printer. And how about the expansion-slot nightmare?</P><P>My point is simple. If the industry of developers is to keep up with all the changes Apple is throwing at them, which it must do to stay healthy, a lot of folks are going to have to do a lot of work. That work is going to take time, in the form of person-hours, mythical or not. Who pays for those person-hours? Why do I think it's going to be the user?</P><P>Apple's attitude in this regard does not encourage me. In the newsletter that came with the latest Developer Mailing, an Apple guru jokes that "God was able to create the world in seven days because he didn't have an installed base." As far as I'm concerned this joke, apparently a current hit around the Apple campus, is on a par with Hermann Goering's notorious quote, "When I hear the word Culture, I reach for my revolver." The very fact that anyone finds it amusing, or even clever, sends a shiver of fear up my spine. In the same newsletter, the concept of "current" Macintosh models is used to mean (as far as I can gather): Performa 410, 460, 470, 550; LC II, III, 475, 520; Quadra 605, 610, 650, 950, and the two AVs; plus some PowerBooks and Duos, and the Color Classic II. I get the idea that as far as Apple is concerned, all the machines in my department (Pluses and Classics running System 6, a Classic II, and a Quadra 800) are bad dreams they wish would go away.</P><P>Indeed, my own machine at home is starting to feel the bad vibes. It's a poor old LC. It was one of the first lower-priced Macs, and when I bought it, a couple of years ago, I was part of the new revolution, helping Apple down the path of higher volume and smaller profit margins that helped save the company into the 90s. Since then I've accelerated my LC and filled it with RAM to its maximum capacity, and I'm still marginalized by the current system software. Judging from the upcoming system software, we're all supposed to have 20 MB of RAM. Too bad if some of us can't. What are we supposed to do, throw out our machines and start over? Does Apple think we're made of money?</P><P>I'm not trying to be a Luddite or a nay-sayer. I drool as much the next person over the prospect of new gee-whiz technologies. And I also think - and this is important, so don't get me wrong - that Apple probably <EM>needs</EM> to do what it's doing in order to keep going. But I have this sneaking feeling that with a lot of old and slightly middle-aged machines getting the cold shoulder, and a lot of costly software upgrades in the works, the user's pocketbook is going to feel the shaft. Certainly it's going to make the $250 it costs me to be the User Over Your Shoulder look paltry.</P><P>In the mean time, if the creek don't rise, and if the Thought Police don't get me, and if I don't get too much hate mail, I might be back from time to time with some more musings on where Apple thinks it's going, and whether it's good for us if it gets there.</P><!-- The User Over Your Shoulder: The New Technologies Treadmill Matt Neuburg --></div>
<!-- end article text -->
<!-- PayBITS -->
<p> </p><div class="sponsorbox">
<div class="sponsortext"><A HREF="http://nuance.com/dragon/mac"><IMG SRC="http://db.tidbits.com/images/badges/dragondictatelockup_vertical_onlight.png" ALT="" HEIGHT="50" WIDTH="50" BORDER="0" ALIGN="left"></A>Dragon speech recognition software for Macintosh, iPhone, and iPad!<br />Get the all-new Dragon Dictate for Mac from Nuance Communications<br />and experience Simply Smarter Speech Recognition.<br />Learn more about Dragon Dictate: <<a href="http://nuance.com/dragon/mac">http://nuance.com/dragon/mac</a>></div>
