- air
- ajax
- algorithm
- apple
- bitbucket
- braintapper_exchange
- charts
- chumby
- codeigniter
- cognos
- complexity
- crashplan
- crosstab
- dash
- dashboard
- date
- dbvisualizer
- decisions
- dimension
- dogfood
- dona_wong
- dropbox
- edward_tufte
- extension
- feature_checklists
- feature_excellence
- filemaker
- firefox
- firewall
- flot
- flowing_data
- fogbugz
- football
- free
- freenas
- freshbooks
- git
- github
- gm
- google_charts
- iPad
- javascript
- jdbc
- jedox
- mac
- macbook
- maps
- marsedit
- mercurial
- metaweblog
- metrics
- microstrategy
- monowall
- moo
- nathan_yau
- news
- nosql
- open_source
- palo
- pentaho
- pfsense
- printing
- programmers_interfaces
- rapidweaver
- regex
- regexr
- rest
- safari
- smoothwall
- sony
- sqlpower
- stackoverflow
- statistics
- stephen_few
- svg
- tablet
- ticket_agent
- time_machine
- tip
- tm1
- transformer
- trick
- typographic grid
- usability
- visualization
- vmware
- w3c
- web
- wiki
- wikkawiki
- work_management
- wsj
In the most recent version of VMWare Fusion for the Mac, they've decided to go with an interesting choice of words for suspending, restarting and shutting down. They've prefixed the action phrases in the menu with the word "Force". So, you end up with "Force Suspend", "Force Resume", "Force Restart" and "Force Shutdown".
To my eye, the use of the word "Force" seems a little too strong, especially in the context of Macintosh UI's. For example, in the OSX Activity Monitor (equivalent to Windows Task Manager), you can "politely" ask an app to Quit, or if it has hung, Force Quit. Notice the distinction?
I don't really see that the use of the word Force in the menu options in Fusion is necessary, and subconsciously, it seems to imply a shaky sense of reliability, even though that is hardly the case.
