For those who do not regularly read Challies, this is his blog entry from today (1/15/2015) about Logos:
http://www.challies.com/articles/should-you-make-the-move-to-logos
I have just read the article and it is a very considered and well put together article. Well worth a read.
Nice to see that he made the switch. The thoughtfulness about the requirements were very well put.
Balanced and fair review. Would be interesting to know exactly what his specs are (other than 'latest-generation iMac'). Sounds like he doesn't have an SSD, which as a few people note in the comments makes a big difference.
Sounds like he doesn't have an SSD, which as a few people note in the comments makes a big difference.
Glad to hear others coming on board with Logos. It's absolutely great.
However, I notice that Tim Challies has the same problem with Logos 6 that I have after an update (I'm using Windows 7 64x with 250GB SSD, i5 @4.4GHz, 8GB, 2GB Video):
"When that was done, I had to restart Logos again, at which point it started reindexing my library—this took about 2 hours of chewing up all of my computer’s available processing power. This entire process took about 3 hours—my entire morning dedicated to sermon-preparation was instead given to sermon-preparation-preparation. For all that Logos does, this is far and away my most consistent concern—the sheer volume of updates Logos requires and the way these updates devastate my computer while they are ongoing."
Changing the indexing process in task manager doesn't help in my case either. I need to pause indexing until I'm having a meal, or run it overnight or when I'm out. My wife is a casual user, and has this problem much more than I, since she uses it less often and has bigger updates and longer indexing each time she uses it. This deters her from using Logos 6.
It would be great to have the indexing grab far fewer system resources so that we could keep working effectively at the same time as indexing running in the background. A settings option between fast (high CPU and disk use) and slow (much lower CPU and disk use) would be great.
I only mention this as indexing has become, IMHO, a flaw in the software recently. User experience, especially for casual users, could be improved if this is resolved.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
