Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Software Books Media Book Reviews

From Airline Reservations to Sonic the Hedgehog 62

danny writes "From Airline Reservations to Sonic the Hedgehog is a history of the United States' software industry, down to 1995. Read on for my review."
From Airline Reservations to Sonic the Hedgehog
author Martin Campbell-Kelly
pages 372
publisher The MIT Press
rating 8
reviewer Danny Yee
ISBN 0262033038
summary A History of the U.S. Software Industry

From Airline Reservations to Sonic the Hedgehog is a history of the software industry in the United States, down to 1995. It avoids technical details -- there's little about software engineering and programming languages, for example, or developments in computer science -- to focus on the economic and business accompaniments of technological change. And Campbell-Kelly is an academic historian, providing full references and a discussion of sources and avoiding hype or dramatisation. But From Airline Reservations is never heavy going: the less interesting tables can easily be skipped over, the references are out of the way as endnotes, and short, focused case studies make for compelling reading.

An introduction discusses industry statistics, other sources, and the restriction to the United States. The basic structure is then chronological and sectoral, with a three sector division into software contracting, corporate software products, and mass-market software products.

Two chapters cover software contracting. In the 1950s, IBM's Technical Computing Bureau and SHARE user groups were important players and FORTRAN and COBOL were developed. The Systems Development Corporation, set up to produce software for the national defense network (SAGE) required thousands of programmers and became a kind of "programming university," while the SABRE airline reservations system was the most important civilian project. As well as large systems integrators there were small software contractors, some of which were to grow rapidly.

The 1960s saw consolidation, with an increasing need for marketing and project management skills as well as casualties from a computer "utility" fad (early Application Service Providers) and the computer stocks crash of 1970. New firms continually appeared, however, with high turnover. Coverage of software contracting stops there, with a closing comment that: "Software contracting remains the most popular way of participating in the software industry, programming services enterprises outnumbering software products firms by 2 or 3 to 1."

There are three chapters on the software products industry. The first covers its origins between 1965 and 1970, with extended case studies of two leading products: ADR's Autoflow (flow-charting) and Informatics' Mark IV (file management). The significance of IBM's 1969 unbundling of hardware and software is also treated at length.

