Slashdot Mirror


Bill Gates Talk From 1989 Surfaces

70sstar writes "A 1-1/2 hour recording of Bill Gates addressing a crowd of university students in 1989 was recently found and digitized, and has been circulating in some IRC channels for the past few weeks. The speech has found a permanent home on the web page of the University of Waterloo CS Club, where the talk is reported to have taken place. Gates covers the past, present, and future of computing as of 1989. While the former two might be of interest to tech historians, the real fascination is Gates's prediction of computing yet to come. Like the now-legendary '640k' remark, some of his comments are almost laughably off-target ('OS/2 is the way of the future!'). And yet, by and large, he had accurately, chillingly, prophesied an entire decade or two of software and hardware development. All in all, a fascinating talk from one of the most powerful speakers in CS and IT."

63 of 317 comments (clear)

  1. OS/2... by TheSHAD0W · · Score: 3, Interesting

    You do know that the NT4 core is extremely similar to OS/2, and the only reason they diverged is because of a fight between IBM and MS?

    1. Re:OS/2... by TheNetAvenger · · Score: 4, Informative

      You do know that the NT4 core is extremely similar to OS/2

      Actually as an OS Engineer that has spent time working with and tearing both apart, they are very much night and day.

      You would have more success in selling OS/2 is the same as BSD.

      Here are a couple of things to get you started, and I could point out a few inaccuracies in each of these, but for the most part they will send you down the right path:

      http://en.wikipedia.org/wiki/OS/2
      http://en.wikipedia.org/wiki/Architecture_of_Windo ws_NT

      Now where you are partially correct. NT started out in the OS/2 3.0 development stages, but by the time MS and IBM split, NT was a start from scratch OS as Dave Cutler thought the OS/2 codebase was horrible.

      MS even looked at using *nix concepts in the early days of NT, since it was being written from the ground up, and why MS held on to Xenix at the time in case that is the direction the NT team wanted to go with NT or base it on

      However the NT team felt the *nix architecture concepts were too limited and instead decided to take the best OS theories at the time and see if they could truly make a new OS technology.

      I get so tired of kids today confusing simple things and I see this crap on here all the time. NT is not VMS, NT was not OS/2, NT and Win95 are not related other than the Win32 subsystem, WinXP does not contain Win9x code, etc etc...

      No wonder people think Windows is more of a joke than it already is, if I saw it as a hybrid and hodgepodge of Win9x and OS/2 and NT I would think it was an insane code base too; however, it is not.

      It is easy to poke fun at Windows, but when you find real OS engineers, the NT architecture/kernel isn't quite so funny and gets quite a bit of respect even if they hate the Win32 subsystem.

    2. Re:OS/2... by Richard+Steiner · · Score: 2, Interesting

      Remember also that OS/2 ran Windows 3.1 software almost flawlessly, including software that used the 32-bit extensions found in WIN32S.DLL, and that Microsoft could only stop IBM from continuing to offer that high level of competability by changing the virtual machine size of WIN32S.DLL starting with version 1.30 and making that a default setting.

      That's why Adobe Photoshop for Windows 3.04 runs just fine under OS/2 Warp 4's WinOS2 subsystem but Adobe Photoshop 3.05 fails, for example. The only thing which changed between those two releases (besides a few fixes) was the move from WIN32S.DLL 1.25a to WIN32S.DLL 1.30.

      --
      Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
      The Theorem Theorem: If If, Then Then.
    3. Re:OS/2... by laffer1 · · Score: 2, Interesting

      Apparently they are not.

      http://support.microsoft.com/kb/308259

    4. Re:OS/2... by dryeo · · Score: 3, Informative

      I think you mean OS/2 ran DOS (including win3.x) in VDMs. But you are right, in win32s ver 30 MS moved some DLLs above the 2GB mark just to break OS/2 which at the time had a 512 MB per process limitation and still does for most apps. Wasn't until ver 4.5 that the client could access 3 GBs and some APIs are still tied to the 512 MB barrier.
      And yes, don't know about MAC OSX but the newer Windows and Linuxes still seem broken compared to what the WPS could do on a 486 (with lots of memory, hopefully at least 32 MB)

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    5. Re:OS/2... by Ilgaz · · Score: 2, Interesting

      In that book I referenced on my comment (The Microsoft File), a very advanced debugger guy finds a huge mistake on Win 3.x code which will totally break it if it runs under DR-DOS. Guy gets totally confused since a coder working for a company like Microsoft can't make that mistake without purpose.

      If I could find my copy , I would give names of course. Apologies.

    6. Re:OS/2... by LarsG · · Score: 2, Interesting
      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    7. Re:OS/2... by TheNetAvenger · · Score: 2, Informative

      Also the DOSCALL1.DLL in NT was quite similar to the DOSCALL1.DLL in OS/2 ver 1.3 and I'd imagine that it is similar when comparing the WIN32 DLLs between WIN9x and NT.
      Naturally this does cause some confusion.


      Ya, it does cause confusion, but this is like 15 years ago, and yet people still don't seem to understand, yet people from the timeframe that all this was happening were 'quite' aware.

      As for the DLLs these are subsystem DLLs, not NT DLLs. I understand that in the SlashDot world, NT is a bit weird and the concepts of subsystems seem to escape a lot of knowledgeable people.

      But people have to understand that Win32 is basically an OS that sits in a subsystem on NT, just as OS/2 1.3 was and the UNIX BSD subsystem MS also ships for Windows.

      To say that these DLLS in these subsystems are a part of NT would be like looking at the BSD libraries in the BSD Subsystem that runs on NT and say that NT and BSD are also the same OS. Which is very far from the truth and even sounds crazy for anyone that understands BSD.

      I try to suggest to people all the time in my professional realm to take a few minutes and just read the Wiki pages on NT, as they do have some inaccuracies, but for the most part are pretty good at defining what NT is and how the client/server nature of the kernel design inherently allows for the subsystem architecture it supports.

      NT cannot be defined by Win32, nor any other subsystem that runs on NT, as ANY of them could be replaced. So it doesn't matter what DLLs or applications are running in the subsystems, they have nothing to do with the NT architecture.

    8. Re:OS/2... by TheNetAvenger · · Score: 2, Interesting

      From my perspective as developer of both real-time data acquisition systems and graphical user interfaces, I would say that it is difficult to make Windows do anything "useful". At least, it's often way more difficult than it ought to be. And no, I'm not a god, but there are times when I sit at my workstation and wish that I was.


      Well, I would buy your argument, but one of the main reasons Windows was as successful as it was in the development world in the early 1990s was based on the fact it was the most centralized and easiest OS to develop for at the time.

      This includes the largest and most encompassing abstracted driver support for developers, making the concepts of Video, Sound, and Printing an agnostic concept for developers.

      Windows is like the melting pot of development, in that anyone that can drag a textbox on a form can write an application and someone with a beginners knowledge can easily mimic what was seen as complex applications of the late 80s and early 90s rather easily.

      I'm not saying that the VB mentality of Windows development is always a good thing, but it allows simple IT people to knock out functional software that meets their particular needs.

      I can remember working with EDS several years back and they designed a full set of assembly-line diagnostic tools for GM/Delco using VB. This was a fairly complex and large scale project that they were able to bring to testing in a matter of weeks.

      And although it was not a realtime system in the true sense, it did provide realtime features that met their plant's needs quite well. So next time you turn up your Bose sound system in a Vette, you might want to give a shout out to Windows and VB.

      This would be far easier to debate if the standard development tools in other OSes all looked like Kylix and were more agnostic about the variant they were running on.

  2. Maybe he was taking the party line by Salvance · · Score: 4, Interesting

    To the computer enthusiasts of the time, it would have been even more laughable had Bill Gates said "in the next two decades, Microsoft software will completely destroy OS/2, will render Apple a shell of its former self by stealing all its innovations, and will demand 1 GB of RAM." So even if he had his world domination plans set in 1989, he couldn't exactly let the world know without being laughed at.

    --
    Crack - Free with every butt and set of boobs
  3. Shh...poster was being smug! by HarryCaul · · Score: 5, Funny


    Don't interfere with Bill-Bashing!

    1. Re:Shh...poster was being smug! by timeOday · · Score: 4, Insightful

      It is funny to hear it straight from Gates though. He owes almost his entire fortune to IBM's failure to deliver on OS/2, and (to be fair) Microsoft's successful delivery of DOS+Windows (crap that it was).

    2. Re:Shh...poster was being smug! by ePhil_One · · Score: 2, Interesting

      Actually, he owes it to Gary Kildall refusing to talk to IBM when they asked him to port his dominant OS to their new computer. Bill got into the OS market to save his contract with IBM for Basic on the new PC.

      --
      You are in a maze of twisted little posts, all alike.
    3. Re:Shh...poster was being smug! by westlake · · Score: 5, Interesting
      He owes almost his entire fortune to IBM's failure to deliver on OS/2, and (to be fair) Microsoft's successful delivery of DOS+Windows (crap that it was).

      Gates began programming at age thirteen, at age fourteen he is clearing $20,000 in is first partnership with Allen. Microsoft is founded in 1975. Microsoft in in Japan in 1978. In Europe in 1979. In 1980 Microsoft is young, hungry, and moving a hell of lot faster than Kildall.

    4. Re:Shh...poster was being smug! by Traa · · Score: 2, Interesting

      Look, I love to hate Windows as much as anyone else (here on slashdot), but I happened to have worked on OS/2 drivers in the mid 90's and just thinking back at those make me cringe. OS/2 was a pile of crap when it died. Anyone thinking that IBM was on the verge of launching a flawless operating system is smoking something significantly stronger then I ever have (and I'm from The Netherlands)

    5. Re:Shh...poster was being smug! by timeOday · · Score: 3, Insightful

      I agree, DOS (like Windows) could so easily have gone to a competitor instead. I guess it just shows how pivotal certain moments can be. IBM in particular made blunder after blunder, refusing the take the PC seriously. I guess their mainframes were doing just fine and they didn't want to open their eyes to the implications of Moore's Law - that $500 PCs would ultimately take most of the market for computing hardware. Just like all the others - Sun, Silicon Graphics, Cray, DEC...

    6. Re:Shh...poster was being smug! by Richard+Steiner · · Score: 2, Informative

      The only reason OS/2 dies was because IBM was greedy and charged too much for it at the beginning of it's life, hence the beginning became the end.

      Wasn't it Microsoft that set the pricing of the SDK for OS/2 1.x, and wasn't OS/2 1.x mainly sold as a Microsoft product? Who set the high prices for OS/2 again?

      Remember that IBM, once it got hold of OS/2 and was able to release the 32-bit version as a product independently of Microsoft, was willing to sell OS/2 to Windows users for US$49 and to DOS users for US$99, thus making OS/2 an extremely affordable product at one of the key times in its evolution -- the time when it alone was a Windows-compatible 32-bit operating system that was completely independent from DOS.

      Windows NT 3.1 (Microsoft's first 32-bit offering) wasn't released until some time after OS/2 2.0 (July 1993, over a year later than OS/2 2.0 ).

      --
      Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
      The Theorem Theorem: If If, Then Then.
    7. Re:Shh...poster was being smug! by hey! · · Score: 3, Informative

      I don't think you have the story quite right.

      IBM was a victim of its unintended success. The first generation IBM PCs were crippled compared to what they could have been, in almost every way. They could have had a much better processor. They could even have run a real operating system. Instead it was low rent all the way, outsourcing as much as they could, because they were making a cheapo product they expected to sell only moderately well. They built a computer that was inferior to the Apple II which had been available for several years. Radio Shack had a 68000 based computer running Unix that was introduced around the same time. These could have been a serious threat, but IBM produced a toy computer, put it in a business like case, and slapped the IBM logo on it.

      If you were working in those days (1981-1982), things started out as planned. IBM PCs were appearing on desks as a status symbol. There wasn't much useful you could do on them. Then in 1983 came Lotus 1-2-3, and suddenly all those PCs became very useful. In the same year, came the Compaq portable, the first 100% "IBM Compatible".

      The disruption of IBM's business came not from their misunderstanding the rate of technological change. They were attempting to slow the impact of change on their existing product lines by introducing a low end product of their own that was positioned low enough that it wouldn't hurt their existing product lines.

      This would have been a good strategy if they hadn't failed to anticipate the success of the product. They didn't even bother to get exclsuive rights to DOS. By making a proprietary PC, they actually accelerated the penetration of microcomputer vendors into their customer base.

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

    If I was said sysadmin I would be changing my numbers right about... now.

  5. Transcript? by rgo · · Score: 4, Interesting

    Is there a transcript anywhere? Or at least a summary? I don't have the time to listen to an hour and a half mp3.

    1. Re:Transcript? by flappinbooger · · Score: 2, Funny

      So, how long have you worked at MS?

      --
      Flappinbooger isn't my real name
    2. Re:Transcript? by Strudelkugel · · Score: 5, Informative

      I don't have the time to listen to an hour and a half mp3

      Crude index:

      • 28:00 Developer teams
      • 36:00 Mouse
      • 50:00 Unix
      • 52:40 Mac
      • 56:00 PARC people
      • 57:00 Mac GUI/Microsoft developers
      • 63:00 Third standard
      • 66:30 Networks
      • 71:50 Lotus/Excel competition
      • 75:00 "World Net"
      • 76:50 Multimedia
      • 79:40 Utility of the CD (Thanks music industry!)
      • 87:00 Learn from competitors
      • 87:50 Hypertext

      Actually Gates was quite insightful. He clearly understood what was important for the evolution of the personal computer, but didn't quite manage to have Microsoft dominate all of it, fortunately. When he discussed Unix in one section, and importance of networks in another, he never mentioned anything about security, which is an important element of Unix design. Later he mentions the "World Net", but of course did not anticipate HTTP and browsers. This makes his comments about hypertext all the more interesting; he correctly states massive amounts of typeless links would overwhelm the user. The significance of search, among other things, eluded his thinking at the time. Gates' discussion of a third standard is interesting to ponder in view of OSS, which could be considered the answer to his question about what other approach might gain traction. Overall his prognostications were quite correct. If he is as astute today as he was then with regard to humanitarian issues, his health initiatives should do a lot of good.

      --
      Imagine how much harder physics would be if electrons had feelings! -Feynman, maybe
  6. But by Centurix · · Score: 2, Interesting

    I really do only need 640k. As long as I can play Scramble on my Vic 20 I'll be happy for life.

    --
    Task Mangler
  7. 640k remark by badasscat · · Score: 4, Informative

    Like the now-legendary '640k' remark

    A better description would have been the "mythical '640k' remark", because he never said it.

    Nobody can ever cite a source for this alleged quote, and in the absence of such a source, you have to take his word for it. It's impossible to prove a negative; that's how urban legends start in the first place.

    (If he did say it, don't you think someone would have figured out the where and when?)

    1. Re:640k remark by Andareed · · Score: 5, Informative

      The exact 640k quote from the talk: "So that's a 1 MB address space. And in that original design I took the upper 340k and decided that a certain amount should be for video memory, a certain amount for the ROM and I/O, and that left 640k for general purpose memory. And that leads to today's situation where people talk about the 640k memory barrier; the limit of how much memory you can put to these machines. I have to say that in 1981, making those decisions, I felt like I was providing enough freedom for 10 years. . That is, a move from 64k to 640k felt like something that would last a great deal of time. Well, it didn't - it took about only 6 years before people started to see that as a real problem."

    2. Re:640k remark by edwardpickman · · Score: 3, Informative

      Probably adding fuel to the fire was the fact that the memory limitations held for so long. I've always been into graphics and animation and the early memory issues were a major hassle. Even today shortsightedness about memory has been a major hassle for Windows. Win 2000 had a 2 gig cap and XP had a 4 gig. With the average person being able to aford 4 gig of ram and graphics people needing all the ram they can get it's bizzare with cheap ram to have such limitations. Vista is an improvement but there is a major system ram charge to get it and there still a cap that will be soon reached. He may not say Win 2000 users will never need more than 2 gig of ram but it's the way the company approaches it. Back when Amiga was around it always ran circles around Windows machines for memory. I always loved the fact that a lot of components came with extra ram slots. The Amiga 3000 had a ram limit in range of modern machines and that was 17 years ago. He may not have declared 640k was enough but he's hardly a visionary where memory is concerned.

    3. Re:640k remark by Psychotria · · Score: 3, Informative

      I'm not sure if it was so much a software (OS) limit rather than a hardware one. I.e. 2^32 is where the 4GB address space (limit) came from, not because MS decided to be mean (for once). Sure, there are ways to get around the hardware "limitation" in software but there was probably not much incentive at the time to do so.

    4. Re:640k remark by Ford+Prefect · · Score: 2, Insightful

      "I have to say that in 1981, making those decisions, I felt like I was providing enough freedom for 10 years. . That is, a move from 64k to 640k felt like something that would last a great deal of time. Well, it didn't - it took about only 6 years before people started to see that as a real problem."
      ... Then you have the Motorola 68000, designed in the late 1970s and used in home computers in the mid 1980s - capable of addressing a whopping 16MB of memory, and using a flat 32-bit address space in case of future expansion.

      So obviously 640kB wasn't enough for everyone back then... ;-)

      --
      Tedious Bloggy Stuff - hooray?
    5. Re:640k remark by westlake · · Score: 2, Insightful
      Then you have the Motorola 68000, designed in the late 1970s and used in home computers in the mid 1980s - capable of addressing a whopping 16MB of memory

      and the street price for 16 MB of RAM in 1980 would have been...what, exactly?

    6. Re:640k remark by akh · · Score: 3, Informative

      According to this page, 16MB of RAM in 1981 would run you about $150,000.

      --
      Accept Eris as your Fnord and personally sate her
    7. Re:640k remark by swillden · · Score: 2, Informative

      Win 2000 had a 2 gig cap and XP had a 4 gig.

      Incorrect, XP can only manage 3 GiB of RAM. You can install 4 GiB, but you'll have one unused. Supposedly Vista supports 4 GiB. 32-bit Linux also appears to be limited to a little less that 4 GiB, unless you build with the HIGHMEM64 option, in which case it will support up to 64 GiB.[*]

      Contrast this with the foresight shown for IBM's System/38, which featured 128-bit pointers at its introduction in 1978. With such a huge address space, the entire system storage was mapped into virtual memory, effectively turning the RAM into nothing more than a cache to accelerate operations. Of course, it was a bit too ambitious for the hardware of its day, it wasn't until the introduction of the AS/400 in 1988 that such a system could really run well.

      Today, a 64-bit address space seems plenty large for whatever we might want to do with it, including virtual addressing for all system storage as well as RAM. Given how inconceivably large a number 2^64 is (16,777,216 TiB anyone?), it seems ludicrous that more could ever be required. But I'm sure Gates would have thought the same of 2^32 in 1981. 128-bit pointers still make me shake my head in disbelief, but who knows, maybe I'm the one lacking foresight now?

      Those System/38 and AS/400 designers didn't take any chances, and their software is unfazed by the growth in RAM and disk sizes.

      [*] Maybe someone who knows could amplify? I thought that Linux with HIGHMEM4G could use up to 4 GiB RAM, but I have a system with 4 GiB, and a kernel compiled with HIGHMEM4G, and /proc/meminfo shows MemTotal 3,238,840 KiB. I'm using the onboard nVidia 6150 GPU, and have configured it to use 128 KiB of system RAM for video, but that should still leave me with 4,063,232 KiB, so I'm "missing" 824,392 KiB, or about 805 MiB.

      I'm rebuilding with HIGHMEM64G right now, and eventually I'll get around to installing a 64-bit Linux kernel (this is an Athlon 64 X2 machine), but I'm puzzled as to why I can't use my 4GB with 32-bit Linux.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  8. One thing is obvious from the photograph by Aokubidaikon · · Score: 3, Funny

    Most geeks' dress sense hasn't changed much since 1989 ;)

    1. Re:One thing is obvious from the photograph by jd · · Score: 4, Funny

      That's because geeks have a genetically-implanted dress sense from hyper-intelligent beings from another world. Those who lack the genes necessary give in to their ancestral ape-man desires for suits and ties.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    2. Re:One thing is obvious from the photograph by thrawn_aj · · Score: 3, Funny

      Most geeks' dress sense hasn't changed much since 1989 ;) Fancy that :P. How foolish of us geeks not to buy into the "hip" mantra. But hey, come up with a less idiotic accessory than a tie (which, seriously was probably invented by a closet S&M freak) and we'll talk business =D. Another fancy I have is that the suit was invented by the same sadist who invented the corset and high heels for women. Gimme a tshirt and pair of jeans anytime. The Linux fanbois can have the penguin suits =D.

      ______

      "What's flamebait daddy?"

  9. Predict the future by imunfair · · Score: 4, Insightful

    What kind of business are you in?

    We predict the future. The best way to predict the future... is to invent it.

    -X-Files

    1. Re:Predict the future by The+Zon · · Score: 3, Funny

      The best way to predict the future... is to invent it.
      I have prior art on the future. Also, a time machine.
      --
      Some attitudes replaced or by cgi optimizes
  10. He thought OS/2 would be the perfect platform... by Anonymous Coward · · Score: 4, Funny

    ...for Duke Nukem Forever.

  11. 30 minutes by Anonymous Coward · · Score: 4, Funny

    1-1/2 hour = 30 minutes

    Oh wait...

  12. Well... by Xenographic · · Score: 4, Interesting

    You have to admit that it's easier to predict the future when you're the one making it... :]

    That said, the places where he was wrong are more interesting to me. I wonder what Microsoft's business plan was had IBM taken over with OS/2 instead of them?

    1. Re:Well... by Bastian · · Score: 3, Insightful

      That said, the places where he was wrong are more interesting to me. I wonder what Microsoft's business plan was had IBM taken over with OS/2 instead of them?

      It was to rake in (slightly less) dough selling OS/2.

      OS/2 was originally a joint Microsoft/IBM effort. What became Windows NT was originally going to be the next version of OS/2, but tensions between MS and IBM increased until Microsoft decided to take its ball and go home.

      So really, Bill Gates was 100% correct in saying that OS/2 is the wave of the future. It's just that in 1989 he didn't realize that it was going to be renamed "Windows NT" 3 or 4 years later. Had Microsoft instead decided to continue working with IBM, they would probably still have ended up being stinking rich, just a bit less so.

    2. Re:Well... by Alien+Being · · Score: 4, Informative

      OS/2 and NT are different animals.

      OS/2 was originally a joint Microsoft/IBM venture and was to replace Windows, but there were squabbles over the API definition which caused Microsoft to rethink the whole plan. By that time, the Windows(3.0) API had become a defacto standard and the world's most valuable computer technology.

      MS realized that abandoning Windows (and control of the API) was a huge mistake, so they didn't. They went ahead with OS/2, but kept Windows as their primary platform. They knew that they still needed a "real" OS to replace Windows' DOS underpinnings, so they started the NT project.

      Windows remained as the market standard and MS remained as the gatekeeper to the API. OS/2 customers who wanted to run/develop apps for the "standard" system would also need a Windows license. And perhaps even more important than their ability to sell licenses, is the fact that by controlling the API, they get a huge head start over the competition when it comes to designing developer tools and applications around that API.

    3. Re:Well... by xigxag · · Score: 2, Funny

      "I'm OS/2, and I used to be the next operating system of your PC."

      --
      There are two kinds of people: 1) those who start arrays with one and 1) those who start them with zero.
  13. I remember this talk. by Ninja+Programmer · · Score: 2, Informative

    I was a fledgling member of the CSC at Waterloo, and I recognize the members in the photos they showed. I also remember attending this talk with a front row seat. I was sort of unimpressed because he didn't discuss anything that was new or that I didn't already know about.

  14. Predictions by yuriyg · · Score: 4, Interesting

    And yet, by and large, he had accurately, chillingly, prophesied an entire decade or two of software and hardware development. Shouldn't be all that surprising, since he more or less controlled the direction of desktop software development in the 90's. I would assume he just stated his vision of the future of software, and that vision was implemented.
  15. Re:Long Road Home by Supercrunch · · Score: 2, Informative

    It was called "The Road Ahead", originally published in 1995. My recollection was that he got some things right, but he speculated that a new information superhighway would come along to replace the Internet. He also predicted that many/most of us would be interacting with their computers via handwriting and voice recognition.

  16. How did you get modded +5 by Anonymous Coward · · Score: 5, Informative

    It says a lot about /. these days. During the days of Olsen, he started a re-write of VMS. It had such luminaries as Cutler and Bell on the team. When the company was bleeding, Olsen killed off this project and others. When Gates got wind of this, he approached Cutler (and others such as Grey and Bell), and convinced him to join him. One of the bigger issues was that he promised the core to the VMS folks. He would control the API and above. They would control the core.
    ANd if that was not enough, back in 94, I even saw the code for NT (I worked at HP and a neighboring group were asked to port it to the pa-risc. ). I can tell you firsthand that it had NOTHING to do with OS2. If you looked at it, you knew it was dec derivitive. Even the comments said it all.
     
    So how did you get modded up?

    1. Re:How did you get modded +5 by Richard+Steiner · · Score: 3, Informative

      APIs are surface features which are (usually) made visible for applications to use, and they give very little indication of the nature or structure of the actual kernel code running underneath.

      OS/2 supports the POSIX API via EMXRT.DLL, for example, and yet OS/2's kernel has very little in common with, say, Linux or Solaris (which both also support POSIX programs).

      The 32-bit OS/2 kernel written by IBM for OS/2 2.0 and later and the Windows NT 4 kernel are quite different. Both Microsoft and IBM completely re-implemented their respective OS's kernels after the 16-bit OS/2 days, and the resulting software has very little relationship to the old 16-bit kernels except for support for the older 16-bit APIs. But as I said, that is simply a surface similarity.

      --
      Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
      The Theorem Theorem: If If, Then Then.
  17. Gates-Quotes from a 1990 interview by Burlador · · Score: 4, Interesting

    From Chip Magazin 1/1990 (my re-translation from German):

    "I think about Handwriting recognition. In two or three years, we may have computers without keyboards. In five or six years this will change, and voice recognition will reduce the importance of graphics."

    "In five or six years, DOS [sales] will be overtaken by OS/2."

    The he said he is personally using "a Mac II, a Compaq and a IBM" computer, as well as a "NEC-Ultralite".

  18. Prophesy? I don't think so by Anonymous Coward · · Score: 3, Insightful

    " And yet, by and large, he had accurately, chillingly, prophesied an entire decade or two of software and hardware development."

    Yeah? Gee, if he was once such a savant, what happened between then and his 1995 book "The Road Ahead" where he totally fails to "predict" the Internet and World Wide Web when it had already happened?

    Sorry, but reciting some corrollary to Moore's Law does not count as accurate prophesy, 'chilling' or otherwise. It's just conventional wisdom

  19. No MS conspiracy required for OS/2 failure by ClosedSource · · Score: 3, Interesting

    What legendary rock-n-roll song was used at the gala release celebration for OS/2? Oh, that's right, there was no celebration. OS/2's number one reason for failing was that IBM didn't make much of an effort to make it a success.

  20. Re:eComStation still has superior technology by Richard+Steiner · · Score: 4, Interesting

    The thing most people don't realize is that even the 1996 flavor of OS/2 Warp 4 is capable of running modern software like Firefox and OpenOffice, and it does so rather well on fairly limited hardware.

    Windows has a hard time doing that these days, and Linux is travelling in that direction (at least in terms of the mainstream distros, which seem to have abandoned legacy hardware support for eye candy).

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  21. Re:Prophesy? I don't think so by laffer1 · · Score: 2, Informative

    Funny you should bring up the Road Ahead. Its interesting to compare the differences between the first and second editions of that book. The Internet "exists" in the second version.

  22. Everyone's predictions are wrong. by suv4x4 · · Score: 3, Funny

    He's the richest dude in the world and his OS is on almost every PC in the world, but let's laugh that he predicted something wrong in 1989! Hahaha, that totally evens things out.

    Gee, I feel better for me now.

  23. Ahem.. by FMota91 · · Score: 4, Funny
    You ARE posting on slashdot. Let me correct your statement...

    Everyone cares about these fabulous corrections and technicalities. Keep it coming, it's really bitchin'.
    --
    09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C1 bottles of beer on the wall. Take one down, pass it round... Oh, umm...
  24. Enough with the conspiracy theories by steveha · · Score: 4, Informative

    I'm top-posting this instead of replying to individual posts because there are just so many posts with one conspiracy theory or another. Microsoft tricked IBM into taking OS/2, Microsoft made Office 95 break OS/2, etc. etc.

    I worked at Microsoft from 1990 to 1996, and during part of that time I worked on Microsoft Word. And I'm here to tell you: Microsoft really believed in OS/2, back in the day. They really thought it would be the future.

    In 1990, I got an OS/2 machine on my desk, as did the other folks around me, because we all knew OS/2 was the future. The MS library had OS/2 machines for looking up books (and as far as I remember, the MS library had only OS/2 machines). And all the major MS apps were shipped for OS/2: Word, Excel, etc. (But they were also shipped for Windows. MS covered all the bets.)

    Now, I was only a lowly developer, not a strategy architect, and I never ate lunch with Bill Gates, so it's possible there was some amazing subterfuge going on without me knowing. But I don't believe it.

    Here is my summary of what happened, based on what I saw then, and on various articles I read in PC Week, Infoworld, etc.

    Microsoft started developing Windows back in the 80's. The early Windows was a laughingstock in the industry: it was a primitive toy. Apple seriously jump-started their GUI efforts by building a closed platform and tailoring their GUI specifically for that platform; Microsoft was hobbled by the suckiness of the 8088 and awful graphics adapters like the CGA card. MS actually tried to get Windows to run on that sort of pathetic hardware. Windows 1.0 did run but no one wanted it.

    MS doesn't give up easily. They kept plugging away at Windows, and it started to suck less, as the machines got more powerful. Also, IBM and Microsoft decided to cooperate on a new OS: OS/2.

    Microsoft wanted to make OS/2 as compatible as possible with Windows, to make it easy to port applications. IBM wanted to make OS/2 "better" than Windows. (My memory is dim here, I don't remember specifically why it was better to be incompatible with Windows. Compatible with some graphics API that IBM already had?) So now, the plan was to sell Windows only until OS/2 conquered the world. But the Windows guys kept plugging away on Windows, even as the OS/2 guys did their thing.

    Around the time I was hired, Microsoft and IBM were telling customers that basically if you have lame hardware, go ahead and run Windows on it, but if you have good hardware, you want OS/2 because that is the future. (IIRC the decision point was: if you have less than two megabytes of RAM, run Windows.)

    Then, in 1990, Microsoft shipped Windows 3.0... and everyone, including Microsoft, was stunned by how well it sold. It flew off the shelves. Egghead (at the time, a successful brick-and-mortar chain of computer stores) sent trucks with ice cream over to Microsoft; along with everyone else, I had a free ice cream bar to celebrate the success of Windows 3.0.

    The key feature was actually that it ran DOS apps very well. You could have multiple DOS shells open at the same time, and it would multitask them well (pre-emptive multitasking, even though Windows itself used round-robin multitasking for Windows apps at the time!). You could even have a DOS app crash, and your other DOS apps would keep running just fine. Compare with the "compatibility box" in OS/2, which was usually called the "Chernobyl Box" by geeks because a misbehaving DOS app could take down your whole machine. The Chernobyl Box could only run a single DOS app at a time.

    Why? Why was Windows 3.0 better than OS/2? Because at the time OS/2 was written only to support the 286, and even if you ran it on a 386 it would just run in 286 mode. Windows 3.0 would only do the cool DOS app multitasking if you ran it on a 386. My understanding is that IBM promised, early on, that OS/2 would run great on a 286; and IBM felt it was seriously important to keep that promise. With hindsight, I

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
    1. Re:Enough with the conspiracy theories by mh101 · · Score: 4, Funny

      Steve Ballmer made a great speech a company meeting. He said that Microsoft had been sending a mixed message to customers: if you have this kind of hardware buy Windows, if you have that kind of hardware buy OS/2. He said that from now on, there would be a new message: "Windows! Windows! Windows!!!" He shouted himself hoarse saying it.
      I guess that was practice for his "Developers developers developers developers" speech.

      --
      Duct tape is like the Force. It has a light side, a dark side, and it holds the universe together.
  25. That's the kind of lack of foresight by DrYak · · Score: 3, Insightful

    Then you have the Motorola 68000, designed in the late 1970s and used in home computers in the mid 1980s - capable of addressing a whopping 16MB of memory

    and the street price for 16 MB of RAM in 1980 would have been...what, exactly?


    It's this kind of lack of foresight that made the whole x86 architectue crappy.
    The question is not only what is realistic to do now and what would be not be possible to buy/build.

    The question is, if this architecture hangs around for the next couple of decade what will you be happy to have taken account for ? What could be useful for future generations of machines ?

    The 68k has been designed on purpose to have a clean architecture, that could easily evolve in future machine without needing hacks. (32 bits internal, even if first versions had 16bit bus. Flat memory addressing, etc.)

    The x86 has been a long series of very short-sighted choice (because nobody tougth it could last) - like the "640k ought to be enough for everyone" (it was back then, it wasn't any more a couple of years later) or the ackward instruction set - and subsequent hacks to circumvent the limitations (the whole segmentation logic is a pain in the ass). Not to say about all legacy modes that current chips still drag around (your Core 2 is still binary compatible with 8088 code and assembly compatible with 8080 code). Intel has tried to restart something completly new and supposedly better with the Itanium, but it failed, mainly because of all this legacy. AMD was somewhat more successful with AMD64 (because it both has a nice new clean x86-64 extension and support for all the ackwrd legacy).

    It's only sad that the x86 was chosen for the IBM PC, a computer whose architecture was subsequently opened and copied by numerous clones that IBM chose to tolerate, which made this architecture popular and made it evolve very quickly.
    Whereas the 68k regularly ended up in very nice machines (Amiga, Macintosh, etc.) but whose parent company never accepted to open. And thus remained less popular (because of higher price and lower development by 3rd parties).

    At least the 68k had much more success in video games (consoles and arcades. MegaDrive and NeoGeo if i have to only site two).
    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  26. Imagine... by ReidMaynard · · Score: 5, Insightful

    Imagine you have the only Mercedes-Benz dealership, every morning customers are lined up, check-books ready. Year after year. You are rich beyond imagination.

    Then one day this fellow shows up with a Vespa and says, "You should sell these Vespa scooters too.."

    What do you do..?

    --
    -- www.globaltics.net

    Political discussion for a new world

    1. Re:Imagine... by kv9 · · Score: 5, Funny

      Then one day this fellow shows up with a Vespa and says, "You should sell these Vespa scooters too.." What do you do..?

      I repeatedly slam a car door against your head for using yet another computer/car analogy on Slashdot

    2. Re:Imagine... by Calinous · · Score: 2, Insightful

      Because in some places, ten $5,000 computers could have taken the place of a "small-iron" system costing $500,000 (with the mainframe getting extra money from support contracts).
            As a well known Mercedes Benz dealership, you won't start selling Volkswagens because some of your clients will buy a Volkswagen instead of the Mercedes Benz (and your profit will be lower)

  27. Re:Prophesy? I don't think so by kjs3 · · Score: 2, Insightful

    Spot on. In addition, if Linus or some such had made a couple of conventional wisdom statements that stood up a decade down the line, it would be "brilliantly" or "insightfully"; since it's BG, it's "chillingly".

  28. Re:We're not in lala-land here by ScrewMaster · · Score: 2, Interesting

    IBM got a number of things right, prior to the release of the original IBM Personal Computer. I was working in a computer store at the time, in 1981, working in both sales and service. I was sent to Boca Raton in the first wave of salespeople and technicians for training on the as-yet-unannounced "IBM PC". I was unusual in that I was sent to both week-long classes, because the company couldn't decide whether I was a salesman or a service tech.

    It was a very interesting week. One question that came up early was, "that's great, but is it going to be another Apple ][, where we have to try and sell people a computer that won't do anything unless they write their own software?" Yes, I know, at that point the Apple ][ was already well-established but when it was first released it really had little application support. However, the IBM folks pointed to a shelf full of business software that they had already had ported to their new machine. BPI and Peachtree accounting, a couple of word processors and a bunch of other stuff. Smart, very smart.

    So, in combination with the magic letters IBM and plenty of common business apps including mainframe terminal emulation, it was hard not to sell the things. And this was when the only video out available was the IBM Monochrome Display and Printer Adapter! The original CGA card followed fairly quickly but we still sold a ton of those things with just the original green monochrome text-only display. It was all that businesses needed back then.

    The Apple grew out of the needs of the original hacker community, where everyone wrote their own software, and developed into a serviceable business system because developers jumped on-board and provided the applications software. IBM recognized this need, and made sure that there were enough good apps out for the PC before they even announced its existence. Some of them were rough ports, in a couple of cases obvious conversions from well-known Apple ][ software. But that didn't matter: business wanted an IBM computer system and it had programs that worked. End of story.

    I worked at a game development house in the mid-eighties: that company developed the original graphics demonstration that was shipped with every Commodore Amiga. I didn't get to write code for it, as a matter of fact it had no native development tools and the two guys that were coding for it had to work on a couple of Sparcs (the two machines were in a room with an electronic lock, nobody was allowed in, all very hush-hush.) The prototype Amiga 1000's came in hand-built plywood cases, and didn't even have a power-on/reset circuit.

    Anyway, as impressive a platform as the Amiga was, from both a hardware and operating system perspective, it suffered from a distinct lack of applications and an even more distinct lack of marketing. Commodore could have taken the lead and blown everyone else out of the water, but they apparently made the mistake of assuming that technological superiority would carry the day. It didn't then, and it doesn't now ... even the best products still have to be useful, and still have to be marketed. Commodore never really figured that out.

    I remember their one TV ad, where the sonorous announcer's voice said, "Only Amiga makes it possible." Makes what possible. The ad didn't say, and really was more confusing than anything else.

    --
    The higher the technology, the sharper that two-edged sword.
  29. I call bullshit. The applets are the proof. by dpbsmith · · Score: 2, Insightful

    Windows 3.0 was, at the time, prettier than OS/2, friendlier than OS/2, nimbler than OS/2, ran on small configurations than OS/2, was more compatible than OS/2... and shipped with about a dozen nice little applets like Windows Write that OS/2 didn't ship with. ToolBook, too, if I remember correctly.

    The applets, are for me, the proof. If Microsoft believed OS/2 was the future, why couldn't it spare a few developers to put some of the trimmings on it that would make it appeal to non-corporate users?

    Microsoft devoted what must have been significant resources to making Windows 3.0 more appealing than OS/2. Why should it have been "stunned" when it sold better than OS/2?

    Maybe the parts of the company that were working on OS/2 believed it was the future, when the higher-ups had really placed their bets somewhere else. Things like that happen in big companies.