Archives
 
 
 
  Special
 
 
 
  About Us
 
 
 

Newsletter
Free E-mail Newsletter from BYTE.com

 
    
           
Visit the home page Browse the four-year online archive Download platform-neutral CPU/FPU benchmarks Find information for advertisers, authors, vendors, subscribers Request free information on products written about or advertised in BYTE Submit a press release, or scan recent announcements Talk with BYTE's staff and readers about products and technologies

ArticlesCadillacs or Cherokees?


February 1997 / Editorial / Cadillacs or Cherokees?

In our quest to be current, let's not confuse newness with appropriateness.

Mark Schlack, Editor in Chief

Fall Comdex produced a definite feeling of split personality in me, and I bet I wasn't the only one. How could BYTE give Office 97 the Best of Comdex award and suggest that developers will soon be writing to the Java virtual machine instead of the very same Windows APIs on which Office is built?

Let's start with the fact that personal computers -- both PCs and Macs -- were never optimized for simple tasks. In the early days, these machines came into companies on the expense accounts of number crunchers, sales pr esenters, and others whose computing needs were unpredictable, occasionally intensive, and highly individual.

For that reas on, today's applications are overkill for many people. And even though it probably won't, Microsoft should rearchitect its massive products the way Corel is building its Java-suite successor to WordPerfect: as a collection of applets that you instantiate as needed. Why complicate your computer?

Still, let's not throw out the baby with the bathwater. Millions of office workers (me, for one) actually do need the complexity that a suite such as Office provides. It was just as evident at Comdex that high-powered, specialized peripherals and applications can transform the general-purpose PC or Mac into an incredibly powerful and inexpensive productivity tool for graphic artists, engineers, multimedia developers, scientists, and a lot of other specialized users. Heck, for $10,000, you can turn your PC into a broadcast TV studio.

It's become equally clear to me that continuing to debate whether Windows, OS/2, the Mac, or Unix makes the best desktop is not the burning issue it used to be. Ditto for processors . They're all viable, and they all have problems. On the software side, they have roughly the same problem. In order to accommodate the very diversity that is their strength, these OSes have become complex and difficult to manage. They're all basically proprietary, and they're all fat clients, limited in their interoperability.

That brings us to Java. The most important decision today is not which desktop OS to adopt, but whether to stick with the general-purpose, proprietary desktop paradigm of the past 20 years or instead go with thin clients, fat servers, and platform-neutral software, such as Java-, HTML-, and HTTP-based packages. At BYTE, we think the issue is so important that we've devoted two covers in three months to it.

But life isn't always simple. When the PC overtook the minicomputer and the mainframe, these technologies didn't evolve much beyond absorbing PC technology. Don't bet on that happening with the PC-to-network-computer evolution. If Intel, Microsoft, and their partners respond to competitive pressures and take substantial amounts of difficulty out of managing the PC, that environment will evolve and remain viable for a long time. I hope these companies understand that failure to do so will ultimately consign them to niche status.

On the Java side, we all have some tremendous opportunities to blaze new ground, and not just as the champion of Son of Host Computing. For example, the growth of the Web and the Internet means that many developers work for non-IT companies that will be producing products and services that are essentially software; a package-tracking application is a good example. It's the perfect test case for Java: Build an application that can run on any customer's computer. And add to your company's revenues.

But weigh the risks. Java's not yet ready for many big bet-your-business projects. And the Java industry has to prove that it can sustain broad interoperability without turning over the specification process for the language and the virtual machine to a st andards body.

For years, we've been comparing luxury-car desktop environments. Now we need to be concerned about these new sport/utility vehicles as well. We will need to master them both to navigate the information-technology terrain of the late 1990s.


Mark Schlack, Editor in Chief, mschlack@bix.com

Up to the Editorial section contentsSearchSend a comment on this articleSubscribe to BYTE or BYTE on CD-ROM  
Flexible C++
Matthew Wilson
My approach to software engineering is far more pragmatic than it is theoretical--and no language better exemplifies this than C++.

more...

BYTE Digest

BYTE Digest editors every month analyze and evaluate the best articles from Information Week, EE Times, Dr. Dobb's Journal, Network Computing, Sys Admin, and dozens of other CMP publications—bringing you critical news and information about wireless communication, computer security, software development, embedded systems, and more!

Find out more

BYTE.com Store

BYTE CD-ROM
NOW, on one CD-ROM, you can instantly access more than 8 years of BYTE.
 
The Best of BYTE Volume 1: Programming Languages
The Best of BYTE
Volume 1: Programming Languages
In this issue of Best of BYTE, we bring together some of the leading programming language designers and implementors...

Copyright © 2005 CMP Media LLC, Privacy Policy, Your California Privacy rights, Terms of Service
Site comments: webmaster@byte.com
SDMG Web Sites: BYTE.com, C/C++ Users Journal, Dr. Dobb's Journal, MSDN Magazine, New Architect, SD Expo, SD Magazine, Sys Admin, The Perl Journal, UnixReview.com, Windows Developer Network