<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Logos</title>
	<atom:link href="http://www.rueplumet.com/2007/02/03/logos/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rueplumet.com/2007/02/03/logos/</link>
	<description></description>
	<pubDate>Wed, 07 Jan 2009 20:29:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brad</title>
		<link>http://www.rueplumet.com/2007/02/03/logos/comment-page-1/#comment-11308</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Sun, 11 Feb 2007 20:46:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.rueplumet.com/2005/10/24/logos/#comment-11308</guid>
		<description>Daniel,
Answering that question just reminds me how happy I am that I can have both products on my machine! To me, the very best thing about Logos is the incredibly deep linking. For example, when I'm reading an entry in BDAG, for many of the Greek grammar references (such as BDF) I can just hover or click on the link and read the corresponding information in the grammar (for the non-Logos people out there, that's because I also own licenses for a bunch of the standard Greek grammars). That's an awesome capability! I also like how the Logos version of BDAG has hover spots for the vast majority of abbreviations used in the definitions. Those are super handy when I can't quite remember what a particular abbreviation is (because BDAG uses LOTS of them).

And I know Logos will love this little piece of advertisement, but the more resources I buy, the better using Logos becomes because more and more links become "live". I bought BDAG as one of my earlier purchases in Logos, and then when I bought a couple of Greek grammars later on, not only did I get some great new reference material, but it even made BDAG better because of the new links that became available. It's really quite addicting. :-)

Now BibleWorks doesn't have all of the linking that Logos does. Even though I have some of the same grammars in BibleWorks, I have to go manually look up the information when I see a reference in BDAG because there is no live link. That's why I was so glad to discover Logos as an additional tool to have on my machine. Once you've purchased a good set of standard references, the linking in Logos is truly amazing.

As another plus for Logos (and as implied in my original post), there are quite a few books and commentary sets that I really appreciate having in electronic format that are simply not available in BibleWorks. I don't think that is a "fault" of BibleWorks exactly, because it is clearly not the market they are going after, but I do enjoy having them available in Logos.

However, there are two things I really like about BibleWorks that Logos does not have. First, I really like the 3-pane layout in BibleWorks: search, Bible passage, and then information about the passage or individual words in the passage. That just makes sense to me and it is really easy to use. I haven't been able to recreate a workspace in Logos that does the same thing for me. Now, to be fair, I used BibleWorks for years before I ever got a copy of Logos, so perhaps my familiarity with that interface makes me like it more. But the interface really does work well.

