After the Software Wars (Paperback)

~ Keith Cary Curtis (Author)

Editorial Reviews

Product Description

Given the technology that's already available, we should have cars that drive us around, in absolute safety, while we lounge in the back and sip champagne. All we need is a video camera on the roof, plugged into a PC, right? We have all the necessary hardware, and have had it for years, but don't yet have robot-driven cars because we don't have the software. This book explains how we can build better software and all get our own high-tech chauffeur.

Product Details

• Paperback: 304 pages
• Publisher: keithcu press (February 20, 2009)
• Language: English
• ISBN-10: 0578011891
• ISBN-13: 978-0578011899
• Product Dimensions: 8.9 x 6.1 x 0.9 inches
• Shipping Weight: 9.6 ounces (View shipping rates and policies)
• Average Customer Review: 3.3 out of 5 stars  See all reviews (6 customer reviews)
• Amazon.com Sales Rank: #303,726 in Books (See Bestsellers in Books)

Customer Reviews

Most Helpful Customer Reviews

12 of 12 people found the following review helpful:

5.0 out of 5 stars A Better Future for Software, April 25, 2009

By	Lorenz Gude "Newmediatheory" (Perth Western Australia) - See all my reviews (REAL NAME)

The existence of free software is an anomaly. It does not fit our assumptions about what must be private property and what should be free to all. Keith Curtis's After the Software Wars is hard to put down because it makes a passionate case that software should be treated like the free exchange of ideas in the world of science. The book manages to consistently upset our industrial age assumptions about proprietary software. Many, including myself, would point out that the demise of proprietary software is not a done deal and would argue that software is a combination of freely exchanged science and proprietary applied science. But Curtis's argument is based in experience (11 years programming at Microsoft) and like a good lawyer arguing one side of a case he forces us to consider the merits of his position.To interested computer users like myself who are not programmers, he convincingly peels back the layers of the software development process so that we can see the strengths of free software (and the weaknesses of proprietary software) very clearly indeed.

During his time at Microsoft Curtis saw Windows struggle with the expensive limitations of the closed industrial model while its free rival - Linux - consistently improved relative to Windows to the point where he is now quite happy to use only Linux. (I have used it as my main operating system for over a year and agree it compares favorable to Windows in most ways). The book is also timely because it asks us to take seriously a clearly less expensive and arguably better approach to software development at a time when economic stress makes it particularly relevant to do so.

While the Linux phenomena tells us that the assumptions of the industrial age don't work for software, it doesn't necessarily tell us where the open model is most important or essential to progress. Linux may or may not go on to 'world domination' as Curtis puts it - Microsoft is making a serious comeback just now with Windows 7 and remains dominant with over 90% of the world's desktops despite shooting itself in the foot with Vista. Still, After the Software Wars makes it much easier to appreciate the enormous difficulties Microsoft faces trying to maintain a secure and smoothly functioning operating system using the proprietary model.

In the second half of After the Software Wars Curtis turns his attention to programming languages, and demonstrates where the proprietary model may well be holding us back in a more fundamental and critical way. He makes the case that the dominant C and C++ programming languages are obsolete and worse - disastrously inefficient. Neither are proprietary which may partly explain why they continue to dominate software development despite their origins in the technology of the 70s. For example, Curtis explains how they suffer from serious limitations such as failure to clean up memory after use (programmers call it garbage collection) which in turn is a major source of bugs requiring endless further work. However, in terms of the free versus propriety dilemma I think his most telling example is his account of how Sun and Microsoft fought to control Java and ruined its chances of becoming a more efficient replacement for the older languages. The implication is clear - developing an up to date, open source, programming language may be more urgent and necessary than even the adoption of Linux.

Speaking for myself as an observer of the interaction of society and technology in the McLuhan tradition I see the simple existence of free software as requiring a change in how we divide what is held in common from what is proprietary. Just as movable type contained a core idea of the industrial revolution - interchangeable parts - I think that free software will eventually compel a new understanding of what divides common from private property.

4 of 5 people found the following review helpful:

4.0 out of 5 stars Insightful, July 7, 2009

By	D. Slager (Puget Sound, WA) - See all my reviews (REAL NAME)

Very interesting to read. Along with another reviewer, I'm not sure about the applicability of the last couple chapters but the rest of the book is great.

I have a lot better understanding now of why Linux and Windows OS's are so different and why the potential of Open Source software and Linux is virtually unlimited.

Linux and Open Source are getting very close to a critical mass; once they do achieve critical mass, the software world will change dramatically (and get a whole lot cheaper!).

I read the PDF version.

1 of 2 people found the following review helpful:

5.0 out of 5 stars Very Intersting and Inspiring Read - Looking forward to next publication, August 18, 2009

By	Shannon VanWagner (Seattle, WA) - See all my reviews (REAL NAME)

This book was very interesting and I enjoyed reading it a lot. The author does a great job in making his points about getting the most from computer technology.

"After the Software Wars" combined the perfect amount of interesting examples, real-life stories(and "dirt"), personal experiences, compelling scenarios, future predictions, technical computer jargon, and carefully researched information to be a great read for people ranging from merely being "interested" in technology to proven technology professionals alike.

What was remarkable to me about this book, is that while I disagreed with some of the arguments the author made, I was still won over by the overall intent of the book - which is the assertion that Freedom, Openness, and Shared Achievement of computer software is the best possible way to solve some of the most massive and exceedingly demanding problems that humankind are faced with today.

I recommend "After the Software Wars" to anyone who is interested in computerized technology and I look forward to seeing more publications from this Author.