Haiku isn't intended as a server OS. It has solid networking (contrary to what another poster wrote), and you _might_ be able to run a cut down version of it as a server OS, but that's going way out of the normal use case for the OS.
BeOS had pretty much no concept of users and process segmentation. Basically anybody who can enter a password has unrestricted access to everything and all programs can run with equal privileges, à la DOS/Amiga/macOS_classic/Windows9x. This is fine for a workstation (maybe?) but definitely not suitable for hosting server applications and daemons that you want to be run in restricted security contexts.
Comments
Haiku isn't intended as a server OS. It has solid networking (contrary to what another poster wrote), and you _might_ be able to run a cut down version of it as a server OS, but that's going way out of the normal use case for the OS.
How do you think that it wouldn't perform? Aside from generalizing. Is there some issue that needs to be overcome?
BeOS had pretty much no concept of users and process segmentation. Basically anybody who can enter a password has unrestricted access to everything and all programs can run with equal privileges, à la DOS/Amiga/macOS_classic/Windows9x. This is fine for a workstation (maybe?) but definitely not suitable for hosting server applications and daemons that you want to be run in restricted security contexts.