Talk:Network computer

From Wikipedia, the free encyclopedia

This article needed extensive rewriting, as at least 50% of it was literally /wrong/. An NC is not a dumb terminal, it was a computer in its own right, which happeded to use the network for storage, hence 'network computer'.

I've also added historical information and details of notable implementations, as well as links to some relevant external sites.

Phil webster 11:04, 23 November 2005 (UTC)

Did you fix some of it at least? 220.233.48.200 14:57, 11 December 2005 (UTC)

[edit] The table

The table looks soooooo ugly and isn't using wikimarkup for it, maybe someone which knows wikimarkup well can port it over?

220.233.48.200 14:57, 11 December 2005 (UTC)

[edit] Reasons for the demise

I helped develop Oracle's second-generation NC software stack in the mid-1990s, helped write the reference profile, and collected the T-shirts as well as a garage full of cast-off NCs. I have some insight into Oracle's intent.

The article's representation of Ellison's vision for the NC is somewhat simplistic. We knew the NC would not supplant the PC in all its use cases. We didn't intend that. We aimed it initially at cases in which a significant number of full-fledged Windows PCs at some site were employed in single applications. We conceived of airport kiosks, hotel rooms, hospital rooms, factory floors, and some typical business workstations (e.g., reception desks). The statement that the NC concept is "appropriate … in certain areas" is a validation of our original aim, not a recognition of some failure of it. Ellison deserves credit for realizing at the time the natural limits of the new computing paradigm he was proposing.

We hoped that NCs would eventually find their way into homes, but that was not part of the original marketing or technical strategy. We were well aware that dialup connections were far too slow for what we had in mind. File storage access was over NFS, for example — fairly unusable over a dialup connection. Our intended market presumed reliable broadband connectivity, so claiming that the NC failed to hit a market at which it specifically didn't aim is somewhat misleading at least in Oracle's case.

Oracle did not consider replacing dumb terminals any kind of violation of the "pure" NC philosophy. We expended great technical effort to ensure that terminal emulation was 100% compatible with hardware examples. Replacing aging and broken dumb terminals with cheaper and fixable alternatives (i.e., NCs running software terminal emulators) was expected to be a major source of revenue.

The notion that an NC would perhaps run only one application program in its entire lifetime was quite welcome in Oracle's NC philosophy. Of course we wanted the NC to be seen as a "real" computer, but the selling point was precisely that you could relegate the NC to a single task without a twinge of conscience, since you were presumably already relegating a fully-loaded Windows PC to that same task.

The market reasons for the NC's demise are relatively simple. Oracle intended the NC to reduce the total cost of ownership for computers that were primarily used in very simple ways. Technically we planned to accomplish this by using inexpensive hardware, open-source and open-standard software, and by managing the software centrally at the server. But in the late 1990s the average price of a Windows PC plummeted to the point where the NC could not compete with it on a price-performance basis. And Microsoft began to address the problems of centralized control.

Those who proposed the NC argue that the PC industry lowered its prices out of fear of NC competition, but I can't find any PC manufacturer who will admit to that. But the NC proponents say the NC concept fulfilled its goal (lower TCO) without needing to be realized.

The technical reasons vary from company to company. The Java Station, for example, was simply too sluggish to be useful as a computer. It relied on first-generation Java virtual machines, and so in that case it can be argued that it was ahead of its time. Java is now routinely embedded in handheld appliances such as cellular phones. Oracle's technical problems amounted to biting off more than it could chew.

Trying to displace Microsoft from its entrenched monopoly over the business desktop is arguably a losing proposition no matter how technically advanced your solution might be. Very few competing companies put enough resources into their NCs to match Microsoft's efforts at improving the desktop at the time. Jpwindley 05:59, 19 October 2006 (UTC)

[edit] Non-contributing text removed

I just deleted the text "In The last few years (2006-2007) there has been a "ComeBack" to NC's and Thin Clients for some reasons and certain Applications. First because most advanced computing has become "Web Based Computing" from Internet Cafe's Corporations Education and Mobile Devices that all need Fast Internet with minimum Client needs. Also Important Reasons are Security, Low Maintenance costs, and Server Operating System and Hardware independance. Since Microsoft stopped going against this trend in the 90's and have joined with WEB-TV and are Partners to Citrix and started "Terminal Services". Also the Large "Third World Market" want to extend the life of "Thinner" Clients and Old PC's or inexpensive Laptops and 3G Cellphones." because, frankly, it is awfully written. Motmot 18:29, 11 February 2007 (UTC)