Comment Old man HPUX user (Score 1) 152
When I first started in IT at the Enterprise level many many years ago I use HPUX for developing telephony software. At the time we used HPUX as a Command and control of our systems. It was also used to develop software for the Motorola 68020 switching systems.
HPUX was not actually a multithreaded OS then. It had fake threads implemented with interrupts. This caused us no end of grief at the time. All of these low level hacks to ensure that things didn't lock up. We needed something that could handle real time systems. HPUX was not it. But we made it work.
( Side bar, We did code reviews on paper from dot matrix printers. The printers were always inside sound proofed boxes they were so loud. )
On top of that we had to make our interface work in the god awful CDE UI environment. Meta-Meta hell.
Solaris/SunOS at the time was light years ahead.
Then in the early 2000's the move to RHEL was on. Finally we could make clustered environments with fault tolerance. RHEL may not have been the most stable at the time. But we finally had the tools to build clusters that would blink an eye when a node went down. In the HPUX days, this was a pipe dream. The OS and the tools just didn't exist.
Now things have moved on to the next level of with containers and very light weight Linux based containers. Which is a good thing.
Rewinding the clock. back to those early days. What we were really trying to implement was what we know as containers today. We wanted systems that we could maintain deploying small updates frequently and having zero interruptions. This contained cloud style environments is what we really wanted back then. Of course we didn't know all what was needed to make that happen.
Long story short. I hated HPUX. It was horrible to code for. And the code was simply not portable unless we put in 5x the work.