Slashdot Mirror
A Look at IRIX 6.5.17
XFS writes "OSNews got their hands on the latest version of IRIX, 6.5.17 (released in August), and they have published an interesting article about it and they explain why IRIX was and still is, one of the best workstation Unices out there. Especially when it comes to multimedia/GL performance. I hope SGI will do something with IRIX though, as they seem to have let it fall behind and be one of these great technologies that get lost through various corporate focus shifts..."
Not sure what this is implying, but it seems to be a surprisingly common misconception that MacOSX has vector based artwork. Not so. GNOME can do, and I think KDE3.1 can as well, via SVG. MacOS icons though are just bitmaps in a variety of sizes, with some scaling/blending algorithms applied.
The SGI desktop is of course based on a heavily modified commercial X Server. And here I will stop for a second, get a big breath and say: 'wow'. I have never seen an X server being so fast, on a 5-year old machine (no matter if this is an SGI machine or not).
I'd kind of expect this given that IRIX comes as a bundle with the hardware. When you choose the hardware as well as the software you can of course optimize the drivers a lot, so you will get good speeds out of it. XFree has to deal with a lot of different hardware, and the driver manufacturers are sometimes less than helpful. Probably worth remember that IRIX won't have some of the newer X extensions like XRender.
IRIX might have enterprise-level performance, but it suffers enormously in the usability department. I work in a lab where IRIX is standard, because 64-bit memory addressing and extreme graphics performance using ImageVision is a must. However, I keep running into issues with the development tools. Most impotantly, SGI's cc (c compiler) is slow and hard to customize flags on, especially for debugging. Furthermore, frequently, if my program commits a memory fault, it receives a SIGKILL rather than a segfault which makes it very difficult to debug (this usually happens if the malloc pool gets corrupted or while using ImageVision).
The ImageVision library (an OpenGL-based image processing system) hsa great performance and features. However, it refuses to link with programs not built with cc (thus, no gcc!). Furthermore, programs that seem to follow spec mysteriously die with a SIGKILL during deallocation. I certainly realise that I might be doing something wrong in the way I call the library, but it does not provide any error
message, exception, or fault.
Finally, IRIX standard header files are a colossal mess and almost impossible to use. Standard C and C++ objects are casually redefined throughout the header structure.