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."
Just move the caps-lock key to the scroll lock button ;). Anyone ever uses -that- button anymore nowadays ?
#include "sig.h"
I am still amazed that after 20 years of the desktop PC, we still have to press the key labelled [F1] to get any type of GUI help, rather than having a key labelled [HELP], although Microsoft did find a way of squeezing in a key with the Windows logo.
Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
hold down shift?
everything in moderation
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
This is one sad excuse of a story. Aren't there any leftover SCO blurbs to fill in?
---
SCO is weenies
Gator is Spyware
Microsoft is thugs
What if he types with only one finger?
My KVM switch uses Scroll Lock (hit twice within 1/2 second) to enable the other keys for switching machines. If we don't have some useless keys on the keyboard, devices like my KVM switch would have to hijack functions I actually use once in awhile, which would be annoying.
Brackets contain world's first nanosig, highly magnified:[.]
If you are teaching young children how to type on computers, you would almost certainly still find a use for caps lock.
While some of them can handle Shift + letter, many of them rely on Caps Lock to get a capital letter through, especially when they are just getting started.
Medicare rules require all digital claim information to be submitted in ALL CAPS for processing. Lowercase alpha characters get claim reimbursement requests rejected.
Ask the Japanese if they should get rid of hiragana since they have katakana, or get rid of kanji since they can simply spell phonetically. Uppercase characters are still important to data processing and the proper use of the English language.
I did the same thing after I got fed up with the key, and found a nice utility to remap it on my Windows machine at work - life's so much easier that way.
And do you give your constants names so long that you really need to use your caps lock key instead of just using shift?
Of course I do. Don't you?
Either your code is full of single-letter names, or you don't do much programming. Holding down Shift while typing hurts my fingers if I do it too much. If I didn't have CAPS LOCK I'd be on workers' comp by now.
I use Home, PgUp, PgDn, and End all day long. Combined with the Ctrl and Shift keys, they are very powerful for navigating aound your documents, editing code, etc. Once you master using these keys and their Ctrl/Shift combos, you will rarley use a mouse again.
TODO: Insert witty sig
Why not just use the Esc key as your "ESC" key?
In the US Air Force, we use CAPS LOCK all the time. It sucks. It's a pain in the ass because they want so much stuff in capitals, like its better that way. I'm a fan of readability. And if everything is in caps anyways, then everything stands out, so why use it. Also, working for the government, you'll notice a lot of busted up keyboards with no caps light that works. So when putting in passwords can be a bitch sometimes.
Mark
I usually use NumLock for that...
Scroll lock is useful to stop the console scrolling (in linux VCs) when some program is spewing lots of data to stdout/err
It can be dangerous. I remember once pressing it accidentally while burning a CD. cdrecord locked trying to write its progress to the console, the CDwriter buffer emptied, and I lost the CD.
This honestly does not bother me that much. If the placement of keys on the keyboard gets you hot and bothered, seek help.
I hate sigs.
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
It's a fairly common convention to have macro names in C/C++ be all caps. This is where I seem to use the CapsLock key the most anyway.
"In mathematics, it's not enough to read the words -- you have to hear the music"
Pressing capslock puts the keyboard into upper case until the shift key is pressed. Then it should go off.
While I think this is a clever idea, it would nullify the point above. People who use capslock to type in long constants would have to press it after each underscore. As any decent programmer will tell you, ACONSTANTNAME is much worse than A_CONSTANT_NAME.
I personally touch-type and hold down the Shift key for long constants; I find it faster than synchronizing my Shift keypresses with my '_' keypresses.
I have a Happy Hacking keyboard and I don't like it much. The keys feel mushy, like a cheapo $5 keyboard, and it's too minimalist for my taste. Also, the alt, fn and compose keys are way too small. My current keyboard is an IBM Model M -- yes, the one that sounds like a machine gun and weighs as much as one.
I remapped the Caps Lock key to be a Left Control, and also put Escape left of the "1" key. The old Escape key closes the current window. Now I'm in business.
There are several keys that I think should be standard on all keyboards, not just to avoid having to use combinations, but mainly to avoid having a different combination in each program (ex., some programs use Ctrl+Z for undo, others use Alt+Backspace, etc.). Here's my list:
Most of these keys could simply emulate the most common shotcuts (ex., Help = F1, Cut = Ctrl+X, etc.), so they would automatically be compatible with most existing programs.
I doubt this will happen anytime soon, though, since Microsoft is pretty much the only company with the power to dictate a "standard", and the fact that the only new keys to appear in several years are the "winkeys" shows that their idea of a "useful" key is one that has their logo on it, even if it's only used about once a month (or, in my case, not even that).
Also, one thing I'd like to see is a mouse where, instead of a scroll wheel (or two wheels), there was a mini-trackball, that could be used to scroll both vertically and horizontally. I'm surprised no-one has come up with this yet (at least I've never seen one).
RMN
~~~
I have a woman and money. Life is good.
Or in Quake : I use it mapped to the "Always Run" function.
Trolling using another account since 2005.
In your example I would use shift key because there is alot of switching between upper and lower case.
Because I so rarely use caps lock, it becomes a distraction to use. Its just so much more natural to hold shift and type "s-e-l-e-c-t" than pausing, looking down, and hitting caps lock. Yeah I know caps lock is right above shift, but I have trained myself to not accidently hit it, so I just can't naturally hit caps lock while typing .
I only caps lock when I know at the beginning of a large chunk of text that I will be using all caps.
I think this article does beg the question "When should we trade tradition for efficiency?"
D6 63 0D 70 89 81 BB 8E 7B 7C 5F 5D 54 EA AB 73
Syntax highlighting is all very well when you're writing the code in the first place, but if you're trying to debug what's going wrong with an app (for example by tailing a log of SQL commands executed) then capitalisation makes things much, much easier to quickly read and understand.
Blaming GW Bush for the Iraq war is like blaming Ronald McDonald for the poor quality of food.
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.
On my keyboard (UK) it's to the left of Z.
When I first got Linux up and running, it was using an American layout. To use backslash I had to press hash, and God knows where the hash key was mapped to, because the backslash key didn't do anything. I found myself copy and pasting from the Perl scripts I'd transported over from my parents' Windows box. Thankfully though, I only needed it in said Perl scripts. " was @ and @ was ".
Now, not only have I figured out how to change the layout, I've also managed to figure out how to stop num lock from being on when I log in. I've got nothing against the key, it's the LED that I hate.
Why is this so much easier to read
select *
from tblWhatever a
join tblYaddaYadda b
on a.ID = b.ID
where b.foo = 1
than: SELECT *
FROM tblWhatever W
JOIN tblYaddaYadda Y
ON W.ID = B.ID
WHERE Y.foo = 1
??
There are other potential problems in your SQL that unrelated to whether the reserved words are all caps or not. For instance: SELECT * can get some unexpected results. [First what table are you selecting from - not that important really, since you were just trying to show readibility.] However, even though the table of interest may have an altered structure you might not be seeing columns of interest if the stored procedure that contains this code was not refreshed after the structure change. You are using stored procedures I assume.
Another simple hint: use aliases that are more easily connected to the table name. Many of us use many more than two tables in our Joins.
For many reasons stay away from selecting everything, if you have no need for most columns. An easy way to bring your system down or locking others out if used in combination with temporary table on an older version of a backend server.
Just because you no longer have an interest in using all caps key, does not imply others do not. There are other more important problems.