Next comes a survey of software products through the 1970s. These were classified by supplier (computer manufacturers and independent vendors, with some turnkey vendors, software brokers, and time-sharing services) and by category. The latter included systems (database systems, IBM's CICS, Unix) industry-specific (banking, manufacturing), and cross-industry (accounting, office automation, CAD) software. Campbell-Kelly suggests that the increasingly fine classification of software was itself significant.

The period from 1980 to 1995 saw "the United States' lead in software products become seemingly invincible." This is illustrated with case studies of IBM (a manufacturer) and three big independent vendors: Computer Associates (a consolidator), Oracle (databases), and SAP (ERP software). One reason for the success of the latter, a German company, was that European companies lagged those in the United States and had not yet invested in company-specific software.

Then come three chapters on the personal computer software industry. The first covers the pioneer period from 1975 to 1983, beginning with the origins of the microcomputer and the "first mover" advantage in operating systems held by Digital Research and then Microsoft. Also covered are programming languages and VisiCalc and other productivity software packages. In production and distribution "there was almost no point of contact between the booming microcomputer software industry and [that] for corporate mainframes and minicomputers."

The second chapter continues the story down to 1995. Much of this involves Microsoft, of course, but the chapter title is "Not Only Microsoft" and Campbell-Kelly argues that it has received disproportionate attention. Topics covered include the IBM PC standard, Autodesk and AutoCAD, the race for a GUI, battles between Lotus 1-2-3 and Excel and between WordPerfect and Microsoft Word, Adobe, and others. Success in the PC software industry came not just from luck, but from exploitation, deliberate or not, of the economics of increasing returns.

A third chapter looks at home and recreational software, in particular at games (and game consoles), CD-ROM encyclopedias, and personal finance software (Quicken versus Microsoft Money). Here Campbell-Kelly sees "a historical trend for software to become subordinate to the intellectual content or the complementary services offered".

Campbell-Kelly himself is British and there are occasional references to British and European companies, but the focus is on the United States. A final chapter looks at reasons for the success of the U.S. software industry: an early start and market size, clustering effects, and government support for R&D.

On "political" issues, Campbell-Kelly takes a more positive view of Microsoft than some: "Microsoft's monopolies and abuses do not seem any worse than some of the others described in this book." He also ignores free software completely, which is perhaps reasonable given the end-point in 1995, though the GNU Project and its antecedents would have made a interesting topic -- and hindsight suggests that the idea of free software was more significant than any specific product.

From Airline Reservations to Sonic the Hedgehog should command a wide audience: participants in the industry, both programmers and managers, students of economics and business, and the interested general public.


Danny's book reviews cover many other business, computing, and economic history titles. You can purchase Airline Reservations to Sonic the Hedgehog from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

This discussion has been archived. No new comments can be posted.

From Airline Reservations to Sonic the Hedgehog

Comments Filter:
  • Dead? (Score:5, Funny)

    by ergonal ( 609484 ) on Monday May 05, 2003 @12:07PM (#5882511)
    Ah, so this article would be the obituary of this [slashdot.org]. I'm sorry to see you go Software Industry! RIP!
  • by binaryDigit ( 557647 ) on Monday May 05, 2003 @12:08PM (#5882520)
    "And hindsight suggests that the idea of free software was more significant than any specific product."

    I assume he means that the concept of "open software" is more significant than any particular open project, not that it is more significant than any particular software, period (open/free or not). If it's the latter, I'd have to disagree. Singular apps like VisiCalc, WordStar, Lotus 123, dBase, Windows, PhotoShop et al helped to create what the software industry is now, which in turn has helped to create an environment in which open software could even exist.
    • by tuffy ( 10202 ) on Monday May 05, 2003 @12:38PM (#5882801) Homepage Journal
      Singular apps like VisiCalc, WordStar, Lotus 123, dBase, Windows, PhotoShop et al helped to create what the software industry is now, which in turn has helped to create an environment in which open software could even exist.

      Before there was a software industry, software was effectively free from hardware manufacturers. And, one typically received the source code along with it. Only with the unbundling [softwarehistory.org] and charging for software did a seperate industry for it come about - eventually necessitating the creation of an "open source" movement. So, in a sense, open software has existed before the industry itself. But Bill Gates and the industry has become entrenched to the point that the notion of software one doesn't have to pay for seems novel.

      • by binaryDigit ( 557647 ) on Monday May 05, 2003 @12:54PM (#5882951)
        Before there was a software industry, software was effectively free from hardware manufacturers

        Apples and oranges. The whole reason the software could be "given" away was that the two were sold as a package. People bought "systems" and "solutions" and a "cheap" system was six figures. Plus then the cost of software was easily subsidized by the hardware and support costs. You're referring to a completely different model and you can't compare that to the pc and current software.

        But Bill Gates and the industry has become entrenched to the point that the notion of software one doesn't have to pay for seems novel.

        The software industry was well entrenched even without Bill's help. Plus, one ALWAYS pays. Except for people who are working on "commercial" OSS, what do these programmers working on "other" OSS projects do to pay the bills. The vast majority of them write software that costs money. A "free" software market can't support itself, it is way to resource intensive. It has to be buoyed by something.
        • The software industry was well entrenched even without Bill's help. Plus, one ALWAYS pays. Except for people who are working on "commercial" OSS, what do these programmers working on "other" OSS projects do to pay the bills. The vast majority of them write software that costs money. A "free" software market can't support itself, it is way to resource intensive. It has to be buoyed by something.

          That "something" was typically hardware sales, software comissioned from software houses by customers or by in

        • Wasn't this the very thinking that caused IBM to license the OS from Microsoft, instead of actually buying it?
  • Whats the point? (Score:5, Insightful)

    by WndrBr3d ( 219963 ) * on Monday May 05, 2003 @12:09PM (#5882539) Homepage Journal
    These book reviews on Slashdot, at times informative, really just are letting people know about the book and not as much reviewing that.

    This demonstrated is that in the last two months, no book has received less than a 80% approval rating by the author (unless you rate a 'very good' This (book) gets my lowest rating ever, seven thumbs up.

    I mean honestly, a review needs to have a few lemons on its record. I think someone should review a Wrox book on Linux and have it summarized with, "This book really gobbled the cob. it wouldn't be fit to like the kitchen floor for my puppy to soil in the evenings."

    Instead of calling it 'Slashdot Book Review', it should just be called 'Slashdots list of books that rule'.

    That's just my opinion though, I could be wrong.
    • Maybe "Slashdot Reading List"?

      But then, of course, you'd be implying that the people who work at Slashdot would be reading these books, so...
    • Re:Whats the point? (Score:5, Interesting)

      by ryanr ( 30917 ) * <ryan@thievco.com> on Monday May 05, 2003 @12:34PM (#5882766) Homepage Journal
      I've exchanged mail with one of the Slashdot guys on the topic of reviews before. He specifically said that they don't like to post the bad reviews.
      • He specifically said that they don't like to post the bad reviews.

        So I have to ask, what's the point? Frankly, the negative ones are far more useful.
        • Good question. I didn't get a reason as to why no bad reviews. I suppose if one wants to be cynical, they could assume because they don't get any click-through purchases on BN.com or thinkgeek. I don't see what it would hurt them any, though... certainly they might get slightly more revenue from bad reviews than from missing reviews.

          It's probably something as simple as the bad books just don't get finished, so the reviewer doesn't write a review. The reviewers are all volunteer, I believe.

          That's obvio
        • So I have to ask, what's the point?

          While not as much value as also seeing the negative ones, it's certainly not pointless.

          We get to know about good books to which we might not otherwise be exposed. Sure, I'd like to see negative reviews as well, but given the choice between no reviews and only seeing the positive ones, I'd much prefer the latter.

          This is not the same as rubber-stamp reviews, where any piece o' trash gets a positive review, but rather a filter blocking the negative ones.

    • Sometimes it is no necessary to analyze a book's karma in order to do a good review.

      I've read about half of this book, and I think this is a good review of the contents with something about the author's point of view thrown in. It describes the features that would make someone decide to spend their valuable time with this book.

      I don't think there is anything wrong with this particular review. As far as the overall reviews go, you could find a book that has been a real disappointment and do a review. That
    • Re:Whats the point? (Score:4, Interesting)

      by Turing Machine ( 144300 ) on Monday May 05, 2003 @01:21PM (#5883193)
      You make a good point. On the other hand, I'd really rather hear about good books rather than books that suck. There's no way I can read even a tiny fraction of a percent of the books that are published. A negative review isn't necessary to convince me not to read a particular book; that's my default action anyway (and that of everyone else).

      While I enjoy a good slagging as much as the next person, positive reviews are ultimately more helpful to me in wading through the torrent of books emanating from the publishing industry.

      I guess the exception would be when a sucky book/CD/movie/game gets overly hyped. In that case, a negative review could be very useful.

    • I think that another factor is that these are volunteer reviews (ie. they don't get paid).

      This matters because in general people don't finish books that they don't like. If I'm a third of the way through a really bad book I'm not going to say "well, I'm going to finish this books so I can write a bad review of it". No, I'm going to throw it in the trash and never think about it again.

      On the other hand, on sites where the reviewer is getting paid, they'll stick with the book through the end and do the revi
    • Speaking as a reviewer, I tend not to write many negative reviews because I usually don't bother reading bad books. Also, with so many books out there, helping people avoid bad ones is less useful than helping them find good ones.

      But I have written some pretty negative reviews:

      (Maybe I should add a "bad books" page to the site.)

      Danny.

  • Up and Down (Score:4, Informative)

    by Mad Man ( 166674 ) on Monday May 05, 2003 @12:10PM (#5882549)
    From Airline Reservations to Sonic the Hedgehog is a history of the software industry in the United States, down to 1995.
    Shouldn't that be "up to 1995"?
    • Up, down, sideways. Does it really matter? I mean:
      1- this book only goes to 1995. What about post 1995? In terms of the computer industry, that might well be two whole epochs.
      2- this is only told from one side. If it had a few authors, it might be a better view, but this is just one guy, giving HIS perspective.
      Sorry, but I think I will wait for the movie.

      RonB
    • And if I travel from Sydney to Canberra, am I going "down to Canberra" or "up to Canberra"? I think in these cases either preposition has pretty much the same meaning.

      Danny.

  • Ahh... perspective (Score:5, Insightful)

    by TopShelf ( 92521 ) on Monday May 05, 2003 @12:12PM (#5882566) Homepage Journal
    It's interesting, particularly in this post-.com, "oh my god their outsourcing!" environment to see a historical perspective that ends just when the madness started spreading. While the technical issues may have changed over the years, the overall industry trends often seem to come back time and again in familiar form. I think too often those involved with tech business fail to take a long-term historical view of things, but are instead focused solely on the few steps that appear ahead in the road...
  • by Guppy06 ( 410832 ) on Monday May 05, 2003 @12:27PM (#5882699)
    "From Airline Reservations to Sonic the Hedgehog is a history of the software industry in the United States, down to 1995. It avoids technical details"

    Technical details like "Sonic is a product of the Japanese softawre industry"...
  • Comment removed (Score:5, Interesting)

    by account_deleted ( 4530225 ) on Monday May 05, 2003 @12:39PM (#5882812)
    Comment removed based on user account deletion
    • I don't think the open source movement was all that significant before '95
    • Open source wasn't mainstream until after 1995. Before then, Linux was the realm of geeks and technical gurus, and the majority of computer (l)users were Windows Oh-Look-It's-Asking-Me-What-To-Do! Drones. Open source was beyond their limited knowledge of the computer.
    • I agree, I first used Free software in 1987, at least Emacs, GCC, and a pile of BSD software. GCC was already considered one of the leading compilers out there, and the BSD software considered the way to go when it came to networking computers. It was at Carnegie Mellon, and they were just finishing up phasing out a TOPS network for a predominately BSD-licensed Unix network with a lot of home grown bells and whistles called Andrew [cmu.edu].

      In 1987, Sun Microsystems [sun.com], the "young upstart" company of the data center,
  • Sonic? (Score:3, Interesting)

    by badasscat ( 563442 ) <basscadet75@yah o o . c om> on Monday May 05, 2003 @12:50PM (#5882899)
    Ummm... [sonicteam.com]

    That doesn't look very American to me.
  • SEGA (Score:3, Informative)

    by Sophrosyne ( 630428 ) on Monday May 05, 2003 @12:54PM (#5882953) Homepage
    SEGA was founded by an American, I have not read this book- but it never says in the title that Sonic was American.
    Sonic, I'm sure, had a huge impact on the software industry in the U.S. as well as other big franchise games, so just because it was made in Japan does not mean that it didn't impact the USA.
    • SEGA was founded by an American, I have not read this book- but it never says in the title that Sonic was American.

      No, but it does in the review posted here. "a history of the United States' software industry." Sega may have been partially founded by two Americans, but it was founded in Japan and has always been a Japanese company (prior to its move to Japan in the 1950's, it was not called Sega and did not produce the same products - effectively, it was a different company). In fact, the original n
      • You may be right, but perhaps the point was to show how Sonic changed the way software was developed in America, although somehow I doubt it... you are probably right and i am probably going to avoid this book.
  • is not mentioned in the review but is owned
    by archie comics.

    - Dr. Robotnic
  • ... to 1995 (Score:4, Insightful)

    by hndrcks ( 39873 ) on Monday May 05, 2003 @01:12PM (#5883108) Homepage
    down seems like the right direction.

    "...battles between Lotus 1-2-3 and Excel and between WordPerfect and Microsoft Word, Adobe, and others."

    I would contend Novell's battles and missteps are equally important; and certainly worth mentioning.

  • 1995 [emulationzone.org] was not exactly a banner year for the blue blur. In fact, with the exception of 1997, it may have been his worst year ever.
  • apropos (Score:2, Interesting)

    by ch-chuck ( 9622 )
    Interestingly I was just playing with old media this last rainy weekend, and a 1983 copy of MultiMate (Word processor) run just fine on an 180Mhz pentium once I put the 1.2Mb 5.25" floppy disk in. It had no idea of the 'fixed' disk, kept asking to insert disk for drive b: etc.

    I'd love to find: PL/M-8 (pl/m for the 8008) and a SCELBAL book.

  • by nero4wolfe ( 671100 ) on Monday May 05, 2003 @01:36PM (#5883361)
    As a former employee of SDC (late 70's to early 80's), the correct name is "System Development Corporation", not "Systems Development Corporation". This is because the company was spun out of Rand to develop one system; the first computer system for NORAD. SDC disappeared in the 80's after Burroughs bought it. There was a free software community back then. An informal group of people in organizations with Unix source licenses swapped tapes. There was an "informal" national Unix users group meeting the summer I graduated from UCLA; I remember playing with the tape from that meeting.

Congratulations! You are the one-millionth user to log into our system. If there's anything special we can do for you, anything at all, don't hesitate to ask!

Working...