Dec
08
2010

#RSRH GOOGLE JUMPS THE CAPS LOCK SHARK.

THEY’VE DECIDED THAT THEIR NEW LINE OF WEB-OPTIMIZED NETBOOKS WILL NOT HAVE A CAPS LOCK KEY, BECAUSE – I QUOTE – “WE EXPECT THIS WILL IMPROVE THE QUALITY OF COMMENTS ACROSS THE WEB.”

It won’t, of course – as Gizmodo notes, this can be evaded via the trivial exercise of holding down the shift key, assuming that some aggrieved caps locker doesn’t create a mod that addresses the problem – and as Gizmodo also notes, this kind of restriction doesn’t actually fix the underlying problem.  I will add that Google’s willingness to still try to take my choices away from me pretty much confirms that it’ll be a c0ld day in Hell before I buy one of their netbooks and/or use the Chrome browser.  Because if they have a taste for restricting my behavior for the perceived sins of others on this unbelievably minor issue, then what’s keeping from trying to do it for more important things?

THAT’S RIGHT.  NOTHING.

Moe Lane

Update: Backtracking already?

PS: Yes, yes, yes: you like Google’s stance on this, so I’m being a big meanie.  Fine.

5 Comments

  • Rob Crawford says:

    Isn’t there a CSS style that changes the text to all caps?

    Ah, yes: text-transform: uppercase.

  • Phil Smith says:

    I like caps lock. It tells you at a glance who the imbeciles in the thread are. Well, one sub-group of them, anyway.

  • Jeff Weimer says:

    Google is getting more and more like Apple that way.

  • Finrod says:

    Caps Lock be damned, I just want a Ctrl key in a usable place. 99 percent of keyboards nowadays have Caps Lock where Ctrl ought to be, so I have to use xmodmap or an equivalent to make them usable.

  • countrydoc says:

    “Do no evil.” They meant you, not them. Silly peasant!

RSS feed for comments on this post.


Site by Neil Stevens | Theme by TheBuckmaker.com