Indeed. You can (and should) color correct an LCD (and should do the same for a CRT anyway) at the OS level if accurate reproduction matters to you. But that's only part of the puzzle. Many LCDs I've encountered are extremely sensitive to viewing position. My laptop has a very obvious gradient from top to bottom at normal viewing distance which shifts dramatically on the smallest movement of your head relative to the screen. It's completely useless for anything where color and tone are even a little bit important. My older LCD monitor has a less-pronounced version of the same problem. The newer displays I have at work are a lot better in this respect but still aren't quite there. These are relatively cheap displays though, the higher end LCDs I'd expect to be much better.

I use an old Trinitron CRT (picked up for $5 at Goodwill) for photo editing. Never could get reliable color or tonal rendition out of any LCD I own; an expensive IPS type one might fix that problem but expensive isn't an option right now. I also found that the slightly fuzzy pixels cause the CRT to render much more like the final print that an LCD does without causing me eyestrain. Our TVs are all CRT, just because they still work. We're not into TV or movies seriously enough to justify replacing them "just because", in fact we only really use one of them on any sort of regular basis so the other two are likely to stay as CRTs for a very long time. But for programming or anything else involving text, it's LCD all the way. Much easier on the eyes for those tasks.

My first full-time job we had logins to both our local system and various scattered mainframes which belonged to our major client. The mainframes required a monthly password change and were strict about not reusing old passwords. After a few months of this I started using profanities as passwords. Then one day, we had a group of new hires. For various reasons the only way they could train to use the mainframe system was to borrow other people's accounts, and so my dirty password secret was out. I've also learned the hard way that certain things should never, EVER be used as passwords. For a brief moment, I used 'rm -rf /' as my password. On a Linux system. Which I had root access to. And often had multiple open console windows, some of them with aforementioned root access. It was only a matter of time before I tried to enter my password while being distracted and having input focus on the wrong console window. :sigh: Luckily, we had a full system backup and the server wasn't in production yet.