Slashdot Mirror
Is Caps Lock Dead?
An anonymous reader asks "Recently I have noticed that I haven't used caps lock other for any purpose other than hitting it by accident. Once upon a time, COBOL was written in all caps, and other languages like BASIC and Fortran were not case sensitive. Capitals were the way to go for writing code. Does the caps lock key serve any purpose any more, and if not, should it be removed, moved, or replaced?"
Caps Lock is EVIL!
I remapped my capslock into an extra control key months ago. I never type more than a couple of words in capitals, and can easily hold down the shift key.
Capslock is just a problem when you accidentally hit it when reading something you are keying in.
Writers and layout people use cap lock all the time. Most will use it from time to time in standard word processing. Computers aren't just for programers. Some of us use the software they write.
I use Caps Lock to check if Windows has completely frozen up. If the light on my keyboard doesn't come on, it's time to do a hard reset.
Of course caps lock is necessary. It's necessary for whenever you want to type in all-caps without holding shift the whole time. I can think of dozens of examples of this. Hell, where I work, the blank fields on our contracts must be typed in all caps. I wrote a screenplay once, and you need caps all over the place. When I'm coding, I write some macro names in all-caps.
No, the caps lock shouldn't be removed or replaced. It's handy to have a key that allows you to toggle lower to upper caps so you don't have to hold shift.
Pointless Ask Slashdot question!
"Sufferin' succotash."
More useful than switching with escape is switching caps lock with Control.
You should have:
Option "XkbOptions" "ctrl:swapcaps"
In the InputDevice section for your keyboard (in XF86Config, of course).
Voila'! Ctrl assumes its rightful place on the keyboard. Ergonomic implications are massive.
Equivalent hack is available for NT too. It's done via registry, but I can't be bothered to google for it right now.
Save your wrists today - switch to Dvorak
You say it doesn't help if you have a syntax highlighting editor; you can't count on having a syntax highlighted editor all the time.
While I think there are benefits to it, many interns that I've worked with seem paralyzed if they don't have syntax highlighting. A few are paralized if they don't have auto-complete. If the code REQUIRES syntax highlighting to be understandable, clearly you need to adopt a different style.
If you don't have SQL syntax highlighting, the more complex the SQL statement is the more it benefits from the all-cap keywords. That in itself is enough to justify (for me) it's use. Since I compose my SQL statements in my C++ interface code, I don't have SQL syntax highlighting; the C++ editor highlights them all as strings. Using caps really helps readability, especially when the SQL statements are complex and require several lines to compose.
//TODO: Think of witty sig statement
The problem with making ANY remapping changes to your keyboard is that in a programming environment where you frequently have to hop on other people's comps to "drive", you instantly take on the role of "goober who can't type" rather than "superhero debugger". It's bad enough there isn't universal standardization of the all-important backslash key, which 2/3 of the time is a std-sized key below enter and 1/3 of the time a 2x length above it.