<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The Light Side</title>
	<link>http://www.ficml.org/jemimap/wordpress/2005/03/01/the-light-side/</link>
	<description>Cheating on the Kobayashi Maru since 2001</description>
	<pubDate>Thu, 14 May 2026 11:05:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: Jemima</title>
		<link>http://www.ficml.org/jemimap/wordpress/2005/03/01/the-light-side/#comment-5426</link>
		<pubDate>Thu, 03 Mar 2005 05:54:25 +0000</pubDate>
		<guid>http://www.ficml.org/jemimap/wordpress/2005/03/01/the-light-side/#comment-5426</guid>
					<description>Yes, I've tried ActiveWords and I still use it on my PC at work.  AW may be more powerful in some areas, but I find that QS does more of what I want it to do:  QS navigates the filesystem intuitively; AW either doesn't do it at all, or does it so non-intuitively that I haven't figured it out in over two months (even though Windows needs navigation aid much more than the Mac does).   QS learns keyboard shortcuts on its own; AW expects me to create every shortcut.  QS is seamlessly integrated into the OS; AW is as clunky as any other Windows program (not its fault).  QS is a launcher that does what it does extremely well; AW is a whole layer of input monitoring on top of a swiss army knife of things to do with those stolen keystrokes.  Whether it does them all well I can't say, since the majority of them are things I don't want to do.

Nevertheless, I don't think of them as competing products.  AW lacks QS's core functionality (file system navigation), and QS lacks AW's core functionality (input monitoring).  I still wish I could have QS on the PC as much as your users wish for AW on the Mac.</description>
		<content:encoded><![CDATA[<p>Yes, I&#8217;ve tried ActiveWords and I still use it on my PC at work.  AW may be more powerful in some areas, but I find that QS does more of what I want it to do:  QS navigates the filesystem intuitively; AW either doesn&#8217;t do it at all, or does it so non-intuitively that I haven&#8217;t figured it out in over two months (even though Windows needs navigation aid much more than the Mac does).   QS learns keyboard shortcuts on its own; AW expects me to create every shortcut.  QS is seamlessly integrated into the OS; AW is as clunky as any other Windows program (not its fault).  QS is a launcher that does what it does extremely well; AW is a whole layer of input monitoring on top of a swiss army knife of things to do with those stolen keystrokes.  Whether it does them all well I can&#8217;t say, since the majority of them are things I don&#8217;t want to do.</p>
<p>Nevertheless, I don&#8217;t think of them as competing products.  AW lacks QS&#8217;s core functionality (file system navigation), and QS lacks AW&#8217;s core functionality (input monitoring).  I still wish I could have QS on the PC as much as your users wish for AW on the Mac.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Buzz Bruggeman</title>
		<link>http://www.ficml.org/jemimap/wordpress/2005/03/01/the-light-side/#comment-5425</link>
		<pubDate>Wed, 02 Mar 2005 21:55:51 +0000</pubDate>
		<guid>http://www.ficml.org/jemimap/wordpress/2005/03/01/the-light-side/#comment-5425</guid>
					<description>I think that we, i.e. ActiveWords, do a lot more than QS, and do it better and more intuitively. Have you tried our stuff? Find a PC, try it, and I will unlock a copy for you. I would love to find someone who was a smart Mac programmer who would port out stuff to the Mac. We get requests daily for a Mac version!</description>
		<content:encoded><![CDATA[<p>I think that we, i.e. ActiveWords, do a lot more than QS, and do it better and more intuitively. Have you tried our stuff? Find a PC, try it, and I will unlock a copy for you. I would love to find someone who was a smart Mac programmer who would port out stuff to the Mac. We get requests daily for a Mac version!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