The other thing I love about BibleWorks is that it is incredibly fast at almost everything it does. Generally when I am working in BibleWorks I feel like I can do almost anything I need to do almost instantly. And even though 3.0 is a *huge* improvement over previous versions, Logos is still considerably slower. And I don't think that's because of my machine. I have a dual core processor, 4 gigs of RAM, SATA 3.0 Gb/s NCQ hard drives in a raid setup, and I'm running XP Pro. The machine is plenty fast, but there are still a lot of things in Logos that just take a long time to run. BibleWorks being crazy fast is the reason I almost always open it first to do my primary work, then open Logos later to do further analysis. If Logos ran as fast as BibleWorks, that would go a long way towards changing my opinion between the two. I have no idea how BibleWorks gets everything to run so fast. Perhaps they just keep enormous index files on disk whereas Logos builds the equivalent information on the fly when you try to do a search? I really have no idea, but the difference between the two is pretty clear.</description>
		<content:encoded><![CDATA[<p>Daniel,<br />
Answering that question just reminds me how happy I am that I can have both products on my machine! To me, the very best thing about Logos is the incredibly deep linking. For example, when I&#8217;m reading an entry in BDAG, for many of the Greek grammar references (such as BDF) I can just hover or click on the link and read the corresponding information in the grammar (for the non-Logos people out there, that&#8217;s because I also own licenses for a bunch of the standard Greek grammars). That&#8217;s an awesome capability! I also like how the Logos version of BDAG has hover spots for the vast majority of abbreviations used in the definitions. Those are super handy when I can&#8217;t quite remember what a particular abbreviation is (because BDAG uses LOTS of them).</p>
<p>And I know Logos will love this little piece of advertisement, but the more resources I buy, the better using Logos becomes because more and more links become &#8220;live&#8221;. I bought BDAG as one of my earlier purchases in Logos, and then when I bought a couple of Greek grammars later on, not only did I get some great new reference material, but it even made BDAG better because of the new links that became available. It&#8217;s really quite addicting. :-)</p>
<p>Now BibleWorks doesn&#8217;t have all of the linking that Logos does. Even though I have some of the same grammars in BibleWorks, I have to go manually look up the information when I see a reference in BDAG because there is no live link. That&#8217;s why I was so glad to discover Logos as an additional tool to have on my machine. Once you&#8217;ve purchased a good set of standard references, the linking in Logos is truly amazing.</p>
<p>As another plus for Logos (and as implied in my original post), there are quite a few books and commentary sets that I really appreciate having in electronic format that are simply not available in BibleWorks. I don&#8217;t think that is a &#8220;fault&#8221; of BibleWorks exactly, because it is clearly not the market they are going after, but I do enjoy having them available in Logos.</p>
<p>However, there are two things I really like about BibleWorks that Logos does not have. First, I really like the 3-pane layout in BibleWorks: search, Bible passage, and then information about the passage or individual words in the passage. That just makes sense to me and it is really easy to use. I haven&#8217;t been able to recreate a workspace in Logos that does the same thing for me. Now, to be fair, I used BibleWorks for years before I ever got a copy of Logos, so perhaps my familiarity with that interface makes me like it more. But the interface really does work well.</p>
<p>The other thing I love about BibleWorks is that it is incredibly fast at almost everything it does. Generally when I am working in BibleWorks I feel like I can do almost anything I need to do almost instantly. And even though 3.0 is a *huge* improvement over previous versions, Logos is still considerably slower. And I don&#8217;t think that&#8217;s because of my machine. I have a dual core processor, 4 gigs of RAM, SATA 3.0 Gb/s NCQ hard drives in a raid setup, and I&#8217;m running XP Pro. The machine is plenty fast, but there are still a lot of things in Logos that just take a long time to run. BibleWorks being crazy fast is the reason I almost always open it first to do my primary work, then open Logos later to do further analysis. If Logos ran as fast as BibleWorks, that would go a long way towards changing my opinion between the two. I have no idea how BibleWorks gets everything to run so fast. Perhaps they just keep enormous index files on disk whereas Logos builds the equivalent information on the fly when you try to do a search? I really have no idea, but the difference between the two is pretty clear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Foster</title>
		<link>http://www.rueplumet.com/2007/02/03/logos/comment-page-1/#comment-11203</link>
		<dc:creator>Daniel Foster</dc:creator>
		<pubDate>Fri, 09 Feb 2007 17:51:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.rueplumet.com/2005/10/24/logos/#comment-11203</guid>
		<description>Glad you found a system that works for you, Brad. We strive to make &lt;a href="http://www.logos.com" rel="nofollow"&gt;Logos Bible Software&lt;/a&gt; a one-stop platform for language study and theological study...but at the same time realize that not everyone uses it that way, and that's okay.

I'd be interested in your thoughts comparing the functionality and utility of works like BDAG and HALOT in the two platforms. Are there things you like better about the implementation of, say, BDAG on either platform?

Daniel Foster
Logos Bible Software</description>
		<content:encoded><![CDATA[<p>Glad you found a system that works for you, Brad. We strive to make <a href="http://www.logos.com" rel="nofollow">Logos Bible Software</a> a one-stop platform for language study and theological study&#8230;but at the same time realize that not everyone uses it that way, and that&#8217;s okay.</p>
<p>I&#8217;d be interested in your thoughts comparing the functionality and utility of works like BDAG and HALOT in the two platforms. Are there things you like better about the implementation of, say, BDAG on either platform?</p>
<p>Daniel Foster<br />
Logos Bible Software</p>
]]></content:encoded>
	</item>
</channel>
</rss>
