Apple II series

Latest

  • Weird and amazing Macs that aren't exactly Macs

    by 
    Erica Sadun
    Erica Sadun
    01.20.2014

    If you haven't heard of the upcoming 1984-2014 Maciversary, well either you aren't paying attention or perhaps you have an actual life. Us? We've been going back and forth talking about this thing for the last month. And one of our most contentious issues involves what exactly counts as a Mac. Some systems are obviously Macs. This? This is a Mac. It's a happy Mac! This? This is not a Mac. It's an Apple II. And while many laypersons might not be able to differentiate between a Mac and an Apple II ("Most people now don't know the difference between an Apple and a Mac. Maybe the people reading our site, yes, but not an actual layman.") we can state for certain that this is completely and utterly not a Mac. This is a Macquarium, a phrase coined by Andy Ihnatko. It is not a Mac, although it is compatible with Objective Sea Life. This, on the other hand is basically a Mac. It's an Apple Lisa, the personal computer that preceded the Macintosh. In fact, the ultimate Lisa was sold as the Macintosh XL. The Lisa offered many of the same user interface features as the Mac and was targeted toward business users. This too, is basically a Mac.It's a Xerox Alto, designed at Xerox PARC and dates back to the early 1970s. It used a mouse-driven GUI-based system, and more or less inspired Apple Co-founder Steve Jobs during a site tour. It provided many of the same look and feel strengths that later showed up on the Mac. This is also basically a Mac. It is a NeXT cube. You don't see a screen in this image from Wikipedia, but if it were connected, you'd recognize a lot of the OS. That's because the NeXT basically ran OS X. It only took a bit over a decade for that technology to return to Apple after Jobs went on a quick run out to pick up some nacho chips and started a brand-new company before returning to Apple with orange fingers and the beginnings of OS X. While he was gone, someone at Apple built this. It's not a Mac. It's not even close to being a Mac. But eventually it inspired people who got around to shoving Mac's OS X operating system onto the iPhone (which, too, is a Mac). This is, of course, not to be confused with these, which are also Newtons but which offer far less computational efficiency. Certainly, this is not an exhaustive list of what is and is not a Mac. There were Power Computing Macs, Hackintoshes, retro bubble Macs, extremely beige Mac IIs and many, many more. All of them properly Macs. Today, we own our impossibly thin MacBook Airs, our super powerful Retina Pros and our beloved Mac minis. Here's looking forward to the next 30 years of Mac. Do you have any strong opinions on what is and is not a Mac? Share them in the comments. All images are courtesy of Wikipedia.

  • Origin Stories: Steve Sande

    by 
    Steve Sande
    Steve Sande
    08.06.2013

    I certainly didn't start my career with plans to become a blogger and editor at one of the world's most active Apple websites. When I was a child dreaming about a future career path, computer science barely registered on the "What I want to do when I grow up" list since only corporations owned room-sized mainframes at that time and there was no such thing as a home computer. The first time I had any physical contact with a computer was in 8th grade in Aurora, Colorado in the Apollo moon landing year of 1969. The Aurora Public Schools had purchased a Data General Nova (see console photo of a similar model at top of this post) in that year for accounting and scheduling purposes, and some brilliant person came up with the idea of buying some Teletypes that could be used as dialup terminals to allow personnel at the schools to access the main computer remotely. Well, the administrators and teachers at the school weren't all that interested in computers, so guess who started using the Teletypes and Nova to learn how to program in BASIC? The students. Since they wouldn't let us save our programs to paper tape (that would come in about two or three years), any programs we ran were usually quite short out of necessity – we'd type 'em in, run them, try to figure out what the TOO MANY NESTED GOSUBS error meant, and then start all over again. It was fun, but frustrating with no real way to store the programs permanently. In 9th and 10th grade, I was only able to play rarely with the Nova or whatever computer they may have purchased as an upgrade. But when the school announced in 11th grade that the regular algebra class would also be offered in a "computer algebra" version providing access to the school system's minicomputer, I jumped on the opportunity to have a full semester of working with ... the future! Things were a little better at that point. We could save our programs out on paper tape, kind of the "floppy disk" of the era. I think part of the reason we wanted to save to paper tape was that the tape punch created some very good confetti for high school football games... About this time I became very interested in two things; transportation engineering and writing. I had a wonderful high school English teacher by the name of David Faull (still alive and kicking) who really taught me how to write, something I'd need to do in college in those pesky elective courses. I had decided to go into Civil Engineering, and was accepted at the University of Colorado at Boulder. Every engineering student at the time had to take an introductory computer class – CS 101 – in which they were introduced to two things: punch card input and FORTRAN IV. There was nothing worse than sitting down at a keypunch machine with a handwritten FORTRAN coding form, typing in several hundred cards, all of which needed to be read by a machine in order and without typos for your program to run. I can recall hearing of several computer science grad students who had nearly committed suicide after having ultra-long programs scattered to the wind when they accidentally dropped boxes of punch cards... One of my best high school buddies, Rick Brownson, was a student at CU at the same time in the Electrical Engineering department, and I recall that in 1976 he introduced me to an amazing game –- Lunar Lander –- that displayed vector graphics in real time onto a round green-screen terminal. We wasted many a weekend hour playing that game in one of the EE computer labs. Rick also introduced me to the nascent world of personal computing around that time, as he and I soldered chips into a MITS Altair 8800 kit in late 1975. I really wasn't all that impressed with the Altair, since when we finished it there was no way for us to connect it to a display (usually an old TV), and we had no keyboard for it. So we flipped switches on the front of the device to enter 8080 opcodes and then looked at the LEDs to see the results. I remember taking a weekend drive to Albuquerque, New Mexico in 1976 to go to a Altair convention of some sorts; the highlight was getting a pirated copy of Bill Gates' Altair BASIC on paper tape from another attendee. At the time I graduated from engineering school in 1978, word was getting out about Apple, but at the time I really didn't see any reason to buy a computer. Even while I was working in my first job and going to grad school, I refused to buy a computer. When I was able to get a Commodore VIC-20 for about $300 I bought one, then when Commodore reduced the price on the C-64 to about $250 the next week, I returned the VIC-20, got a refund, and picked up a Commodore 64. After a short amount of time I found myself hooked. I bought an Epson printer, got the cassette tape drive, and bought the height of communications technology at the time – a 300 baud modem. I quickly found myself on some of the early bulletin board systems of the time. But the Commodore 64 wasn't a "real computer", so when IBM compatible devices started hitting the market I went out and bought a Sanyo MBC-555 PC clone complete with two floppy drives (a Sanyo MBC-550 with only one floppy is shown below)! This is where I got my first introduction to business software, with WordStar as a word processor and CalcStar as a spreadsheet. At this time, I was working for a natural gas pipeline company called WestGas. The company was a subsidiary of a larger electric and gas utility (Public Service Company of Colorado, now part of Xcel Energy), and as a subsidiary we had of control over our destiny. In the fall of 1983, the Vice President of our company came to me to see if I would perform a study of possible uses for personal computers in our company and create a five-year plan to budget the introduction of those devices, so I jumped to the task. Everything was based on costs and benefits, and a calculated rate of return on the investment in IT. In retrospect, a lot of my numbers were probably quite suspect, as they were based on estimates of time savings that most likely never occurred... The final study saw a need for no more than about 15 PCs over the next five years as well as a handful of dedicated IBM DisplayWriter word processors. About the time that my study was completed, there was a lot of speculation in the computer world about Apple's forthcoming Macintosh. I was interested in seeing one, so a few days after they were introduced my boss and I went over to a Nynex Business Center store to take a look. While the mouse, the bitmapped display, and the 3.5" floppy drive were all amazing, the lack of memory (128K) was a real turnoff. Still, I felt as if I had seen the future, and I vowed to get myself a Mac if they ever built a model with more RAM. Towards the end of the year Apple introduced the 512K "Fat Mac", and the company was doing a "Test Drive A Mac" promotion where you filled out loan paperwork, took a Mac home to use for about three days, and if you decided you wanted to keep it they processed the loan. Having the Mac at home really made me fall in love with it, so in December of 1984 I bought my first Mac. Being enthralled with the Mac, I started lugging it with me to work. By this point I was the supervisor of a group called "Special Projects", and my team was charged with a number of things: regulatory compliance, studies, project management, and now IT. Pretty quickly, my co-workers got began to turn into Mac fans, and I started tweaking the five year plan to buy fewer PCs and more Macs. I was also going to a lot of Mac User Group meetings in those days; that was the place to really try out software, as most everyone would bring boxes of floppies as well as the original disks for new applications they had purchased. Copying was rampant, but I don't remember anyone doing outright pirating; if you tried a program and liked it, you'd end up buying it. That was the case for me in 1985 when I tried out a copy of Aldus Pagemaker (the first "professional" page layout application) and then bought the application. At one point, I bragged to our financial manager that I could use the app to lay out our subsidiary's annual report at a much lower cost than sending it out to a traditional printshop; he called my bluff and for the next month I worked with the very buggy 1.0 software to create the report. In the end, I was successful and the finance department decided to get Macs for everyone. In a few more years, the engineering role ended for me and I was a full-time IT manager. Starting in 1987 and through 1994, I attended Macworld Expo in San Francisco. From about 1990 to 1994, I also went to the Apple WorldWide Developer Conference, which was held in San Jose at that point. These were the years of trying to get a new Mac OS off the ground, the intro of the Newton MessagePad, the MPW vs. CodeWarrior battles, and extremely boring keynotes by such luminaries as Michael Spindler and Gil Amelio. I also spent a lot of time using Pagemaker to create printed newsletters for WestGas and for a number of groups I was a member of. While that was a bit of work that I never really ended up getting paid for, it taught me a lot about design, layout, printing, and writing. From 1986 to 1994, I also ran a Mac bulletin board system known as MAGIC (Mac And [Apple II] GS Information Center). This started off on my original Mac 512, and by the time I quit running the BBS and moved to a website, it was a three-phone-line setup running on two networked Macs Including my favorite Mac of all time, a Mac IIcx. The BBS was the "official site" for the MacinTech Users Group, a MUG that's still going strong to this day. My first website was PDAntic.com, a play on John Sculley's acronym for the Newton – Personal Digital Assistant – and the fact that my wife often refers to me as being pedantic. I chose to run the site with news posts written in a reverse chronological order, which means that I was essentially doing blogging in 1994! I was doing some half-hearted development for the Newton at the time, and still have a working MessagePad 2100. 1995 was the start of a bad period for me personally – our pipeline company was swallowed back into our parent company, and then all of us who had any dealings in information technology were outsourced to IBM's ISSC services group (later IBM Global Services). While I won't go into details, it was the worst part of my career, with incompetent and occasionally unethical managers, a strategy that consisted of trying to do more and more work with fewer employees (with predictable bad results), and the most demoralized staff I've ever seen. I survived for nine years, after which I chose to go out on my own. At the beginning of my time with IBM our client (the company I worked for) had a total of over 1,200 Macs company-wide; by the time I left we were down to a handful in the corporate communications department. One of my first IBM projects in 1996 was to move all of the Mac users to Windows 95 –- I should have quit when I was ordered to do that. One bright spot during the years 1999 through 2006 was my participation in a number of Microsoft's Mobius conferences. These were meetings of those of us who ran mobile-oriented websites, with Microsoft showing off concepts and picking our brains for ideas about UI, built-in applications, and the direction of the mobile world. I also met a number of the top bloggers in the mobile space, including Ryan Block and Peter Rojas, who were both instrumental in starting up Engadget. Peter was one of the co-founders of Weblogs, Inc., the blog network that TUAW was a part of before being purchased by our current owner -- AOL. In 2005 I started my own consulting firm, Raven Solutions, to do Mac consulting and support. I became a member of the Apple Consultant Network (ACN), which helped my business to grow quite quickly. I also started writing books at about this time, creating a book called "Take Control of your iPod: Beyond the Music" that is still for sale from Adam and Tonya Engst's Take Control Books. One top moment about this time was seeing Steve Jobs introduce the iPhone at the 2007 Macworld Expo. That was something I'll never forget, and I have a Nitrozac painting of the event within my field of view in my office. In late 2007 I was on a weekend trip to Vegas with my wife when a friend pointed out that one of my favorite Apple sites –- TUAW –- was accepting applications for freelance writers. I turned in my requisite three sample articles, but didn't hear anything ... until April of 2008. I was on a business trip when I received a call from former TUAWite Scott McNulty, who wondered if I was still interested in being a TUAW blogger. He gave me a test that I remember quite well; I had one hour (sitting in an airport waiting for a flight) to write a news post about a new and completely hypothetical Apple product. I zapped it to him via email with time to spare and was offered the job. Since that time I've become a full-time employee of TUAW parent company AOL, I've met thousands of TUAW readers at Macworld/iWorld and other events, written a number of books (many with fellow TUAW blogger Erica Sadun), and published almost 1.8 million words of blog posts. I love sharing time with TUAW fans every Wednesday afternoon on TUAW TV Live, as well as delivering the daily Apple news on the Daily Update podcast. And when I get to join with my teammates for one of the Sunday night Talkcasts, that's like getting together with family. The only way to describe my life right now is as "blessed." I work with a great team of professionals doing what I love to do the most, writing about a company that has had such a huge effect on the course of my career and my life. I don't know how long this ride will last, but I sincerely hope it's for a long, long time.

  • The Daily Roundup for 01.02.2013

    by 
    David Fishman
    David Fishman
    01.02.2013

    You might say the day is never really done in consumer technology news. Your workday, however, hopefully draws to a close at some point. This is the Daily Roundup on Engadget, a quick peek back at the top headlines for the past 24 hours -- all handpicked by the editors here at the site. Click on through the break, and enjoy.

  • The Apple II, as described by Steve Wozniak

    by 
    Sean Buckley
    Sean Buckley
    05.28.2012

    Ask the average geek to describe the Apple II and you'll probably hear something about its legacy or software. Ask Steve Wozniak circa 1977, on the other hand, and he'll write you a technical tome -- or at least he did for Byte magazine. Way back when the classic computer was fresh, a young Woz penned an extremely detailed "system description" for the rig, pouring over specifics on the II's graphical capabilities, memory, peripherals, programming language and more. Perhaps in (slightly late) honor of the machine's 35th anniversary, Information Week has seen fit to reprint the extensive examination for your reading pleasure -- assuming you're up to wading through the technical nitty gritty. No? Well, Woz does have a few nuggets of wisdom for the layman. "To me," he says, "a personal computer should be small, reliable, convenient to use and inexpensive." No arguments here, Steve. Read the man's words for yourself at the source link below.

  • DevJuice: Promotion from the Trenches

    by 
    Erica Sadun
    Erica Sadun
    05.09.2012

    TUAW Dev Juice talks with Mac developer Lyle Andrews, who agreed to discuss his real-world experience launching applications. He'll be sharing tips and hints about practical app promotion skills. I want to thank you for taking the time to talk to me and to TUAW readers. The reason I asked you here was because I think you have a really compelling story to tell and tips to share. You're a small developer who's achieved some exciting success in Apple's App Stores, yes? Can you tell us about your background and your products? Yes, I've been coding since I was 12, have been through 14 languages, have a degree in philosophy, and am a veteran of the dot.com wars where I ran over 60 projects including a dot.com startup and a Fortune 500 web deployment. My project history can be seen here. I've been moving into consumer software development and have two large projects in the works, Ynnis Myrddin, an interactive film about Merlin, and MetaView, a 3D market vizualizer. When the Mac App Store started operations I decided to write a few small apps to learn its dynamics: Tempest - a video lightning screensaver, Fireworks HD, another screensaver, and Network Logger, an active network monitor. Network Logger is currently selling in the top 6%, Fireworks HD in the top 2.5% and Tempest! in the top 2% of their categories on the US store. I first came across your work when I reviewed your Fireworks app just before New Years. Can you share how that process of pitching and reviewing worked from your end and talk about how the TUAW review affected your sales? Getting Fireworks HD reviewed by Apple was straightforward compared to getting the first screensaver on the store, since the App Store doesn't sell screensavers directly. I tried numerous ways around this restriction, including zipping up the saver and storing it in a shell app's bundle or having the app download the saver. After half a dozen rejection cycles one of the Apple reviewers took pity on me and suggested adding a download link that the user could click on in the app. This puts the onus of responsibility on the user, gives them control, and with that approach I was able to get approved and onto the store. Being very much a developer I have the classic indie tendency to just keep coding and sit around wishing that someone was promoting my apps full time. This does make the exposure the App Store affords very attractive. I do occasionally send out press releases and hold free promotions on the store. For Fireworks HD, I knew getting some exposure for New Year's Eve was important so I emailed an editor at TUAW about the possibility of a review right after Christmas. I saw that as a win/win since that was the app on the store most appropriate for New Years' Eve at the time. Fireworks HD was named Mac App of the Day on Dec 27, 2011 and the sales rank responded immediately and dramatically, moving from around rank #100 up to #4 in Top Paid Entertainment within a day. On New Year's Eve itself Fireworks HD was on the Top 10 Entertainment charts of 13 countries. Over the next few weeks Fireworks HD trended down as expected but happily ended in a higher average range which has persisted for five months to date. Can you tell me about some of the strategies you've used in-store for helping your apps stand out from the competition? I know you mentioned something about icons when I first started talking to you about doing this interview. What other suggestions do you have? I anticipated your question, so here is a very long list of suggestions. Pop out. Your icon has to pop out. Look at the primary category you will be listed in, imagine you are in the top 200, what similarities or appearance trends can you find in the app icons, and how can you break them in a way that draws attention and invites a click. A number of people have told me that they clicked on Network Logger just because of the icon. Something about it just makes you want to click it whatever it leads to. Keep it short. This indicates that you are confident that the customer is going to like your product if they are interested in general. It shows you feel like you don't have to say that much to make the sale. This is true with new clients as well as products. A long description starts to feel like an apology after awhile. However, some things are complex and merit a longer description. Conciseness is the actual metric. How can you say the most with the least words? Keep it Plain. Plain descriptions with minimal self-praise and adjectives are trusted more by App Store customers than overinflated rhetoric. Focus on Strength. Best in class in some way? Definitely say so. If nothing is the best, should you be aiming higher? This is true for Fireworks HD, it is in some ways a silly app I built to test out the store, but if you need beautiful 100% realistic HD fireworks for your event that don't repeat in sequence and work when no network connection is available, there is nothing better available for Mac than Fireworks HD. Be a master of the obvious. While there are many great naming strategies, if you can name a product after its product category, you have a home field advantage. With "Network Logger" for instance, the genus is instantly obvious, the customer just needs to know the species. They click, they are coming to see you, you are the category, the sale is yours to lose. Don't sweat bad reviews. They are going to happen, if an app has merit it will tend to sell anyway and time will equalize things. Tempest has been in the top 10 in Spain in Paid Entertainment for many weeks despite having only two reviews there, both 1 star. Follow or lead the market, either way know which you are doing. Leading the market is much more challenging, and can be much more rewarding. Can you come up with a way of systematizing a part of the raw unordered universe and create a new class of human activities? If you succeed your glories will be sung in Valhalla. Following the market can be safer and is often more lucrative. Can you rethink a better way to handle a common human activity? Use resonance awareness. There are some things you just know are going to resonate with a particular audience, fireworks, lightning, beaches, white rounded kitchen appliances...resonance awareness is really a diverse skill set it pays to hone. We know Steve Jobs actively developed this skill set throughout his life. Understand need. You need their need. What fundamental emotions are driving the user as they use your software? A desire for order? Curiosity? Love? A desire to conquer? Every activity has a number of emotions that are commonly associated with it. Knowing what your audience is experiencing and wants to experience emotionally is the foundation of an evolving relationship. It's not just woven into the advertising, the product is built around it. In conclusion, these things are all simple in theory, but if the execution sounds simple, think again. The student sees the simple and thinks it simple, the master sees the simple and thinks it profound. I hope one day to be such a master myself. There's been a lot of negative talk over the last few years about the App Stores being too saturated, that small guys can't make a living at it, that there's no room to break in. What would you say to that? I would say that oversaturation is bound to happen given the gold rush mentality, but overall the App Stores have been really empowering to smaller developers and that virtue will be recognized if one persists. The bar is higher now and development and marketing effort have to reflect that. The App Store gets far more traffic than my own web sites and provides more than just sales exposure; the review system has sort of opened up a dialog between me and my customers that wasn't there before. There are a lot of nasty reviews on the US App Store but internationally they are much more measured; they all make you tougher (better at taking criticism), and your app better. Being able to say you have apps on the store also has a certain social cachet these days that's valuable in personal and professional situations and that opens up new opportunities. Lyle, thank you so much for taking the time to talk today. I'm hoping that your experience and your insights will help inspire other developers, especially those just getting started. And if you're still reading this post and you like this kind of developer-centric coverage, please let our editorial team know. Drop a note and tell TUAW that you care about dev topics.

  • Apple II turns 35, doesn't bother with midlife crisis

    by 
    Sean Buckley
    Sean Buckley
    04.16.2012

    It was 35 years ago today that two Steves and a handful of employees introduced the world to a game-changer: the Apple II. Easily recognizable today as one of history's first truly accessible personal computers, it's a bit odd to think that the iconic rig was almost overlooked at its debut at the 1977 West Coast Computer Faire. Even so, the beige box weaseled its way into our homes and schools. $1300 bought the most basic model of the machine that taught a generation of children the dangers of fording a river, rocking a paltry 4KB of RAM and a 1MHz processor. Despite its age, the old Apple II is doing its best to keep up with the times -- making music, going to concerts and even trying out those hip Bluetooth protocols its grand kids are always talking about. Feeling nostalgic? Check out Time's in-depth tribute to the Apple II's history, influence and legacy at the source link below.