|This article does not cite any sources. (June 2009) (Learn how and when to remove this template message)|
NetPositive 2.2 under BeOS R5 showing Wikipedia (no CSS support)
|Stable release||2.2.2 / November 1, 2001|
Built binaries of NetPositive, including all encryption libraries, and other tools not provided by the OS itself, such as the HTTP and FTP engines, weigh in from 1.4 to 1.7 MB in size, uncompressed, depending on the strength of encryption provided.
NetPositive can be embedded into another application, or into the desktop of the OS itself, using the replicants system provided by the OS. When Active Desktop was launched on Windows, Microsoft promoted it as having been a major achievement. Be later claimed to have cloned the functionality using NetPositive (where Internet Explorer is used in Windows) in "nine lines of code".
A number of projects exist to clone NetPositive for BeOS, due to BeOS users' familiarity with its interface. The most advanced of these is Themis, which aims to capture the feel of NetPositive in a browser with modern features. There is also Net++, which aims to use the Gecko layout engine in the shell of the failed NetOptimist browser. For Haiku there is a successor for NetPositive, based on WebKit, called WebPositive.
It is still included in ZETA as the default browser for opening saved files and links from other applications, due to unfinished implementation of the native OS bindings in Mozilla Firefox for BeOS. However, Firefox is promoted as being the primary browser on the platform.
Error messages in Haiku
The browser was notable among BeOS users due to its haiku error messages, which led to the name of Haiku, an open-source BeOS clone. A late 1990s email joke which claimed that Microsoft was moving to Haiku error messages in Japanese versions of Windows was almost entirely made up of NetPositive error messages. For instance, a user might see the following error message if they try to access a website that is unavailable:
- Cables have been cut
- Southwest of Northeast somewhere
- We are not amused.
If the user tried unsuccessfully to authenticate against a website, they might see:
- Server's poor response
- Not quick enough for browser.
- Timed out, plum blossom.