Slashdot Mirror


How the Lisa Changed Everything

Sabah Arif writes "The Lisa, started in 1979 to provide an inexpensive business computer to Apple's lineup, enjoyed little success. With its advanced object oriented UI and powerful office suite, the computer was priced well above the means of most businesses. Despite its failure, the Lisa influenced most user interfaces, and introduced many features unheard of in earlier systems (like the Xerox Star or VisiOn). Read the story of the development and demise of the Apple Lisa at Low End Mac."

194 comments

  1. Oh Please by Anonymous Coward · · Score: 1, Insightful

    I can't believe Slashdot is posting this "At Apple, even our failures are huge successess!" story. Would they publish one on how Microsoft Bob revolutionized the world of user agents and computer interaction?

    1. Re:Oh Please by Anonymous Coward · · Score: 1, Insightful

      Clearly not, as MS has left us nothing but a shattered wasteland of hopes and dreams...

    2. Re:Oh Please by pwnage · · Score: 1

      No, but Microsoft Bob did get Bill Gates laid.

      --
      Reminder: Apple owns 1/255th of the internet.
    3. Re:Oh Please by hey! · · Score: 3, Insightful

      Well, it was very historically significant machine. By your standards, Smalltalk is contemptible because it never had more than a handful of programmers.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    4. Re:Oh Please by Anonymous Coward · · Score: 0


      Microsoft Bob did get Bill Gates laid

      By the same token it also assured Melinda Gates a place as one of the all time worst role models for women in the tech industry. Hey, why worry about whether your product is any good or not when you can just sleep with the boss?! Does anyone seriously think that MS Bob would have seen the light of day if Melinda had been a guy?

    5. Re:Oh Please by OrangeTide · · Score: 1

      Microsoft Bob did change the way people thought about human interfaces. It got a lot of things right, and a lot of these newer experimental interfaces have a lot in common with BOB. I think the problem with Bob wasn't the technology, but it was a lack of a market.

      --
      “Common sense is not so common.” — Voltaire
    6. Re:Oh Please by rbanffy · · Score: 3, Insightful

      Microsoft Bob was very important - it told us what not to do and which way not to go.

      An yes, the Lisa shows paths we did follow as well as some we didn't. The whole idea of centering document creation on templates at the GUI level is very interesting and should warrant further investigation. Hope Gnome and OpenOffice folks think about it.

    7. Re:Oh Please by kevcol · · Score: 1, Funny

      What do you mean?! I am using Bob right now- it's a tremendous OS!

    8. Re:Oh Please by shmlco · · Score: 1
      From a certain perspective, this is just a metaphor. Does it matter if the icon on my desktop is a diamond and called an application or rectangular and called paper or a template? Either way, I double click it to get a "new" document of that type.

      Besides Word and many other application allow you to save templates, and not all applications fit the template model anyway.

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    9. Re:Oh Please by cagle_.25 · · Score: 1

      We had hopes and dreams for Microsoft? I just wanted my computer to boot without crashing. That's not exactly in the "dream" category...

      --
      Human being (n.): A genetically human, genetically distinct, functioning organism.
    10. Re:Oh Please by srleffler · · Score: 1
      The key difference is how you open an old document. In a true document-oriented system, the most natural way to open a previously-created document is to locate the document, based on where you stored it (perhaps by date, or by project, or by some other classification that suits you). In an application-oriented environment, it's more natural to locate the application that created the document, and then open the document from within that application. Windows has elements of both.

      The document-oriented approach is probably more intuitive and encourages better organization of files (e.g. storing documents by topic rather than by what application created them). One downside is that the user still needs to be aware of applications, as some tasks don't naturally have a 'document'.

    11. Re:Oh Please by Anonymous Coward · · Score: 0

      The Lisa was a great machine. I had great fun with them. Certainly more fun than the Macintosh.

      Maybe someone will see this article and be inspired by it. There are certainly a lot of good ideas there that could be amalgamated anywhere.

      Calling it a failure is ignoring the fact that you yourself have nothing comparable to come with. You might call it a failure, but at least it's not the loser you are.

  2. Remembering Lisa by erick99 · · Score: 1

    I remember going to training on the Lisa when I first started working for an Apple dealer in '83 (though the training might have been in '84). The Lisa sold for about $10,000 with a small hard drive. Still, it was very cool.

    --
    http://www.busyweather.com/
    1. Re:Remembering Lisa by ghound · · Score: 1

      All complaints about the relevance of this article aside, it allows us greybeards to reminisce about about why we started tinkering with computers in the first place. I also worked for an Apple dealer and the Lisa was the coolest gadget we had! It weighed about 30 pounds, had a five megabyte external hard drive, and was way ahead of anything IBM/MS put out at the time. Of course, we didn't actually sell any. Who could afford it?

    2. Re:Remembering Lisa by Anonymous Coward · · Score: 0

      Yep, I remember the Lisa. Cute name. Bad design. It was slow. It had a processor with an externally available serial number that was used by the Lisa software to key itself on. It had a non standard floppy drive called a 'stringy floppy' or 'twiggy floppy' drive. I never saw any blank floppies for it to use, ever. I never say any software for it except Apple's own stuff. I think that none was ever available. It had a software loadable bios, meaning that the only hard coded bios had to be a set of sparse barebones routines meant only to set up Apple's own bootstrap routines. No native language like Apples' Apple ][ basic was present. By itself without its software loaded, it was a doorstop. An expensive one. Its software was a load once affair. Its software had to load with its masters unprotected so that the system would write back onto the original disks with the serial number of the processor and other system data found on the system when it was first loaded. The software would not install unless this was allowed. This meant if any part of the hardware failed, the software would not install as it would detect a difference in the system and shut down. Calls to Apple produced nothing but false accusations of attempted software theft and demands that a totally new package of software be purchased. This software was exceedingly expensive for what one got. We all laughed at the fools that bought into this
      masochistic swindle. Now look at we all and the industry that we allowed our governments and big business to foist on us.

  3. I for one welcome... by Crayon+Kid · · Score: 0, Redundant

    ...our new user interface overlords.

    Oh wait. It's not 1979 anymore. Let me see... 2005 minus 1979 is 26... it's obviously the 26th aniversary of Lisa that makes this news-worthy, right?

    --
    i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer
    1. Re:I for one welcome... by erick99 · · Score: 2, Interesting

      The Lisa was introduced for sale in 1983 for about $10,000. It sounds like development began in 1979.

      --
      http://www.busyweather.com/
    2. Re:I for one welcome... by GigsVT · · Score: 0

      And the Xerox Alto came out in 1973 with a GUI, object oriented OS, etc. This story is just an Apple fanboi jerkfest. The Lisa wasn't innovative.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    3. Re:I for one welcome... by andersbergh · · Score: 1

      Why do you spell it fanboi?

    4. Re:I for one welcome... by Anonymous Coward · · Score: 0

      Did you even read the article? Twit.

    5. Re:I for one welcome... by GigsVT · · Score: 0, Troll

      It throws in added implication that they are homosexual.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    6. Re:I for one welcome... by gbarrelhouse · · Score: 2, Funny

      I think waht made it newsworthy was that it's an interesting new article at Low End Mac. Just a theory.

      --
      GROGNARD'S TAVERN Old-School, Out-of-Print & Obscure RPGs
    7. Re:I for one welcome... by Chris+Tucker · · Score: 2, Insightful

      Because he's a pretentious git, who wants people to think he's hip, happening, with it, a part of the hip happening with it scene.

      Actually, he's just some damn skript kiddie. They ALL talk like that.

      Pathetic, actually.

      --
      Guaranteed! This comment 100% Anthrax free!
    8. Re:I for one welcome... by Back+Slider+1969 · · Score: 1

      So could it right click?

  4. Knew I read this before by enigma48 · · Score: 4, Informative

    /. already posted this story http://apple.slashdot.org/article.pl?sid=05/07/31/ 1346224&tid=190&tid=3 a few months ago. In their defense, the old article was hosted at Braeburn.ath.cx (but looks like they've redone their website and braeburn resolves to lowendmac.com).

  5. The Lisa Was a Very Slow Computer by Anonymous Coward · · Score: 5, Funny

    Haha.. reminds me of this joke:

    Knock knock..

    Who's there?

    (wait 45 seconds) ... ..... .......

    Lisa!

    1. Re:The Lisa Was a Very Slow Computer by slowbad · · Score: 1
      wait 45 seconds

      How about wait 4.5 years ? Maybe if the Slashdot article referred to the
      "1979 Lisa Project" it might provide a bit of a better timeline persective.

      A computer that was in most shops for 7 months does not have a 7 year history!


      --
      Not a troller flame.

      See subject header.

      Note ID of poster.

  6. You got to wonder by Stevyn · · Score: 4, Interesting

    How would things be different today if Apple initially offered the Lisa at a substantially lower price just so people experienced the GUI? IBM and the clones were much cheaper, so businesses probably chose initial cost over an interface that could have lowered training costs and increased productivity. And if people were using Apple machines at work, then they would have bought an Apple for home later on.

    1. Re:You got to wonder by cosmic_0x526179 · · Score: 1

      { wonders idly } Has anyone doen a Lisa emulator for OS X ?

      Lisa 7/7 under OS X... that would be trippin !

      --
      This msg is brought to you by the letter 'W'.. for Worthless Wuss
    2. Re:You got to wonder by Midnight+Thunder · · Score: 1

      I would have pointed you to emulation.net, but it appears to be resolving to 127.0.0.1!?

      --
      Jumpstart the tartan drive.
    3. Re:You got to wonder by GigsVT · · Score: 1

      It's wasn't all that much more, an IBM PC was $3000, and with a couple upgrades could easily be $10,000, the same as the Lisa.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    4. Re:You got to wonder by Midnight+Thunder · · Score: 4, Informative

      The site seems to be here: http://emulation.victoly.com/ Must admit I couldn't find any Lisa emulators on the site, but did find this link: http://lisa.sunder.net/

      --
      Jumpstart the tartan drive.
    5. Re:You got to wonder by Anonymous Coward · · Score: 0

      Uh, the Amiga was done a year later, and kick ass all over the Lisa. Can you say color and multi-tasking?

    6. Re:You got to wonder by tpgp · · Score: 1, Interesting

      substantially lower price just so people experienced the GUI?

      I think you overestimate the importance of a GUI to businesses at the time.

      Many tasks could be accomplished far easier without a GUI - text and number processing comes to mind (the mainstays of business desktop work)

      GUIs have advanced tremendously since then - to the stage where a GUI/mouse combo does actually enhance productivity with word processing/spreadsheet applications - but there are still many areas where a GUI (particularly coupled with a mouse) will decrease productivity (think Point of Sale particularly)

      --
      My pics.
    7. Re:You got to wonder by cpt+kangarooski · · Score: 2, Insightful

      Meh. A damn lot of the POS terminals I see these days have buttons -- often touchscreen buttons -- and are GUI based. A GUI doesn't have to be a windowing interface with a mouse, you know.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    8. Re:You got to wonder by JulesLt · · Score: 1

      It was just way ahead of it's time. Bit like building a machine with a 6GHz 128 bit CPU and quadruple 512 Mb graphics cards and a 42" monitor . . . in the computer market there's always a trade-off between what you could do and what makes commercial sense. The Lisa didn't. The Mac, while substantially cut down from Lisa, made commercial sense.
      I remember using Sun workstations in the very late 80s - multitasking PostScript based windowing, 19" or possibly larger hi-res monitors, really cool stuff. Absolute fortune. NEXT was the Lisa to OS/X. In motoring terms I guess they are concept cars. Jobs is just peculiar in trying to sell them.

      Businesses don't automatically go for the cheapest machines BUT if you consider your computer investment is going to go down in value rapidly, far better to lose 500 on a 1000 machine, than 5000 on a 10000 machine. Plus there is always the 'any good innovation will become standard' argument- and to be fair, most of those innovations have eventually turned up on the PC. The majority of businesses are happy not to be at the edge of innovation.

      --
      'Capitalists of the world, unite! Oh ... you have' (League Against Tedium)
    9. Re:You got to wonder by oliverthered · · Score: 1

      To that extent may companies still use textdriven interfaces, there much faster than the GUI equivalents, do exactly the job you want and nothing more and don't distract the user, perfect for productivity and training.

      not every office job requires a word processor or web browser etc..

      --
      thank God the internet isn't a human right.
    10. Re:You got to wonder by Dogtanian · · Score: 4, Informative

      Two years later. And yes, the graphics and multi-tasking ability of the Amiga kicked the Lisa's ass (and Macintosh's) all over the shop at a fraction of the cost, no doubt about it.

      But, as a former Amiga user, I'll still say that the OS 1.x interface wasn't the best GUI ever. They improved quite a lot with 2.x onwards, but that was five years or so later.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    11. Re:You got to wonder by Hiro+Antagonist · · Score: 3, Insightful

      The problem is, you're looking at computers as if they are disposable, not capital, goods. Realistically speaking, having a long-term planner in your systems department, someone who thinks about where a business is going to be in ten or twentry years, alleviates a lot of the costs of continuously replacing hardware, because their logic is, "Buy quality, plan for expansion, and don't through out perfectly good solutions just because Oracle bought me lunch at Morton's."

      --

      --
      I Hit the Karma Cap, and All I Got Was This Lousy .sig.
    12. Re:You got to wonder by Anonymous Coward · · Score: 0

      To be fair the Lisa and early macs didnt have that much of a GUI either.

    13. Re:You got to wonder by tpgp · · Score: 1

      Meh. A damn lot of the POS terminals I see these days have buttons -- often touchscreen buttons -- and are GUI based.

      True - but touchscreens (along with mice and all other pointing devices I've used) are a RSI disaster.

      Also - even though they are initally easier, GUIs tend to make repetetive tasks more complicated - they are unsuitable for most POS applications.

      A GUI doesn't have to be a windowing interface with a mouse, you know.

      Indeed - and a text based interface can have alot of graphics - as long as it is text (keyboard, not pointer) input driven.

      --
      My pics.
    14. Re:You got to wonder by timeOday · · Score: 1
      How would things be different today if Apple initially offered the Lisa at a substantially lower price just so people experienced the GUI?
      Maybe there would be no Apple, because they would have lost their shirts selling expensive hardware at a loss. If comparable hardware could be produced at a reasonable price back then, Lisa would have had much more competition. But most computer makers knew the time wasn't yet right.

      I disagree with the basic notion that the Lisa influenced everything to follow because it had a GUI first. Everybody already knew expensive hardware could do more, just not enough to make it worthwhile at the time.

      As another example, I don't think the modern game hardware industry owes much to Silicon Graphics - their hardware was ahead of PC hardware for a long time, but at a price most people wouldn't pay. When the time was right, graphics hardware became widespread, but it was no thanks to SGI who were trying to maintain the old prices.

    15. Re:You got to wonder by slowbad · · Score: 1
      How would things be different today if Apple initially offered the Lisa at a substantially lower price

      Substitute "Mac II and 1987" for "Lisa and 1983"

      And if people were using Apple machines at work, then they would have bought an Apple for home

      Pull up Apple's stock price for 15 years starting in mid-1983. And watch AAPL go nowhere.
      Plot product line versus Wall Street valuation, and it was never a business computer company.

      Apple does well with consumers. Up 310% in twelve months with iPod as half their business.
      (Feb 2004 through Mar 2005)

    16. Re:You got to wonder by drsmithy · · Score: 1
      Indeed - and a text based interface can have alot of graphics - as long as it is text (keyboard, not pointer) input driven.

      I'd still call that a GUI.

      To me, the best way of describing the difference between a CLI and a GUI is that with a CLI you tell the computer way to do and with a GUI you select one or more operations the computer gives you to choose from.

      From a usability perspective, a CLI requires you to know what you want to do /and how to do it/ before you can use it, only offering reactive feedback. A GUI helps you figure out how to use it based on proactive feedback.

      IMHO, an 80x25 text-based interface, which is just a bunch of menus, is still a GUI.

    17. Re:You got to wonder by Kadin2048 · · Score: 1

      This is very true. A "command line" program which uses ncurses for an interface is still a GUIed program, even though it may not use a windowing environment (xwindows, Aqua, MS Windows) to do it.

      We have gotten to the point today where we dismiss anything that doesn't use a window manager as a program without a graphical interface, but that's simply not true. It is quite possible, and was very common in the past (before said window managers existed) to create GUIs in an entirely fixed-width, text-based environment.

      I think the difference is that a true "commandline" program takes in and produces data in a strictly linear fashion. A graphical program produces a great deal of information on the screen, which the user then interprets and not necessarily in any particular order.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    18. Re:You got to wonder by marcello_dl · · Score: 1

      The first Amiga I saw (with the famous juggler demo and the HAM graphics) had the most unstable OS I had experienced up to that time. Guru meditation all over the place.

      Lisa and macs, at least, were perfectly usable up to their limits (and the first 128k mac's limits were easy to reach).

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    19. Re:You got to wonder by Dogtanian · · Score: 2, Interesting

      You're aware that a large amount of Amiga software (primarily games and graphics-oriented software) bypassed the OS, and "hit the hardware" directly?

      I'm not sure that the Mac/Lisa would have been focussed on those types of apps (let's face it, 2-colour monochrome isn't going to compete with 4096-colour HAM), so perhaps the comparison isn't entirely valid.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    20. Re:You got to wonder by default+luser · · Score: 2, Interesting

      As another example, I don't think the modern game hardware industry owes much to Silicon Graphics - their hardware was ahead of PC hardware for a long time, but at a price most people wouldn't pay. When the time was right, graphics hardware became widespread, but it was no thanks to SGI who were trying to maintain the old prices.

      Are you kidding me? The modern game hardware industry owes a lot to SGI.

      First, let's talk about SGI's direct effect on the industry:

      SGI designed the N64. It was basically all the best bits of a $10,000 Indy workstation, shrunk down and sold for $250. Sure, it was a little memory-deprived, but that was a result of the pricepoint. Its 3D prowess was unmatched by anything consumer-level until the Voodoo Graphics was released for the PC a year later (which still cost more, intro-ed at $300), and was unchallenged in the console arena until the Dreamcast.

      SGI's '$250 Indy' featured hardware support for mip-mapping, billinear filering, anti-aliasing...tons of features typically only seen on SGI workstations.

      Now, let's talk about the indirect effects SGI had on the industry.

      SGI developed OpenGL. This had the following indirect, but lasting effects:

      * 3dfx based their GLide API on a subset of OpenGL, removing some of the professional-only instructions, as well as the transform and lighting hardware support, in order to implement a cheap 3D pipeline. 3dfx was the most influential hardware company in the early consumer 3D industry.

      * OpenGL made Microsoft react and make Direct3D a solid development platform, and encouraged MS to innovate even when they surpassed OpenGL. The ability of OpenGL to use unofficial extensions kept Microsoft on their toes. SGI's industry clout was key in getting OpenGL support built into Windows 95b / 98.

      SGI lead the way in making 3D a commodity, but once 3D became a commodity they lost the reins.

      --

      Man is the animal that laughs.
      And occasionally whores for Karma.

    21. Re:You got to wonder by marcello_dl · · Score: 1

      I was only pointing out that the Amiga came out after 2 years but was as mature as the initial Lisa/Mac environment much later (if evar :-) ).

      You're aware that a large amount of Amiga software (primarily games and graphics-oriented software) bypassed the OS, and "hit the hardware" directly?
      Are you aware that, even if it were justifiable by the circumstances, this is not considered to be good design? :-)

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    22. Re:You got to wonder by Dogtanian · · Score: 1

      Bad design? Absolutely!

      A lot of that software caused major problems when going from the A500 to the A500 Plus/A600 (same "generation", but slightly upgraded custom chips). Many games failed to work. Then, more problems from the A500-generation to the A1200 (major upgrades to the custom chips).

      However, that was required, because going through the OS slowed things down too much. If the Mac had had similar hardware to the Amiga, it would probably also have required doing the same thing to get acceptable performance.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    23. Re:You got to wonder by bjb · · Score: 1
      Uh, the Amiga was done a year later, and kick ass all over the Lisa. Can you say color and multi-tasking?

      Hate to respond to a troll, but to clarify any confusion this might introduce. The Lisa DID have multitasking - it was one of the features stripped out for the Macintosh.

      Basically, they wanted to have multitasking in the Mac, but without a MMU it made things a bit difficult to do. The Lisa had custom MMU hardware which significantly added to the cost of the machine. This was too much for the more affordable Mac.

      Yes, I know the Amiga OS never used the MMU on models that did infact have it (any non-EC 68030 and 68040), but that also explains why we all know about the Guru Meditation. (Yes, OK.. "enforcer" used the MMU, but wasn't an integrated part of the OS!)

      --
      Never hit your grandmother with a shovel, for it leaves a bad impression on her mind...
    24. Re:You got to wonder by bjb · · Score: 1
      Has anyone doen a Lisa emulator for OS X ?

      Last time I checked, a Lisa emulator is underway in the MESS suite. Was able to boot into Office 7/7, but not very stable.

      I think much of the problem comes from the fact that there isn't a lot of documentation out there on the hardware details (especially given the custom MMU and other hardware bits).

      --
      Never hit your grandmother with a shovel, for it leaves a bad impression on her mind...
  7. Mac changed everything by gilesjuk · · Score: 3, Informative

    The Apple Lisa was way too expensive and rather slow. The Mac was much cheaper and worked much better. Hence why you buy an Apple Mac not an Apple Lisa when you go to an Apple store now.

    It was Steve Jobs who brought us the Mac too, he recognised it was the right product and better than the Lisa. Much of the work on the project until Jobs took over was done by Raskin and his team.

    1. Re:Mac changed everything by TheAncientHacker · · Score: 1

      Actually, the Lisa was out for a year before the "Baby Lisa" (Macintosh) came out. As for why people would use Lisa rather than Macintosh? Well, for one thing, Lisa came with great software (in some ways better than what's available even today). Macintosh, on the other hand, had at best, MacWrite and MacPaint and little else that was available until a year later. There were no native dev tools so there were no in-house apps and no liklihood of them. There was no hard drive. The computers had 128K of TOTAL RAM. Basically, for 1983 and 1984 there was NO viable Macintosh.

    2. Re:Mac changed everything by cerebis · · Score: 2, Informative
      It was Steve Jobs who brought us the Mac too, he recognised it ...
      Hang on there. Steve Jobs can take credit for seeing the Macintosh project taken to market, but Jef Raskin deserves all the credit for the initial concept (and name, complete with misspelling) and early development. It was only after Jobs was refused the position of project leader for the Lisa that he came across the small Mac research project, consisting of about 10 people Raskin had collected, and set about forcibly taking it over.

      Fear the 20 something millionaire major share holder with bad management skills and a serious case of narcissism.

    3. Re:Mac changed everything by Anonymous Coward · · Score: 2, Interesting

      Jef Raskin's total contribution to the Macintosh project was "Hey, let's build an inexpensive computer that's easy to use." That's it. He had absolutely no technical input whatsoever, and no input at all once Jobs took over the project.

      People love to latch on to Raskin and call him the unsung hero, but the fact is that he totally abandoned the project when he didn't get to do everything his way.

    4. Re:Mac changed everything by maxwells_deamon · · Score: 1

      The Mac was not the better computer at the time. If it had not been for the laser printer, the Mac would have died too. Remember the Mac had only a single floppy drive and 128K ram. Then came the 512K Mac and second floppy (a vast improvement but still not really usable in a office setting). Every once in a while you would have to swap floppies out of the drives (20 swaps sometimes to save a document, yes really!)

      The Mac did not truely become usable in the office until the Mac Plus came out. (My external SCSI drive for my Mac plus was over $1900 for 65MB IIRC)

      The Lisa had features like full preemptive multitasking and office applications which could work with each other long before Microsoft was attempting anything like it.

      The Lisa 2 is not really that slow, it takes a while to boot, but based on other computers of the time it was not that slow. I remember a PDP-11 taking most of a work day to reformat a 10MB hard disk.

    5. Re:Mac changed everything by WillAdams · · Score: 1

      The 128KB Mac had a connector for a second (external) floppy drive, and they were available in 1984 for those who didn't want to do the ``floppy shuffle''

      William

      --
      Sphinx of black quartz, judge my vow.
  8. Ah, Memories by rob_squared · · Score: 4, Informative
    I remember the good old days, back when the Apple computers were simpler. When the mouse only had 1 button.

    I kid, I kid.

    Anyway, here's a picture of the orgional ad: http://www.jagshouse.com/lisabrochure.html

    --
    I don't get it.
    1. Re:Ah, Memories by Tablizer · · Score: 1

      My godness, they had it back in 1982(?) but we *still* don't have decent data-grid widgets for Web apps (unless you pay an arm and a Lisa)

    2. Re:Ah, Memories by halleluja · · Score: 1

      Darn, 32bit in 19-miami-vice..

    3. Re:Ah, Memories by courtarro · · Score: 1

      Gee, I wonder who that is making easy use of the Lisa in photo 7 ...

    4. Re:Ah, Memories by Anonymous Coward · · Score: 0

      I thought the same thing too, but on closer inspection, determined it looks nothing like Steve Balmer. :)

      What sctually struck me more is that the guy is using the mouse left handed. Try that with a multi button mouse! ;)

  9. Jobs didn't get it. by Baldrson · · Score: 3, Interesting
    As I described here years ago:

    Gutting programmer effectiveness and routing new programmers into BASIC by a factor of at least 10 while maintaining, and even slightly improving the GUI is a great example of "not getting it". You can say OOP would become important in a few years and I can say the windowing GUI would become important in a few years with or without Jobs. But the revolution had already occured at PARC (and if you're focused on the mouse environment -- even a decade earlier at SRI which is where PARC, and indeed PLATO with its touch panel, got their inspiration -- I remember sitting in meetings at CERL/PLATO viewing the films of SRI's research in 1974 as part of PLATO's computer-based conferencing project).

    DOS applications were starting to pick up on it despite the horrid CGA they had to work with initially -- and it wasn't because Jobs did the Mac. The Windowing GUI was inevitable and obvious to people with money as well as most personal computer programmers, especially once Tesler had already popularized it with his 1981 Byte magazine article.

    Dynamic, late-binding programming environments that highly leverage the sparse nerd matrix out there -- like Smalltalk, Python, etc. -- are, however _still_ struggling to make it past the concrete barriers Jobs poured into the OO culture with the Mac.

    When Jobs passed up Smalltalk for Object Pascal, and then again, with Next, passed up Smalltalk for Objective C, he set a pattern that continues to this day when Sun passed up that sun-of-Smalltalk, Self and went with that son-of-Objective-C, Java.

    Gutting the superstructure of technology while maintaining appearances isn't leadership.

    1. Re:Jobs didn't get it. by Blakey+Rat · · Score: 1

      Whoa, hello. Apple had a BUDGET to work with. Xerox (for all practical matters) didn't. What did a PARC workstation cost? $25,000+? Something like that?

      While I'm sure that, philosophically, you're correct (and I'm not going to really debate them, because half of what you said is gibberish to me), but you have to remember that Apple is a corporation... they can't spend millions of dollars and years and years of R&D to get some high lofty goal of computing done, they had to get a product out the door to recoup their losses before the Apple ][ sales fell by the wayside.

      Hell, the Lisa was slow enough on its paltry 68000 CPU *without* a smalltalk interpreter.

      In any case, if the approach you prescribe had really be *SO* superior than Apple's, we'd have seen an Apple competitor using it, right? So... where were they?

  10. Where are they now? by clamboat · · Score: 1
    "By Monday morning, a preliminary version of Desktop Manager was ready for review by Atkinson's boss, Wayne Rosing, who was thrilled with the change."

    Wayne Rosing went on to a distinguished career at Sun, eventually heading the Sun Labs research division before taking the helm at FirstPerson, the semi-spinoff meant to commercialize Java. Wayne retired for a few years before being called by his friend Eric Schmidt to become a VP at Google, where he remains today. Hell of a career.

    I think Owen Densmore was also an alum of the Lisa project. He left Apple and moved to Sun where he created the object-oriented postscript system that was used to program NeWS, the Network Extensible Window System. I think the acronym might have been captialized in a funny way so it could be trademarked.

    What ties all this together? Both NeWS and Java were invented by James Gosling who is still at Sun, and is probably still doing cool stuff.

    1. Re:Where are they now? by cerebis · · Score: 1
      Mr Rosing might enjoy his Wikipedia reference... From Wikiquote
      Wayne Rosing born in approximately 1947, and still alive as of 27 February 2004, is Google's Vice President of engineering.
      Yes folks, someone born in ~1947 can amazingly still be alive in 2005! So surprising is this fact that it requires special emphasis. Ah, the computer industry. :)
  11. Article is hostile : mc68000 was 32 bit! not 16! by Anonymous Coward · · Score: 3, Interesting

    Article is hostile : mc68000 was 32 bit proccessor because it used 32 bit registers, had 32 bit math, and address more than 16bit addressing in linear addressing and used address registers than held 32 bits.

    the DATA bus and code bus used 16 wires.... b ut it was a goddamned 32 bit chip and this fact used to piss off intel x86 people for many years.

    So much so that they try to rewrite history with articles like this crap that ignore that the chip was 32 bits.

    A 64 bit processor for example DOES NOT have 64 bit data bus lines typically to the actual motherboard ram, and certainly NEVER EVER offers all 64 bit of addressing. (possibly some offer 48 in this universe though).

    but does that mean a 64 bit chip is not a 64 bit? no!! Jsut as the 68K was a genuine 32bit chip and almost no effort was needed when a full 32 bit wired version was offerred for sale.

    The article is hostile to history of the mac and lisa.

    by the way i bought both the years both shipped.

  12. The Price by themepsp · · Score: 0

    I wonder just how 'low end' it will be. Mac is so friggin expensive as it is.. ;-(

  13. The original message. by Baldrson · · Score: 4, Informative
    Here is the base message originating the "Jobs Didn't Get It" exchange:

    When Jobs brought technology in from Xerox PARC, and Adobe, he had the keys to the kingdom handed to him on a silver platter:

    1) A tokenized Forth graphics engine.

    2) Smalltalk.

    The Forth graphics engine was originally intended to grow from a programmable replacement of the NAPLPS videotex graphics protocol, into a silicon implementation of a stack machine upon which byte codes, compiled from Smalltalk would be executed. At least that's the direction in which I had hoped to see the Viewtron videotex terminal evolve when I originated the dynamically downloaded tokenized Forth graphics protocol as a replacement for NAPLPS in 1981 and discussed these ideas with the folks at Xerox PARC prior to the genesis of Postscript and Lisa.

    If Charles Moore could produce an economical 10MIPS 16 bit Forth engine on a 10K ECL gate array on virtually zero bucks back then, why couldn't Jobs with all his resources produce a silicon Postscript engine with power enough to execute Smalltalk?

    Somehow a Forth interpreter made it into the first Mac, as did Postscript, but Smalltalk just didn't.

    The Motorola 68000 family just didn't have the power. It may have been better than the Intel 86 family, but that really isn't saying much, now is it?

  14. not really by jbellis · · Score: 1

    if you maxed it out with a high-end Hercules graphics card and 640KB of ram, you were still a few hundred short of $5k.

    1. Re:not really by GigsVT · · Score: 1

      The drives were where you had to sink major money. Don't remember exact numbers but throwing in 2 360k drives or a hard disk, that would seriously push the price.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    2. Re:not really by jbellis · · Score: 1

      Oh yeah. Mine had a 20MB hard disk too, and one 360KB floppy.

      All for about $4800!

    3. Re:not really by Anonymous Coward · · Score: 0

      What year are you talking about? IIRC, Hercules cards weren't available until 85 or 86, which puts it several years after the Lisa came out. This is akin to giving someone shit for spending 300 bucks on a GeForce 3, cos gosh, you were able to get a GeForce 6800 for that price.

    4. Re:not really by GigsVT · · Score: 1

      Yeah hehe, the prices did drop a good amount from 80 to 85. I can't seem to find a site with a good price list from 1979-80 or so, but I really don't think it would be hard to hit $10k with a PC back then.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    5. Re:not really by OwnedByTwoCats · · Score: 3, Informative

      High-end PC:

      High-end PC: 640 KB RAM. No further expansion possible
      LISA: 1 MB RAM, expandible to 2 MB.

      High-end PC: One 360K floppy, one Hard Drive
      LISA: Dual 860K floppies, 5 MB Hard Drive.

      High-end PC/Hercules Graphics: 720x348 bin-mapped display (plus 80x25 chararcter)
      LISA: 720x364 bit-mapped display

  15. An addendum by Baldrson · · Score: 2, Interesting
    While Jobs had his failure of vision in not pursing a hardware stack machine similar to Moore's Tesler also should have pushed back on Jobs harder to get some form of Smalltalk onto the Lisa even with the Motorola chip. The reason is that there are optimization techniques involving type inferencing and dynamic code generation that had been researched and to some extent exploited at PARC, and have certainly become a mainstay of the JVM today. If the software engineering resources that were to be invested in programming an abortion like Object Pascal had been instead invested in the optimization technologies already researched it is likely the Motorola chip could have performed adequately and the software industry wouldn't have been set back more than decade.

    I don't mean to single Jobs out here since, of course, Gates is the guy who ultimately defected against civilization to become its richest man.

    1. Re:An addendum by Anonymous Coward · · Score: 0

      Since we can't rewrite history (well, we can rewrite it, but we can't change what actually happened), what should be done differently today? Have things equalized at all, or are glaring deficiencies still in progress?

    2. Re:An addendum by Baldrson · · Score: 2, Informative

      Things are starting to recover a bit with "AJAX" due to Javascript's more dynamic character. However, Gates can't get the garbage collector to work properly with IE for some reason so it can't be used as an application platform. Whether this is deliberate or not it certainly has helped protect his monopoly position by preventing web browsers from being becoming a viable cross-OS platform for network service applications. We'll have to wait and see if Ray Ozzie fixes the garbage collector before passing judgement. Thus far, it appears IE7 beta's garbage collector is still shit.

    3. Re:An addendum by xgamer04 · · Score: 1

      And if you agree with yourself enough times, you might trick people into thinking that you are building a consensus.

      --
      When you look at the state of the world, how can you not become a radical, liberal anarchist?
  16. Re:The Price - macs cheaper for Gflops by Anonymous Coward · · Score: 0

    for computing nothing but scientific calculations, especially (but not exclusively) math that can be vectorized, a dual G5 is cheaper per gigaflop than any computer for sale.

    macs are cheap

    they also sell something called a mac mini now too.

    notice how www.top500.org one year is dominated by powerpc chips? thats because www.top500.org is based on a real test used to compare actual supercomputer cluisters. A mac cluseter is typically 5 to 7 times cheaper than anything else.

    the 8gig of fast ram and THREE pci-x slots dont hurt either.

    or the 16 gigaflops a lowly 2Ghz dual g5 can do. (two Ghz * two chips * 2 floating cores * combined multiple AND add in one clock == 16gflops)

    and thats not even considering the astounding 128 bit huge registers on the generous altivec vector cores

    PRICE INDEED?!?! waht are you a goddamned pauper?

    price for what? getting nothing done per second?

  17. LISA by hhawk · · Score: 2, Interesting

    The Lisa wasn't cheap unless you were comparing to some mainframe. We had one at Bell Labs when I was there. Did some graphics on it, which was easier than trying to do graphics with TROFF/PICS...

    but it was also always breaking needing service and it didn't get a lot of use..

    --
    http://www.hawknest.com/
    1. Re:LISA by Anonymous Coward · · Score: 0
      The Lisa wasn't cheap unless you were comparing to some mainframe.
      And the Lisa wasn't slow unless compared to a mainframe. Or the Apple IIc.

      Whether in concept in 1979 or production in 1984, Lisa was an expensive plaything.

      The best Apple ever did in regards to market penetration for businesses was from
      1981-1983 with $2200 machines running real-world killer apps like 64k VisiCalc.

  18. you clearly have no idea what you're talking about by jbellis · · Score: 2, Informative

    Objective-C's object system and general philosophy is _very_ smalltalk-ish.

    Java is much more "C++ with some warts removed" than an Obj-C derivative. Obj C _is_ a "dynamic, late-binding programming environment." C++ and Java are not.

    Self is no more a son of Smalltalk than Java is a son of Obj C. They (Self and Smalltalk) both came out of PARC, but they are very different.

    I suspect you have no more idea about what went on at Apple than you do about programming languages, but I can't speak to that myself.

  19. Lisa was like taking home an attractive woman by geekoid · · Score: 2, Funny

    to find out she has a penis.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    1. Re:Lisa was like taking home an attractive woman by Anonymous Coward · · Score: 0

      So you get more bang for your buck?

    2. Re:Lisa was like taking home an attractive woman by Deitheres · · Score: 1

      What is this "taking home an attractive woman" that you speak of?

      --
      Just like driving a car:
      (D) to go forward
      (R) to go backward

  20. I disagree with the conclusion by AshPattern · · Score: 5, Informative

    My father, an early adopter-type, had a Lisa for his office, and it was the Lisa that I first learned how to program on.

    One of the most maddening things about programming the Lisa was that you couldn't make programs that integrated well with the Lisa office suite. Why? Because there was no API for the GUI. None. If you wanted a window drawn, you fired up QuickDraw and drew it yourself. Want a scroll bar? Do it yourself. Menus? Right.

    I ended up only using the development environment's console for my programs' interfaces. The development environment was also console based, probably for the same reasons. A couple of years later, Apple released the Lisa Toolkit that had all that stuff, after they had announced they were going to discontinue it.

    So in my opinion, it was the lack of software that killed the Lisa, not its high price. I mean, people were paying for it, and they wanted more. The ability to use proportional fonts was the killer feature to end all killer features.

    It's worth noting that Apple learned its lesson about making developers happy - the developer support program for the Macintosh has been one of the best.

    1. Re:I disagree with the conclusion by destinationmoon · · Score: 1
      This turns out not to be the case. There were definitely higher level primitives than Quickdraw available for GUI programming on the Lisa. If you look in the header files for the Apple Lisa Desktop Library Interfaces, you'll see such procedures as:
      PROCEDURE DrawMenuBar;
      PROCEDURE MenuSelect(startPt: Point; VAR whichMenu, whichItem: INTEGER);
      PROCEDURE ShowWindow(window: WindowPeek);
      PROCEDURE SetWindTitle(window: WindowPeek; title: Str255);
      PROCEDURE DragFrame(ptMouse: TPt; fDrawScrolls: TF; VAR ptNewBR: TPt);
      Dig further and you'll see that Apple had the Lisa Toolkit, which was what we'd now call a GUI framework, written in an OO variant of Pascal called Lisa Clascal. It had classes called TScrollBar, TImage, TDialogBox, TPaginatedView, and so on.
    2. Re:I disagree with the conclusion by Anonymous Coward · · Score: 0

      Lisa had a much worse problem than limited software: they wouldn't communicate with each other. Users could not even sneakernet files from one to another. Floppies formatted on one Lisa could not be read or written on another. This was an early Apple approach to DRM.

    3. Re:I disagree with the conclusion by AshPattern · · Score: 1

      I mentioned the Lisa Toolkit. It was announced after the discontinuation of the Lisa.

      Sure, Apple had it. Didn't do much good for the rest of the third-party developers.

    4. Re:I disagree with the conclusion by Jeff+DeMaagd · · Score: 1

      It's worth noting that Apple learned its lesson about making developers happy - the developer support program for the Macintosh has been one of the best.

      I was just reading an article that took a different view with respect to video and video hardware, claiming that Apple provides NO support for a third party to make their own video card drivers.

  21. xerox didn't copied apple by nazsco · · Score: 1

    there are thousands of anecdotes about rafkin convincing jobs and the rest to the managers to walk to palo alto to take a tour in xerox's labs, where they saw for the first time a computer with a GUI.

    but kudos to apple. they release it before.

  22. Comprehensive Lisa info at guidebookgallery.org by toby · · Score: 3, Interesting

    Marcin Wichary has compiled a great deal of Lisa information, from screenshots, ads, brochures and articles to posters and videos, at his site GUI Gallery Guidebook. Recent postings include 17 exclusive Lisa posters for download and enjoyment, and an interview with Dan Smith that reveals "The original trash can for Apple Lisa was supposed to have been an old, beat up alley trashcan, with the lid half open, flies buzzing around it and appropriate sounds as user put something inside."

    --
    you had me at #!
    1. Re:Comprehensive Lisa info at guidebookgallery.org by Lars+T. · · Score: 1
      --

      Lars T.

      To the guy who modded me down from perfect to terrible Karma - Apple haters still suck

    2. Re:Comprehensive Lisa info at guidebookgallery.org by Anonymous Coward · · Score: 0

      Yes, he does - transcribed, even: http://www.guidebookgallery.org/videos/lisachi98

  23. Article is a Troll by Anonymous Coward · · Score: 0

    Xerox introduced the GUI and Apple was only the first of many to copy it - big deal. Remember, before Apple went full into the Mac they had significant market share. So it could be strongly argued, that going GUI was Apple's downfall.

  24. commentary is off-base by idlake · · Score: 3, Informative

    I had a Lisa, and Apple made the same mistakes with the Lisa as Xerox had made with the Star: it was too expensive, in particular for the limited hardware and completely incompatible software you got.

    Claims that the Lisa represented significant technological innovation seem dubious to me. You need to compare the Lisa to the totality of R&D efforts around at the time, not just the Star. Xerox alone had Alto, Star, Smalltalk, and probably others. The GUI of the Lisa was an evolutionary change, and not always for the better; what was under the hood of the Lisa can charitably be described as pedestrian. It took Apple 20 years to catch up and finally adopt system software that even is in the same league as Smalltalk-80 (that's "80" as in "1980"; Smalltalk-80 is the language and platform that Objective-C and Cocoa are modeled on).

    Lisa's main significance was to be a prototype for, and cannibalized for, Macintosh (and it served as the main development machine for Macintosh apps for a while), but I can't think of any significant new technology it introduced.

    1. Re:commentary is off-base by Blakey+Rat · · Score: 2, Insightful

      Making a computer easy for the masses isn't a "technology," but it's still damned important. You talk from the typical open-source "code is everything, usability unimportant" viewpoint but you have to remember that for the average user, if they can't use a feature, that feature might as well not exist. Now you're right in that the user experience for a few reasons didn't really gel until MacOS 4 or so, but the Lisa was a thousand times better (for users) than anything that came before it.

      Alto was, from every account I've read, a beast to work with. Sure, it had a GUI, but its GUI wasn't modeled after anything in real life, unlike Apple's desktop metaphor. You can make a GUI that's just as dense as a CLI easily, and that's what Xerox had done.

      Anyway, I think your criticism is unfair.

    2. Re:commentary is off-base by nagora · · Score: 1
      but the Lisa was a thousand times better (for users) than anything that came before it.

      I think you underestimate how slow the Lisa was, the GUI was of no importance when waiting for it to do anything was an exercise in frustration.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
    3. Re:commentary is off-base by shakeedoo · · Score: 2, Informative
      I can't think of any significant new technology it introduced.

      Ummm.... menus?

  25. You are a Moron by Anonymous Coward · · Score: 0

    Yes, moving from CLI to GUI is why Apple's marketshare fell.
    It had nothing whatever to do with the proliferation of cheap IBM PC clones starting in the mid-80s, once the PC BIOS was reverse engineered by Phoenix.
    You fucking idiot.

    1. Re:You are a Moron by ScrewMaster · · Score: 5, Interesting

      Actually, the original PC BIOS wasn't so much reverse-engineered, as it was simply duplicated. IBM published the full annotated assembler listing in the original IBM PC technical manual. I still have a copy, somewhere. And in any event, because the BIOS was accessed via software interrupts (unlike the Apple ][ machines, which required direct calls into the ROM) it was pretty painless to duplicate the functionality, and IBM for its part didn't seem to care one way or the other. That simply encouraged the entire PC clone market to burgeon and spread. Contrast this to Apple Computer, which was continually trying to shut down competitors (like Franklin, for example.) Apple ][ clones had endless compatibility issues with applications that were making ROM calls that would fail on non-Apple firmware. IBM (by using INT13 software-interrupts to access BIOS services) eliminated that problem, and so long as a clone BIOS correctly emulated the original functions the system would work.

      About a year after the formal release of the Mac, I called up Apple's service people looking for a replacement gate array chip for an Apple // disk controller board. They wouldn't sell me the part (it was for one of my customers, I finally found a computer store that had a couple left) and I was told that "we recommend you purchase a Mac." Apple lost market share all right, and it wasn't because of the Mac ... it was because they treated loyal, long-standing customers like myself as dirt. After that experience (and several others like it) I went out and bought a PC and never looked back.

      And the parent poster isn't too far off base in one respect. Apple's market share did drop, not so much because of the move from DOS3.3/ProDOS to the Mac, but because of the way Apple treated their existing base of Apple ][ and //e customers. I mean, even when the Mac came out there was still a huge base of installed Apple //e business customers and Apple pretty much just threw them away, fully expecting them to migrate to the Macintosh. Migrate they did, but to the IBM PC.

      Never forget one thing: Apple was the incumbent, with all the advantages that confers. Atari and Commodore together couldn't market themselves out of a cardboard box and both eventually fell by the wayside. I look back at Apple Computer as a company that was at the right place at the right time with everything in its favor, only to squander opportunity after opportunity, relegating itself to second place. And such a distant second as to be almost out of the running, when they could have owned the market. They do seem to be making some good moves lately: let's see if they can keep it up.

      --
      The higher the technology, the sharper that two-edged sword.
    2. Re:You are a Moron by phillymjs · · Score: 2, Informative

      Holy crap, are you misinformed. Read some books on the history of the personal computer industry in the late 70s and the 80s. Start with Cringely's "Accidental Empires."

      Actually, the original PC BIOS wasn't so much reverse-engineered, as it was simply duplicated. IBM published the full annotated assembler listing in the original IBM PC technical manual.

      Yes, that was done purposely in the hopes that its existence could be used to quickly shut down any cloners via copyright infringement lawsuit. The grandparent poster was right on about Phoenix. They actually took out a huge insurance policy from Lloyd's of London that would protect them if IBM sued them, so IBM couldn't just use a nebulous lawsuit to legal-fee them into submission (as Hughes and the RIAA like to do today).

      IBM for its part didn't seem to care one way or the other.

      The hell they didn't! Aside from addressing shortcomings in the ISA bus, one of the main reasons IBM developed the very proprietary Micro Channel Architecture was to try to cram the cloning genie back in the bottle. IBM told the cloners they'd be happy to license the MCA, but demanded extortionate fees to do so, and apparently also wanted to be paid for every prior IBM PC clone that had been produced-- an offer that IBM had to know would be completely unacceptable.

      The cloners told IBM to pound sand, and went on building ISA-based IBM PC compatibles without paying IBM a dime, until PCI came on the scene. MCA went nowhere, and IBM's PC business continued its downward slide that started when Compaq was first to market with an 80386-based machine, and finished just last year when they sold the division to Lenovo.

      ~Philly

    3. Re:You are a Moron by alan_dershowitz · · Score: 1

      The PC BIOS code was still copyrighted, and the implementation of the clone BIOS was a clean-room implementation according to every source I have ever read. As for duplicating the functionality of the BIOS being easy, I can't speak to that. The PC ASM I had done in college would lead me to believe that it wouldn't be too complicated for an expert. But boy, I really wouldn't know.

    4. Re:You are a Moron by Anonymous Coward · · Score: 0
      The PC BIOS code was still copyrighted, and the implementation of the clone BIOS was a clean-room implementation according to every source I have ever read.
      The grandparent seems to have confused the histories of PC and Apple II clones. The PC BIOS was cloned by a clean-room process, first by Compaq and later by other companies like Phoenix. The Apple II clones made by Franklin actually used copies of the Apple II ROM, which Franklin brazenly argued wasn't covered by copyright. (The courts disagreed, which is why Apple succeeded in stopping clones where IBM did not.)
    5. Re:You are a Moron by ScrewMaster · · Score: 1

      I confused nothing. Yes, Franklin initially tried that and got nailed (I saw an early model which simply booted up saying "APPLE ][" across the top ... hilarious) which was why they were forced to eventually code their own. However, since a lot of applications depended upon ROM subroutines being located at specific addresses, Franklin machines had a lot of compatibility problems. Customers were treated to periodic ROM updates in order to address particular application failures, and it was generally a pain in the neck. Franklin actually had a nice system and the big keyboard was popular ... Apple never addressed that in the Apple ][ series, although the //e finally did. At one point I copied the ROM from my Apple ][ into a Franklin just to avoid all the crashes but still get the nice keyboard.

      Apple succeeding in stopping clones because they were aggressive in doing so (and except for a brief interval some years ago where they permitted Mac clones, they still are.) Other than the one attempt to sue Phoenix (where they lost and simply affirmed clean-room reverse-engineering as a legal methodology) IBM really didn't do a whole lot to stop the Clone Wars. Maybe that's because it wasn't possible at that point, but I don't think that's the case. If Apple could do it, a company as powerful as IBM could have used a thousand different legal maneuvers to stop it if they'd really wanted to do so. Presumably IBM felt it was in their best interests to allow the competition, or maybe they just didn't care. But for us, the end result was the same.

      --
      The higher the technology, the sharper that two-edged sword.
    6. Re:You are a Moron by ScrewMaster · · Score: 1

      It's a heck of a lot more complicated nowadays, but in 1981 the BIOS in an IBM PC was pretty straightforward, nothing particularly tricky about it. It's not like it was a complete application or operating system in itself, it was just a collection of utility routines for testing memory, initalizing hard drives, allowing simple text output, crude COM port handling, RTC stuff, and so forth. In a lot of ways, the Apple ][ Monitor ROM was far more sophisticated in the things it could do (anyone that tells you that Steve Wozniak isn't a genius is wrong.)

      --
      The higher the technology, the sharper that two-edged sword.
    7. Re:You are a Moron by Fujisawa+Sensei · · Score: 1

      And who's fault was the proliferation was the PC Clones?

      Could it be that Apple and Commodord were still using 1979 Chips while the PC builders were using 386's?

      Could it be that Apple was lying to customors by saying the the AppleIIg would be supported, after the Mac was introduced and then canning support for the IIg the day Mac was out?

      Could it be that the Mac was little more than an doorstop when it was released? Becuase it had half the memory it needed and was un expandable.

      Could it be Commodore didn't descent system untill the A500 was released? (Kickstart on floppy).

      Could it be that both Commodore and Apple kept trying to push 2nd rate systems on customers? A600, CD32, CDTV, A1200, Mac classic color, Mac se/30, when people were buying 486s? with descent harddrives. Those systems should have been released in 1988, not 1993!

      Could it be that the Quadra should have been the saving grace of Apple, (And in many respects was.) But nobody know how to sell it or what it could do because Apple kept changing the specs and not telling or training anybody?

      Could it be that Commodore and Apple both alienated 3rd party vendors. (Apple by not letting them in, and Commodore by not allowing for cross compatibility. A2000 vs A3000 compatibility for the Video Toaster.) And Apple did have some clones for awhile, but they were pretty much garbage.

      Could it be that both companies had the edge in vision and technology, but rested on their laurals, and failed to press it? because they wanted low volume high profit machines, and made their low end machines overpriced and incompatible, hardwarewise with the industrial grade boxes.

      The reason we have to deal with garbags OS's like XP on today is because both CBM and Apple failed. In fact Apple has still failed because there are applications that will not work because Apple will not implement multiple event threads within OS-X https://bugs.eclipse.org/bugs/show_bug.cgi?id=6738 4#c14 !

      --
      If someone is passing you on the right, you are an asshole for driving in the wrong lane.
    8. Re:You are a Moron by Sabah+Arif · · Score: 1

      I take a couple issues with your assessment (though I agree with most of it). The GS was supported for six years. From 1986 to 1992. The original Mac was expandable. Several venders sold memory upfrades, and there were also hard drives that interfaced through the floppy drive port. The SE/30 was very powerful, had a large hard drive and was inexpensive compared to comparable 386's. The clones got great reviews from MacAddict, which usually rated them higher that Apple Macs for better value/performance.

    9. Re:You are a Moron by Anonymous Coward · · Score: 0

      Could it be that the answer to all those questions is 'yes'?

      Could it be that you're an obnoxious twat?

      Could you be any more pedantic yet overly simplistic?

      Could it be that your writing style makes me want to pull off your head and shit down your neck?

      The reason we have to deal with gasbag pukes like YOU is because YOU FAIL IT.

    10. Re:You are a Moron by Fujisawa+Sensei · · Score: 1

      It warms my heart to see annoy a spinelss AC. I'm going to have to post more messages exactly like this. :D

      --
      If someone is passing you on the right, you are an asshole for driving in the wrong lane.
  26. Objective-C is not even close to Smalltalk by idlake · · Score: 1

    Objective-C's object system and general philosophy is _very_ smalltalk-ish.

    Yes, Objective-C has late binding and limited dynamic typing, but that's only a tiny part of what Smalltalk offered in 1980.

    The sad fact is that it is Apple, more than any other company, that is responsible for the bloated toolkits and libraries that we see today: they set the pattern with the Lisa and the Macintosh toolboxes, and everybody else copied it, up to and including Java and C#. And while Objective-C happens to copy some of Smalltalk's nice object features, it is has grave deficiencies in areas like run-time safety, reflection, and resource management.

    1. Re:Objective-C is not even close to Smalltalk by shmlco · · Score: 1
      "The sad fact is that it is Apple, more than any other company, that is responsible for the bloated toolkits and libraries that we see today..."

      Oh please. Probably the Apple II or the orginal IBM PC were the last micro's where you could count on knowing the in's and out's of every byte running on the machine. And even those had BIOS's.

      Once you get into interactive GUI's, you don't want every single application having to reinvent Quickdraw, or a menuing system, or a windowing system, or a file system, or an event manager, or controls, or printing, or... whatever.

      Especially if you want to maintain uniform behaviour, interoperability, and a consistent look and feel across applications.

      Of course, today the real problem lies in the fact that too many people refuse to learn all of those "bloated" libraries and toolkits, and instead choose to roll their own incomplete, inconceived, buggy, and totally undocumented solutions to problems that have already been solved.

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
  27. Re:Article is hostile : mc68000 was 32 bit! not 16 by NormalVisual · · Score: 4, Informative

    Interestingly, the article also refers to the 8088 as a 16-bit processor, which is an 8-bit processor if one uses the same criteria that you'd have to in order to call a 68000 "16-bit".

    68000: 32-bit registers, 24-bit address bus (linear addressing), 16-bit data bus
    8088: 16-bit registers, 20-bit address bus (segmented addressing), 8-bit data bus

    I frankly don't consider the 8088 and 68000 even remotely comparable - it's far easier to program for (and design hardware around, IMHO) the 68K. The only difficulties that I knew of anyone really experiencing when moving to the 68020 and other full 32-bit variants was that people had gotten into the really bad habit of using the upper 8 bits of the A registers for general storage, which would break things on a '020 horribly. Even so, it was certainly nothing like the EMS/XMS hell that PC programmers had to go through just to use memory above 1MB because of the limitations of the 8088 memory architecture.

    --
    Please stand clear of the doors, por favor mantenganse alejado de las puertas
  28. What is an "object oriented UI"? by Tablizer · · Score: 3, Funny

    OOP is a technique for organizing programming code, not UI's. Thus, what exactly is an OO UI? I am not sure if there is only one way to interpret a UI analog to programming code code techniques. In fact, nobody can even agree on a clear definition of OO in the code world. If you want to start a bar fight in OOP forums, ask for a precise definition of OO, and e-chairs start flying.

    1. Re:What is an "object oriented UI"? by PapayaSF · · Score: 1

      It is confusing, but they mean that the user interacts with documents ("objects"), instead of directly with applications or the Filer:

      Dan Smith, a major contributor to the desktop interface, had created the Lisa's first interface, the Filer. The Filer asked a user a series of questions about what task the user wanted to accomplish, and when enough questions were answered, the tasks were executed and the Filer shrank to the background.

      --
      Q: What does the "B." in Benoit B. Mandelbrot stand for? A: Benoit B. Mandelbrot
    2. Re:What is an "object oriented UI"? by Tablizer · · Score: 1

      It is confusing, but they mean that the user interacts with documents ("objects"), instead of directly with applications or the Filer:

      Is not an application also an "object"? True, we may want to hide it from the user for practical purposes, but that is another issue.

    3. Re:What is an "object oriented UI"? by Anonymous Coward · · Score: 0

      ask for a precise definition of OO

      Well, that's easy. OO is the classical type system with the addition of 1) type inheritance and 2) polymorphic operators. Everything else is syntax.

      See, for instance, The Third Manifesto for a more rigorous treatment on the topic.

    4. Re:What is an "object oriented UI"? by Tablizer · · Score: 1

      Well, that's easy. OO is the classical type system with the addition of ...

      Dynamic OO languages generally don't view stuff as "types". TTM generally view things thru a static lens.

    5. Re:What is an "object oriented UI"? by drsmithy · · Score: 2, Informative
      Thus, what exactly is an OO UI?

      OS/2's Workplace Shell is generally considered the best example.

    6. Re:What is an "object oriented UI"? by Anonymous Coward · · Score: 0

      If you want to know what an 'object oriented UI' is, download squeak and give it a try. Squeak is a continuation of the original Smalltalk-80 project.

      Squeak is an object-oriented language, system, environment and desktop. Everything you see on the desktop (every icon, every window, every title-bar, every button, every menu, every menu item, every piece of text, every piece of selected text) is an object. You can interactively reference and manipulate every single object on the desktop as an object in the object-oriented language. You can find its class in the class heirarchy, you can get hold of the actual object as a 'piece of software'. You can inspect and deconstruct it in any number of different ways. You can do this from the gui, and you can do this from a text-based interface. Everything is seemlessly integrated, and the object-oriented language/system/environment is the key to it all.

      That is an object oriented GUI.

      Smalltalk-80 introduced the concept of OO, defined it and implemented it. If you want to know what a real object oriented language feels like, give it a go. Java is just a procedural language with object capability bolted onto the outside of it. The difference is the paradigm you use to conceptualise what you are doing. Java - procedural code in an object oriented context. Smalltalk - OO pure and simple.

    7. Re:What is an "object oriented UI"? by Tablizer · · Score: 1

      This seems to be saying that an "object" is an icon that you can click on, move, etc. However, it could in theory also correspond internally to a record in a database instead of a SmallTalk class. An ST class is not the only way to represent such internally.

  29. spot on by idlake · · Score: 0

    I fully agree: Apple's decision to go with Object Pascal, and then a collection of assembly-language toolboxes had really bad consequences for the industry, consequences that we suffer from to this day.

    I disagree, though, with your assessment of the relationships of the different languages; Java, unfortunately, is not the son of Objective-C, it is the son of Object Pascal and C++. Objective-C would have been the right language for the original Macintosh--close to the machine to allow Apple to meet their price targets, but dynamic enough to eventually turn into something decent. Instead, Appple led the industry on a 20 year detour into static object-oriented languages and, worse, "toolboxes", and is now returning to a dynamic language that is 20 years out of date.

    Fortunately, C# and Java do address this problem. While the C# and Java languages themselves are cumbersome and static, their runtimes are sufficiently powerful to put decent dynamic languages on top of them and still interoperate with the unwashed masses of static object-oriented programmers.

    1. Re:spot on by oaklybonn · · Score: 1
      Java, unfortunately, is not the son of Objective-C, it is the son of Object Pascal and C++.

      Wrong.

      Java Was Strongly Influenced by Objective-C

      NeXT's mach-o & java even share the same magic number:

      /usr/share/file/magic:

      # mach file description
      #
      # Since Java bytecode and Mach-O fat-files have the same magic number the test
      must be preformed in the same "magic" sequence to get both right. The long
      at offset 4 in a fat file tells the number of architectures. The short at
      offset 4 in a Java bytecode file is the compiler minor version and the
      short at offset 6 is the compiler major version. Since there are only
      only 18 labeled Mach-O architectures at current, and the first released
      Java class format was version 43.0, we can safely choose any number
      between 18 and 39 to test the number of architectures against
      (and use as a hack).


      --ob
    2. Re:spot on by Anonymous Coward · · Score: 0

      It is sad how Java managed to lose most of what actually makes Objective-C good.

    3. Re:spot on by idlake · · Score: 1

      Wrong. Java Was Strongly Influenced by Objective-C

      It doesn't matter who Naughton's muse was, Java's object model is close to C++, and very different from Objective-C.

    4. Re:spot on by Anonymous Coward · · Score: 0
      [Patrick Naughton:] So, naturally when I stayed to start the (eventually) Java project, Obj-C had a big influence. James Gosling, being much older than I was, he had lots of experience with SmallTalk and Simula68, which we also borrowed from liberally.


      Well, which only goes to show that neither Naughton nor Gosling can use ignorance as an excuse; they messed up Java even though they really should have known better.
    5. Re:spot on by feijai · · Score: 0
      It doesn't matter who Naughton's muse was, Java's object model is close to C++, and very different from Objective-C.
      What the hell? Do you know anything about Java? Java has:
      1. Single Inheritance
      2. Interfaces (a direct copy from Obj-C's Prototypes)
      3. Wrapper classes for basic data objects (another direct copy)
      4. All virtual methods
      5. Late binding
      6. Late method calls which throw an exception on call-time if the object cannot respond to it.
      7. No stack allocation
      8. No pass-by-reference
      In what way does this remotely resemble C++'s object model? Java is very very far away from how C++ does things internally. Don't get wrapped up with the intentionally similar syntax.
  30. Remember, the original Mac didn't sell well either by Animats · · Score: 4, Informative
    It's worth remembering that the original Macintosh was a flop. The attempt to cost-reduce the Lisa resulted in a machine too weak to do much of anything. Remember the original specs: 128K, no hard drive, one floppy. Ever use one? Ever actually try to get work done on one? You had to fit the OS, the app, and your documents on one floppy. Or you could get an external floppy, which made the thing marginally useable. It was cute, but not productive.

    The lack of a hard drive was the killer. By the time the Mac came out, IBM PCs had a hard drive, so Apple was playing catch-up. Apple had tried building hard drives (the LisaFile), but they were slow and crashed frequently. But at least the Lisa had a hard drive. Third parties added a 10MB hard drive to the Mac in early 1985, which brought performance up to an acceptable level. Some people say that third-party hard drives saved the Mac. But Apple fought them tooth and nail. Apple finally came out with a 20MB external hard drive for the Mac in 1986. This was very late; IBM PCs had been shipping with hard drives for five years.

    Sales for the Mac were well below expectations. Apple had been outselling IBM in the Apple II era. (Yes, Apple was once #1 in personal computers.) In the Mac era, Apple's market share dropped well below that of IBM.

    What really saved the Mac was the LaserWriter, which launched the "desktop publishing" era. But that required a "Fat Mac" with a hard drive and 512K. By then, the Mac had reached parity with the Lisa specs, except that the Lisa had an MMU and the Mac didn't. The Lisa also had a real operating system, with protected mode processes; the Mac had "co-operative multitasking" in a single address space, which was basically a DOS-like system with hacks to handle multiple psuedo-threads.

    The MMU issue was actually Motorola's fault. The 68000 couldn't do page faults right, and Motorola's first MMU, the Motorola 68451, was a terrible design. The Lisa had an Apple-built MMU made out of register-level parts, which pushed the price up.

    Apple might have been more successful if they'd just stayed with the Lisa and brought the cost down as the parts cost decreased. They would have had to push Motorola to fix the MMU problem, but as the biggest 68000 customer, they could have.

  31. gui by Anonymous Coward · · Score: 0

    apple set the pop standard for user interfaces way back when, gates got rich perfecting it and getting it to the masses, kde on the other hand is one of the world best kept secrets which is better than both.

  32. No, you don't get it. by Tablizer · · Score: 2, Informative

    You have to remember that the microcomputer hardware was sloooow and expensive back then. Compiled "static" languages simply run faster, even if they take longer to program with.

    Personally, I feel that GUI's should be mostly declarative based such that one stores descriptions and attributes of windows and widgets rather than use boatloads of "new Window(...)" and "new Widget(...)" commands in code. Events are then bound to a programming language of choice. Declarative approaches are usually easier to adapt to multiple programming languages. Why does the world still want to hard-wire GUI's to one and only one programming language? Java still made this same mistake in 1996, almost 20 years after Job's alleged "big mistake". I see no reason why it *must* be this way. It does not make sense to reinvent GUI engines for each of the 100 or so common languages. They like to talk about "reuse", but don't practice what they preach.

  33. document centric... by hitmark · · Score: 1

    hmm, it would be realy interesting if this was brought back again.

    today its to much focus on what apps one use, not what one want to do.

    i all to often see people having photoshop installed when all they do is look at digital photoes...

    --
    comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    1. Re:document centric... by maxwells_deamon · · Score: 1

      Start a MS office 2004 application. (for Mac) It starts with a window with a bunch of documents of various types for you to chose from. This is borrowing from the older Works interface.

      For example, I open PowerPoint and I get a Window with a bunch of document templates on it. If I select Excel Workbook, Excel opens up with a blank workbook and PowerPoint goes into the background.

      On the Lisa, you have a folder call Stationary that has blank copies of documnents. You just double click on one and the application starts. The document is saved with a name that includes the date if you do not fo out of the way to change it. Not sure what happens if you add an application from some other vendor to your Lisa. My Lisa only has Apple applications on it.

      Of course you can build somthing like this is windows on the desktop with shortcuts and just remember to save everything under a new name.

    2. Re:document centric... by drsmithy · · Score: 1
      hmm, it would be realy interesting if this was brought back again.

      Back ? UIs have been moving more and more away from being application-driven and towards being document-driven for the last 25+ years. Methinks you never really used computers before the 90s :).

      today its to much focus on what apps one use, not what one want to do.

      I think you've got that backwards. Interfaces today are *very* much document-centric, not application-centric.

      That many users treat them mostly as application-centric, is not the fault of the interface, but the person who taught them how to use it.

  34. Self is a Smalltalk by Jecel+Assumpcao+Jr · · Score: 1

    I don't know why some people think Self is a very different language than Smalltalk-80. With the optional parser and GNU Smalltalk classes you can even file in Smalltalk-80 code and run it.

    http://research.sun.com/self/papers/smalltalk.pdf

    I don't remember who said "Self is like Smalltalk, only more so" but that is a great definition. To avoid having to repeat this discussion all the time I have renamed my Self/R project as Neo Smalltalk.

  35. Sculley fucked Apple (nt) by Anonymous Coward · · Score: 0

    'nuff said

  36. Kinda makes me think... by Anonymous Coward · · Score: 0

    > The Apple engineers were not the only ones impressed by the visit. The researchers at Xerox, long discouraged by Xerox's inability to release a product based on the technology developed at PARC, were impressed by Apple's seeming willingness to implement advanced technologies in their products.

    Xerox --> Microsoft
    +
    Apple --> Linux
    =
    Internal wars?

  37. Re:Article is hostile : mc68000 was 32 bit! not 16 by Blakey+Rat · · Score: 1

    Interestingly, the article also refers to the 8088 as a 16-bit processor, which is an 8-bit processor if one uses the same criteria that you'd have to in order to call a 68000 "16-bit".

    No, it makes the rather confusing assertion that:

    1) Apple decided that a 16-bit machine was necessary for what they were trying to accomplish.
    2) Apple considered many CPUs for the LISA, including the 8088.

    So, you see, the article doesn't state that the 8088 is a 16-bit CPU, it just states that Apple considered it despite earlier agreeing that it wouldn't be sufficient. Based on the places I've worked, that happens quite a bit in the business world.

  38. Another good site is by stevey · · Score: 2, Informative

    Another good site full of first-hand descriptions of how early Apple development was done is http://folklore.org/.

    I've never owned a Mac, and am too young to have been involved in earlier developments - but that site does make it all seem very impressive.

  39. The Mac's other salvation: square pixels by PapayaSF · · Score: 4, Informative

    The Lisa, like other computers of the day, had rectangular pixels. The Mac's introduction of square pixels allowed true WYSIWYG, and was crucial to desktop publishing and computer art. The Mac's still strong position in the graphic arts industry is a direct result.

    --
    Q: What does the "B." in Benoit B. Mandelbrot stand for? A: Benoit B. Mandelbrot
    1. Re:The Mac's other salvation: square pixels by jcr · · Score: 1

      I'll just point out that many other companies had already shipped displays that had 1:1 pixel aspect ratios. Scion corporation sold a 640x480 graphics card for the IBM PC in 1982.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    2. Re:The Mac's other salvation: square pixels by njh · · Score: 2, Interesting

      How does square pixels allow true WYSIWYG? The screen representation is still an approximation (unless you are printing on a B&W printer with 72DPI). One thing that we've learnt since is that tall pixels are better value, as the human eye needs greater horizontal resolution than vertical (c.v. cleartype, lcd mode in freetype, or whatever). I would rather have a 2:1 tall-pixel display than a /2:/2 once the resolution goes above 100dpi - better visual resolution for a given investment in pixels. Quickdraw even supported non-square pixels in the original firmware.

      (And IBM PCs had square pixels in some modes too in 1985)

  40. 80386 better than 68000. by tjstork · · Score: 3, Informative

    Time to bust out the holy wars.

    I like the 68000 because it has so many registers but I think all in all in the 80386 is the better CPU.

    For reference, consider:

    http://www.freescale.com/files/32bit/doc/reports_p resentations/MC680X0OPTAPP.txt

    http://www.df.lth.se/~john_e/gems/gem0028.html

    http://linux.cis.monroeccc.edu/~paulrsm/doc/trick6 8k.htm

    http://www.csua.berkeley.edu/~muchandr/m68k

    Right off the wheel, we notice that the 68000 did not support 32 bit multiplecation at all. Doesn't sound too much like a 32 bit chip to me. Compare that to Intels quirky IMUL, which I believe puts the result into EAX, EDX to get a real 64 bit result.

    Integer math was faster clock for clock on the 386. Compare things like 68K register addition to Intel register addition. There's no comparison.

    Compare

    http://www.gamedev.net/reference/articles/article2 14.asp#ADC

    to

    http://www.df.lth.se/~john_e/gems/gem0028.html

    Whenever you did any 32 bit pointer math on a 68k, you paid a huge, huge performance penalty. It was always more efficient to do things in 16 bit PC relative addressing.

    The 68K had no concept of isolated memory or tasks. So systems like the Amiga and the Macintosh would run without any isolation between processes. I was an Amiga fan boy and I used to get that GURU meditation error so much that it was not even comical.

    The tragedy of the 386 architecture was actually Microsoft and not Intel. DOS and Windows did not use even the 386 chip to its fullest capability for memory management. MS users would have to wait until Sept 1995, almost 10 years after the 386, for a true 32 bit operating system.

    --
    This is my sig.
    1. Re:80386 better than 68000. by Anonymous Coward · · Score: 0

      The 68000 can multiply 32bit numbers by 16bit numbers,
      just not 32bit by 32bit

    2. Re:80386 better than 68000. by Alioth · · Score: 1

      Of course the 386 was better than the 68000 - it was considerably newer! The 68000 was a mainstream processor when Intel's 8086 was Intel's mainstream processor.

    3. Re:80386 better than 68000. by Misagon · · Score: 4, Informative

      You are comparing a newer generation to an older.
      The 68000 came in 1979. The i386 was introduced first in 1986.
      The 68020 however, introduced in 1987 did support 32x32->64 bit multiplication and division between all data registers. An external MMU was available, but it was unused by MacOS and AmigaOS.
      And the 68000 has had nice relative addressing modes from the start. I don't understand what you are referring to. (I have written machine code for all of these.)

      --
      "We mustn't be caught by surprise by our own advancing technology" -- Aldous Huxley
    4. Re:80386 better than 68000. by master_p · · Score: 1

      The comparison was between 8086 and 68000, i.e. Mac vs PC XT, not with 80386.

      Even with 80386 though, PCs were inferior to Macs, because there was no proper 32-bit protected-mode O/S for 80386 (unless you count expensive Unix).

      Let's not forget that the 68000 was the CPU used in most coin-ops...the most impressive of which was Outrun and other SEGA super-scaler games. All the SEGA machines used two 68000 plus a group of custom chips to do the graphics job...the 68000 was particularly co-operative with co-processors, unlike the 80386, I assume mainly because the 68000 had memory-mapped I/O, whereas the 80386 had I/O ports.

    5. Re:80386 better than 68000. by Anonymous Coward · · Score: 0
      MS users would have to wait until Sept 1995, almost 10 years after the 386, for a true 32 bit operating system.
      You must be confused. MS did not release any 32-bit operating system in 1995...
    6. Re:80386 better than 68000. by drsmithy · · Score: 1
      MS users would have to wait until Sept 1995, almost 10 years after the 386, for a true 32 bit operating system.

      This is not correct. Their first choice would have been OS/2, followed closely by Windows NT. Not to mention that as of Windows/386 (ca. 1988), DOS-based Windows was starting to become "32 bit" (was using >640k RAM, could pre-emptively multitask DOS boxes, etc).

      DOS-based Windows was always an evolving product. To say "Microsoft users" didn't get any 32-bit goodness until Windows 95 is simply wrong.

    7. Re:80386 better than 68000. by drsmithy · · Score: 1
      Even with 80386 though, PCs were inferior to Macs, because there was no proper 32-bit protected-mode O/S for 80386 (unless you count expensive Unix).

      Firstly, there was OS/2 and Windows NT or more esoteric choices like NeXTSTEP. Not to mention that as of Windows/386 (ca. 1988) the OS was becoming "32 bit".

      Secondly, MacOS didn't have protected memory at all (until OS X, ca. 2000) and wasn't "32 bit" until System 7, in 1991 (and then only on "32 bit clean" Mac hardware).

      In technical terms, DOS-based Windows and "Classic" MacOS were basically neck and neck in terms of technical features until Windows 95 (and Microsoft had the advantage of Windows NT for "pro" users, whereas Apple had nothing).

    8. Re:80386 better than 68000. by tjstork · · Score: 1

      I primarly meant process isolation for mainstream computer users. People buying a computer at the local store were not going to get it preloaded with OS/2 or WNT. Windows 95 was the first consumer MS product that offered both a 32 bit OS, and, had some degree of process isolation.

      --
      This is my sig.
    9. Re:80386 better than 68000. by tjstork · · Score: 1

      It's an academic point. The mainsteam computers that used these parts were only a two years apart, and that's a lot different.

      Apple Macintosh was introduced in 1984
      Commodore Amiga was introduced in 1985
      Compaq 386 introduced in 1986

      --
      This is my sig.
    10. Re:80386 better than 68000. by NormalVisual · · Score: 1

      Firstly, there was OS/2 and Windows NT or more esoteric choices like NeXTSTEP. Not to mention that as of Windows/386 (ca. 1988) the OS was becoming "32 bit".

      Given that NT wasn't introduced until almost 10 years after the Mac, and only a year before Apple went to the PPC architecture, I don't think it really can be considered here. OS/2, while a true pre-emptive multitasking system (and a damn good one IMHO), didn't come out until about the time the second-generation Macs did (1987), and didn't even have a GUI until more than a year later. It's interesting that you mention the NeXT OS, since the original NeXT machines ran just fine on 68030 CPUs and it wasn't until after the 68K-based machines were discontinued that the NeXT system was ported to the Intel architecture. Windows/386 was basically a 16-bit window/event manager bolted on top of DOS, with usage of 386-specific features limited to XMS memory support and support for multiple real-mode DOS applications, and you *still* couldn't directly allocate a chunk of memory larger than a megabyte IIRC. Support for printing for any of the systems mentioned (except for NeXT) wasn't anywhere comparable to that offered by Apple at the time.

      Secondly, MacOS didn't have protected memory at all (until OS X, ca. 2000) and wasn't "32 bit" until System 7, in 1991 (and then only on "32 bit clean" Mac hardware).

      "32-bit clean" referred to software, specifically an application that properly used the 68K address registers for addresses ONLY, and thus could run on a 68K-family chip with a 32-bit address bus.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    11. Re:80386 better than 68000. by drsmithy · · Score: 1
      Given that NT wasn't introduced until almost 10 years after the Mac, and only a year before Apple went to the PPC architecture, I don't think it really can be considered here. OS/2, while a true pre-emptive multitasking system (and a damn good one IMHO), didn't come out until about the time the second-generation Macs did (1987), and didn't even have a GUI until more than a year later.

      The comment I was replying to was talking about the 386, and PCs being "inferior" because "there was no proper 32-bit protected-mode O/S for 80386" - it seemed obvious to me the context of discussion was in the era of 32 bit MacOS, which started with System 7 in 1991. Therefore, I though comparisons with NT (1993) and OS/2 (1988 - 89) were quite valid. I can't see how the poster I was replying to could be seen as referring to the original Mac.

      Windows/386 was basically a 16-bit window/event manager bolted on top of DOS, with usage of 386-specific features limited to XMS memory support and support for multiple real-mode DOS applications, and you *still* couldn't directly allocate a chunk of memory larger than a megabyte IIRC.

      Windows/386 started the metamorphisis of DOS-based Windows into a 32 bit, pre-emptible, protected mode OS. It provided virtualisation for most of the hardware, allowing simultaneous DOS applications. The memory management part I can't comment on, I wasn't a developer at the time, but you're probably right.

      As I said, I think it's fair to view MacOS and DOS-based Windows as pretty much on par technically until Windows 95. Both got comparable features at roughly the same time, and both had some pretty big albatrosses around their necks (68k emulation, DOS/x86 legacy) by the mid 90s.

      "32-bit clean" referred to software, specifically an application that properly used the 68K address registers for addresses ONLY, and thus could run on a 68K-family chip with a 32-bit address bus.

      IIRC, it also referred to the hardware - in particular, whether the machine had "32 bit clean" ROMs.

    12. Re:80386 better than 68000. by master_p · · Score: 1

      Firstly, there was OS/2 and Windows NT or more esoteric choices like NeXTSTEP. Not to mention that as of Windows/386 (ca. 1988) the OS was becoming "32 bit".

      OS/2 was in the design stage when the 80386 came out (in 1986). Windows NT was only a thought in the back of Microsoft's mind. NextStep did not run on 80386. There was no Windows/386 fully 32-bit product then.

      Secondly, MacOS didn't have protected memory at all (until OS X, ca. 2000) and wasn't "32 bit" until System 7, in 1991 (and then only on "32 bit clean" Mac hardware).

      Yeap, MacOS did not have protected memory, but it was fully 32-bit. C programs have 4 GB of memory to play with, unlike the PC programmer which fought with memory models, near and far pointers, memory extenders etc.

      In technical terms, DOS-based Windows and "Classic" MacOS were basically neck and neck in terms of technical features until Windows 95 (and Microsoft had the advantage of Windows NT for "pro" users, whereas Apple had nothing).

      Nope, not even close. Windows was just a shell over DOS, whereas MacOS was a graphical O/S itself. There was no 16-bit mode in MacOS. The Mac's ToolBox was in ROM, which means the computer booted in the GUI, whereas in DOS/Windows you have to load DOS first, then start Windows manually, going through a series of text screens first. MacOS supported drag-n-drop throughout the system, whereas DOS/Windows did not. MacOS had creator information resource forks in its files, whereas Windows used centralized control with .ini files. Macs can be networked with AppleTalk, whereas in Windows you needed third party products. Macs could output professional printings in lazer printers, whereas in Windows you only had ugly raster fonts (truetype came much later).

      Dos/Windows and MacOS could never be more different, from a technical point of view. And don't get me started in the usability front.

    13. Re:80386 better than 68000. by Smurf · · Score: 1

      And the Macintosh II was released on March 2, 1987.

      From that point of view it makes more sense to compare the CPU of the first 386 Deskpro with the 68020 of the Mac II as opposed to the 68000 of the original Mac, as they are closer in time.

  41. Re:The Price - macs cheaper for Gflops by Anonymous Coward · · Score: 0

    While you build your garage supercomputers computnig rc5 numbers the rest of us has real problems to attend to, and an xserve with a dogslow OS X isn't going to cut it for REAL problems.

  42. Sun changed everything by rogergregory · · Score: 1

    I bought my first Sun 100 (serial #82 1M ram 80M disk) later upgraded to Sun 100U in Aug 1982. When upgraded to bsd 4.3 in 1983 it had a GUI, so when the Lisa came out, so what? Admittedly, it cost over $20,000 but Moore's was in effect so, the Lisa a year later was about the same at $10,000. In 1984 when the Mac came out at about $2,500, it was below the price curve by 50% but it didn't have a disk! The Lisa had great software, what there was of it. The Sun had a real Unix, what more could you ask for?

    All of the above machines had some version of the Motorola 68000, so where other people saw a Mac, I saw a very crippled Sun, needless to say I wasn't impressed, and I'm still not impressed.

    I'd say the Sun is much more the model of what Linux is today, for better or worse.

  43. Interesting ad by boomgopher · · Score: 1

    I think it's kind of cool how in the Lisa ad below:

    http://www.jagshouse.com/images/lisa4.jpg

    The real world images above the icons look like the photorealic icons used in OS X (no shit, yes they're real, but i.e. the lighting, camera angle, etc.)

    --
    Your hybrid is not saving the environment. Its purpose is to make you feel good about buying something.
  44. Some corrections by flimflam · · Score: 2, Informative

    The Fat Mac had neither a hard drive nor cooperative multitasking (unless you count desk accessories, but the original Mac had those too). There was Switcher which gave the ability to switch between apps, but there was no multitasking -- the background apps were completely suspended. Cooperative multitasking didn't come 'til Multifinder with System 6.

    Internal hard drives didn't come 'til, I want to say Mac II? Was there one for the SE?

    --
    -- It only takes 20 minutes for a liberal to become a conservative thanks to our new outpatient surgical procedure!
    1. Re:Some corrections by transient · · Score: 1
      Was there one for the SE?

      The SE/30 had an internal hard drive, but was produced after the Mac II and was really just a Mac II in an SE case.

      --

      irb(main):001:0>
    2. Re:Some corrections by Animats · · Score: 1
      Internal hard drives didn't come 'til, I want to say Mac II? Was there one for the SE?

      There was a Mac SE FDHD, but that wasn't until 1989. The Macintosh Plus, released in 1986, was the first Mac with a SCSI port, and Apple sold a matching hard drive. That was the first Mac with a supported hard drive. There had been previous third-party attempts to add a hard drive, but they either required internal mods or worked, slowly, through the printer port.

      Multifinder originally was an add-on for System 4. It came standard with system 6 but wasn't installed by default. Not until System 7 was it standard. Many early apps wouldn't run under MultiFinder, and the transition generally required application upgrades. Internally, it was a horror, since it began as an external add-on above a single-thread OS, not as a scheduler installed in the core system. Developers used to refer to the Mess Inside.

    3. Re:Some corrections by BandwidthHog · · Score: 1

      The SE/30 was a IIcx in an SE case, the ‘x’ designating 68030. The Mac II was a 68020. (If they had stuck to their naming conventions, it would have been called the Mac SEx.)

      --

      Quantum materiae materietur marmota monax si marmota monax materiam possit materiari?
    4. Re:Some corrections by BandwidthHog · · Score: 1

      My career (such as it is) began on a Mac SE with a 20mb internal hard drive in July of ’88. I don’t know when that machine was purchased, but I do know that it was a factory drive, not aftermarket.

      --

      Quantum materiae materietur marmota monax si marmota monax materiam possit materiari?
  45. The Apple II: What might have been? by Faust7 · · Score: 1

    And the parent poster isn't too far off base in one respect. Apple's market share did drop, not so much because of the move from DOS3.3/ProDOS to the Mac, but because of the way Apple treated their existing base of Apple ][ and //e customers. I mean, even when the Mac came out there was still a huge base of installed Apple //e business customers and Apple pretty much just threw them away, fully expecting them to migrate to the Macintosh. Migrate they did, but to the IBM PC.

    Never forget one thing: Apple was the incumbent, with all the advantages that confers. Atari and Commodore together couldn't market themselves out of a cardboard box and both eventually fell by the wayside. I look back at Apple Computer as a company that was at the right place at the right time with everything in its favor, only to squander opportunity after opportunity, relegating itself to second place. And such a distant second as to be almost out of the running, when they could have owned the market.


    I always find myself wondering what would have happened if Apple had taken all the energy and GUI focus that they had for the Macintosh, and instead applied them to the much more flexible, expandable Apple II line. Might the Apple II line have evolved into a modern-day industry standard, with as many clones and as much software as PCs have now?

    1. Re:The Apple II: What might have been? by ScrewMaster · · Score: 3, Insightful

      Well, it cost them the entire industrial sector, for one. At the time I was using Apple ]['s and //e's as data acquisition systems, real-time graphics displays, and other fun stuff like that. Then out came the Mac and my initial reaction was "Wow ... what a useless toy." Granted, it was cool and I had one for a while. However, without the ability to plug in an EPROM burner, high-speed A/D and D/A boards and other commonly-available Apple ][ peripherals the Mac was of no consequence to me. The PC, on the other hand, could be looked at as what the Apple ][ should have become (minus the stupid Intel CPU, of course. I would have just LOVED to have had a 68000-based Apple //e.) Slots, better monitor, lots better keyboard, etc. So, yes ... I think Apple might have ended up being a much bigger player if they'd played it a little differently. At least, it would have been a good idea not let Jobs' ego and limited view of the computing world push the Mac to the exclusion of the existing product lines.

      --
      The higher the technology, the sharper that two-edged sword.
    2. Re:The Apple II: What might have been? by laird · · Score: 1

      "I always find myself wondering what would have happened if Apple had taken all the energy and GUI focus that they had for the Macintosh, and instead applied them to the much more flexible, expandable Apple II line."

      Ask Steve Jobs. One of his sneakier moves (rumored -- no public documentation that I know of) to make his product (Macintosh) successful was to force the Apple IIgs to run at 1/2 the clock speed that its processor could have run at. This was important to him because it would have been impossible to sell a monochrome, unexpandable, 16-bit Macintosh for more than the color, expandable Apple IIgs. It makes me wonder how Apple would have done, much as I like the Mac, if they'd really made the Apple IIgs as good as it could have been.

  46. Re:Remember, the original Mac didn't sell well eit by Anonymous Coward · · Score: 0

    It's hard to understand why anybody would call a product that sold faster than it could be produced and that exceeded even the most optimistic expectations a "flop."

    In point of fact, the Mac and Mac Plus were stupendous successes for Apple, successes that really couldn't be duplicated until the iMac showed up in 1998.

  47. Not IBM? No sale. by Thu25245 · · Score: 1

    The IBM PC wasn't successful because of its price (the Apple II was cheaper and more open) or because of its technology. It was successful because the nameplate on the front had a big, prominent IBM logo.

    If the Lisa had been an IBM product, it would've been vastly more successful. Same with the Macintosh, Commodore 64, anything. Businesses bought IBM, because it was IBM and because IBM knew how to support corporate customers. Such was the power of the brand in those days, and there's nothing like it in the computer market today.

    Clones sprang up around the IBM because it was the hot thing. They reverse-engineered the PC BIOS because that was the only way to go. No other computer could've justified the R&D necessary to create a clone, but the IBM could.

  48. Hindsight is 20-20 by Thu25245 · · Score: 2, Insightful

    So Jobs didn't get it.

    Gates didn't get it.

    Sun didn't quite get it.

    But we, with the full benefit of hindsight...we get it. Just like those little-known geniuses, writing papers in the bowels of university research labs and Xerox PARC. We get it now. We are so friggin' smart. So much better than those short-sighted billionaires who pillaged and plundered the ideas of their betters twenty years ago.

    We get it. We are so brilliant. We totally rock.

    1. Re:Hindsight is 20-20 by DocScience4 · · Score: 1

      But we, with the full benefit of hindsight I knew Baldrson during the time frame he references (early 80s) and I can tell you, first-hand, he told me many of these same things then. Plus a lot of other pretty prescient (and just darn helpful) stuff.

  49. Opteron better than 80386 by Thu25245 · · Score: 1

    Why compare two processors from totally different time periods?!

  50. Bob and Lisa by c0d3r · · Score: 1

    Can you install MS Bob on top of Lisa?

    =)

  51. RE: Microsoft Bob by NotFamous · · Score: 1

    Would they publish one on how Microsoft Bob revolutionized the world of user agents and computer interaction?

    Actually the Mac version was much better, surely you remember Bob for Apples?

    --
    Some settling may occur during posting.
  52. Re:Is it that time again? by Anonymous Coward · · Score: 0

    Why isn't this modded troll?

  53. mod parent up by Billly+Gates · · Score: 2, Informative

    There is a huge 6 year gap between the two. I could say a powerpc G5 processor is alot better than an 8086. Well of course it is. But does that mean a fast Athlon64 is slower than a G5?

    By the time the 80386 came out, Motorrola had 60020's and perhaps 68030's.

    PS the 68020's and I think the 68000's could run Unix because of built in memory protection and other features. Could 8088's, 8086's, 80186's or 286's do that? No I do not Consider early SCO XENIX aka Openserver a real unix with built in memory protection and primptive multitasking until well after the 386.

  54. Re:Remember, the original Mac didn't sell well eit by Anonymous Coward · · Score: 0

    Most PCs had hard drives in 1984?!? I doubt it.

    I certainly didn't get a PC with a hard drive until my first 386 in 1990. I was perhaps a bit behind the times, but I doubt your average new PC had a HDD until at least 1986.

  55. My fault by mrs+dogbreath · · Score: 0

    I said it was poo poo to a large british bank
    Yeah so i was drunk!

  56. You are a Moron-Old buses by Anonymous Coward · · Score: 0

    Your history is a bit incomplete.* The EISA (1988) was the industries answer to the MCA (1987). Look at the card edge, and you'll notice it's basically the ISA (1985) bus with an additional row of pins. PCI came later (1994)

    The VL-Bus was popular about '93-'94.

    http://www.pcguide.com/index.htm

  57. The Mac Plus with INTERNAL hard drive by mah! · · Score: 1
    Well, I bought a Mac Plus at educational discount as soon as the prices went down (equivalent to about $500-600 at today's value I guess) because of SE's and II's introduction in 1987.
    That was almost 20 years ago, now that I think of it.

    True, the Plus did not have an internal hard drive... originally. It came with 1MB RAM and one internal 800k floppy. But... I installed an INTERNAL 20MB 5.25" ST-225N Seagate hard drive into it, by mounting it diagonally to the CRT, and soldering the SCSI connections directly to the motherboard. It was great!

    Performance-wise it was OK (my previous machine was an Atari ST), but the thing had a great GUI for its OS, and with Lightspeed Pascal graphics was easily accessible.

    When I think about those years, I stop even considering complaining about my PBG4 not being fast enough :-)

  58. Re:Article is hostile : mc68000 was 32 bit! not 16 by seebs · · Score: 1

    Actually, there were significant problems with the 68020, because many developers used the top byte of addresses for flags. But they were warned against it pretty much from day 1.

    (Emacs, BTW, was a major early offender, because the default assumption it made was that you could use part of every pointer for flags. I think it still does this, rather than defaulting to separate pointers and flag bits except on platforms where the assumption has been tested.)

    --
    My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
  59. Re:You are Mistaken by Anonymous Coward · · Score: 0
    So Apple has not been in a steady decline since '84? I did not mean to imply "why" only "when". The "why's" of these things are always more complicated. Some have suggested it's Steve's karma for shafting Woz - I know a lot of that went on. I put it down to ego over reason, in may forms, not just ego-Steve.
    I was there - I'm not reading this stuff from some fanboi's biography. IBM PC's of the time, and the clones were all as expensive or more so than Apple][ line - on par with the Macintosh line. We're talking before the 286 was released.
    I dislike Apple because they forced me onto PC's by not providing a viable alternative until 2001, approximately 16 years too late.

    Your need to call me a moron and a fucking idiot for expressing my opinion merely illustrates the depth of your ignorance.

  60. Re:Attention Apple Fags! by Anonymous Coward · · Score: 0

    10% market share? Awww, you're too kind!!

  61. Does Patrick Naughton Have No Idea Too? by Baldrson · · Score: 2, Interesting
    Patrick Naughton wrote:

    ...When I left Sun to go to NeXT, I thought
    Objective-C was the coolest thing since sliced bread, and I hated C++.
    So, naturally when I stayed to start the (eventually) Java project, Obj-C
    had a big influence. James Gosling, being much older than I was, he had
    lots of experience with SmallTalk and Simula68, which we also borrowed
    from liberally.


    The other influence, was that we had lots of friends working at NeXT at
    the time, whose faith in the black cube was flagging. Bruce Martin was
    working on the NeXTStep 486 port, Peter King, Mike Demoney, and John
    Seamons were working on the mysterious (and never shipped) NRW (NeXT RISC
    Workstation, 88110???). They all joined us in late '92 - early '93 after
    we had written the first version of Oak. I'm pretty sure that Java's
    'interface' is a direct rip-off of Obj-C's 'protocol' which was largely
    designed by these ex-NeXT'ers... Many of those strange primitive wrapper
    classes, like Integer and Number came from Lee Boynton, one of the early
    NeXT Obj-C class library guys who hated 'int' and 'float' types.


    Another interesting side-note, (so as not to break any rules on my first
    [and last]-ever posting to comp.sys.newton), John Seamons, (who happened
    to be Andy Bechtolsheim's roommate at Stanford and largely reponsible for
    the first ever port of Unix to the SUN-0) once did a port of Oak (Java)
    to the Newton. We were in the midst of trying to do a deal with 3DO to
    run as their OS/API, and we didn't have any 3DO dev systems on hand, so
    John took apart an Apple Newton 100 and wired it up to a bunch of logic
    analyzers, reverse engineered the interfaces and actually got some of the
    original Star7 demo to run on this machine. After the 3DO deal tubed, I
    think most of the code was lost to history... last I heard, John was out
    in Aspen working for wnj, so you never know.


    Sigh... we sure knew how to have fun in those days...


    -Patrick


    -------------
    Patrick Naughton
    President and CTO
    Starwave Corporation
    http://www.starwave.com/people/naughton

  62. Now this.... by mblase · · Score: 1

    ...is the kind of discussion I expect in a Slashdot article. ;-)

  63. My First Into to GUI by grantdh · · Score: 1

    When I was a kid at high school I was helping a guy who'd picked up a Lisa for his office. It wound up at my place while I learned how to set up a DB for him in Omnis. There I was with the biggest "home/office" computer I'd ever seen on a table in our lounge, mucking about with a mouse (woooo - never seen something like that before) and it even had an external HDD (which sat on top, had to be turned on before the computer so it could spool up to speed and sounded like a DC-8 engine-start as it did :)

    Had a few of the local geek-kids coming over to inspect it - amazing times :)

    --

    I left my body to science, but I'm afraid they've turned it down...
  64. confusion reigns by toby · · Score: 1
    ... Somehow a Forth interpreter made it into the first Mac, as did Postscript, but Smalltalk just didn't.

    As far as I know, Apple never shipped a Forth interpreter with Mac system software (although Power Macs around 10 years later did include one as part of Open Firmware, used during booting only).

    A couple of years after Mac's introduction, Apple certainly did ship a complete Smalltalk environment for 68K Macs, as did several third party vendors.

    PostScript was never part of the MacOS imaging model (and with OS X, still isn't) and in any case did not arrive on the scene for a year after 'the first Mac'. Once the LaserWriter shipped, the printer driver gained a primitive PS generator for the Mac's QuickDraw model.

    (Much later, some imagesetter vendors and preflighting/soft proofing applications, and Ghostscript, of course, included PostScript implementations for specialised purposes. Even Adobe's graphic arts applications did not embed anything approaching a full PostScript implementation until quite recently.)

    --
    you had me at #!
  65. Re:Article is hostile : mc68000 was 32 bit! not 16 by runderwo · · Score: 1

    But the 8086 would be 16-bit using that criterion. Also, XMS was not available on a 8088, nor was EMS emulation in the typical sense (using paging ala EMM386) - although a memory board implementing EMS would work.