Logos 5 for Mac

Quick question - has Logos 5 completely finished indexing? The program can be very sluggish while indexing. You should have an icon in your menu bar that will show you when Logos is downloading and indexing.

Dear Rev. I own Accordance and Logos. Comparing the two is just futile.

Accordance is, as you say " ripping fast " and is so at everything.

Accordance is based on Apple technology , started there, grew up there and makes use of software and hardware on Macs.

Unfortunately the library is pretty limited. If you are doing primarily exegetical work, it's fine, all the tools you need. But if you look at a lot of resources, history etc, they just don't have access to those licenses.

Logos is a huge library, the Mac version is still based in Windows technologies and thus, is slower, much slower.

Large libraries take more time to go through, if in person or, by computer, just does.

The primary thing you are running into those is the bottlenecks created by the interface used to bridge between Windows code an Mac code. It is what it is.

I use Logos as my library system and Accordance as my Exegetical tools and it's a pretty happy mix that way. Hope this helps.

Yes this does help.  Thank you to all of your responses.  If this is the case, why does Logos not a true Mac version?  I don't get it?  As I said earlier as you do so my friend does also, use Accordance with Logos.  The thing is I am considering this but yet I'm not sure its worth it because I have all the exegetical tools I could ever need  on Logos5 but the speed is so, so, so annoying.  I think I'm not alone in saying I paid for the upgrade, whether it was steep or reasonable is relative according to each his own.  I already had platinum and could not afford diamond so went with Gold.  I love Logos, I like the way Accordance looks too, but Accordance seems so much more steeper in price for what you get and bibleworks is not even on radar screen.   Conditional if, but "If" Logos was not as you say based on Windows technology, and based on Apple Tech, this would be the ultimate piece.  What else would you need.  At this point I think I rather save my money for an iMac 27in at home, then purchase Accordance for exegetical purposes, then see how L5 operates on there.  If its the same outcome then I will be frustrated.  When I find myself going to google for quick word searches and getting quicker responses there then on Logos, I sort of feel like... Well enough said.  I would just like some more stability and speed.  I may be preaching to the choir.  I guess with L5 the salesmen made it seem like I was going to be in the new jerusalem.

Logos is a Mac application with, unfortunately, 'feet of clay' or, put another way, a dark secret. Meaning the user interface is a Mac application, and is coded with Mac tools but underneath, the part that interfaces with book data on disk, it uses Windows technology. And not just that, for Mac users it means to run this (ugh) Windows code there has to be an 'emulation layer' called 'Mono' running so the Windows code runs on your Mac. If you look inside the Logos 5 application (Applications | Select Logos 5 | Right click and choose 'Show Package Contents' and then navigate in Finder to Contents >> MacOS >> lib the 'dark secret' will be revealed.

Certain persons don't like me pointing this out, in fact I was made fun of by none other than the big boss a few years ago, but I think Logos should just come clean in this area and tell customers up front that that is how they have a cross platform product. This is the downside, the plus with Logos 5 being cross platform is that the installed base is much larger and therefore we get other benefits like bigger libraries.

If one understands the (cough) limitations of Logos 5 running on the Mac being held back by Windows pollution, for example also it is not a 64 bit application, even running on Mountain Lion, also, compared to other big apps like Safari & Photoshop, it seems it does not take advantage of virtual memory, and one does what is possible to get around those limitations then the performance can be reasonable.

Get a modern fast Mac with a fast processor if possible, a 2008 MacBook is holding you back. Get as much RAM as you can afford, any OS, any system and application benefits from having RAM to spare.

Many people have found running Logos on an SSD improves things as that makes accessing data off the disk much faster.

Finally we can hope and trust that Logos continues to improve Logos for Mac and to minimise the impact of having extra baggage like Mono running.

Logos is a Mac application with, unfortunately, 'feet of clay' or, put another way, a dark secret. Meaning the user interface is a Mac application, and is coded with Mac tools but underneath, the part that interfaces with book data on disk, it uses Windows technology. And not just that, for Mac users it means to run this (ugh) Windows code there has to be an 'emulation layer' called 'Mono' running so the Windows code runs on your Mac. If you look inside the Logos 5 application (Applications | Select Logos 5 | Right click and choose 'Show Package Contents' and then navigate in Finder to Contents >> MacOS >> lib the 'dark secret' will be revealed.

If one understands the (cough) limitations of Logos 5 running on the Mac being held back by Windows pollution, for example also it is not a 64 bit application, even running on Mountain Lion, also, compared to other big apps like Safari & Photoshop, it seems it does not take advantage of virtual memory, and one does what is possible to get around those limitations then the performance can be reasonable.

Get a modern fast Mac with a fast processor if possible, a 2008 MacBook is holding you back. Get as much RAM as you can afford, any OS, any system and application benefits from having RAM to spare.

Greetings, I am a Mac and iOS software developer who works for a company other than Logos.

This isn't some "Dark Secret" that has been kept from Logos users. The use of Mono in the Mac version is well known on these forums and, if I recall correctly, something that Logos has looked back on as perhaps not the best move in the world.

Nor is Mono a "emulation layer" for Windows or any kind of application. No Windows code is involved with Mono. Mono is an open-source implementation of Microsoft's .NET application framework and the C# language. It's parallels would be the old Carbon API combined with C++ or Cocoa with Obj-C.

The lack of 64-bit support is due to the lack of support in the Mono project, not because of any "Windows Pollution." Indeed, if it were actually Windows code being used, there would probably be 64-bit support already as .NET has had 64 bit support for years.

Virtual memory is not something that Mono has control of and is solely under the control of OS X. That is to say, Logos has virtual memory support because OS X has VM support.

Do not underestimate the need to share common code across platforms. There is a principal in programming called "Don't Repeat Yourself." The idea being that you only have one definitive place where data or code is expressed. By having duplicated code, you make the application more difficult to maintain and greatly increase the risk of bugs.

That being said, Logos probably would have been better off implementing the back in something other than .NET and Mono. Even with the Mono backend, I believe that Logos could be better than it is. I do no think Logos should be blamed for minimizing code duplication on a vital portion of code. Nor do I think that "Windows Pollution" is solely to blame for any Logos performance issues. And that is my professional opinion.

 I have to be honest, I am a bit disappointed that L5 is not a "true" Mac"ie" app,

I wouldn't necessarily say that any more than I would say Safari is not a "true" Mac app because most of it's code came from a Linux project. (Apple started Safari by taking the web rendering engine from the KDE web browser and putting a Mac GUI on it.)