Is the Logos for Mac designed and programed from the ground up to be a Mac program?
Or is it Logos for windows with a program that allows it to run on Mac?
If it is the latter, does Logos have plans for an excellent Logos designed and built for Mac?
It was originally built on Windows and then made available on Mac.
A lot of code is common - initially built on top of the .Net framework but I don't know whether any of that detail has changed.
I doubt very much if Logos would produce a separate codebase for Windows and Mac.
Was there something particularly you were hoping for? Are there issues that the current approach is causing you?
Logos for Mac is a real, native macOS application — not just the Windows version running through an emulator or compatibility layer. It reports as Kind=Apple in Activity Monitor. It's not the Windows .exe run through Wine, CrossOver, or similar compatibility layers.
They provide a dedicated Mac build that users download as a .dmg file, with versions for both Intel and Apple Silicon Macs. The Silicon versions are compiled so they run directly on those chips without emulation. So Rosetta is not needed on Apple Silicon.
I was prompted to ask this question when I quit Logos and Logos did not cleanly quit. I force quit Logos. Seems that a clean quit is hard to do. I think it should be simple to quit, but I not a programmer.
when I quit Logos and Logos did not cleanly quite
What did happen?
When I quit Logos, Logos seemed to quit, but was listed in "Force Quit" as "not responding." Often Logos will not open if I do not force quit Logos when it is "not responding"
I only have this problem with Logos now and perhaps Kindle in the past.
I often have to force-quit logos, and if I’m shutting down/rebooting, logos won’t shut down on its own.
@David Bergquist Is the Logos for Mac designed and programed from the ground up to be a Mac program?
No. The Logos desktop program is multi-platform, built on .net framework. That means it is not truly a native windows program on Windows either.
There are many things that a native Mac program can do that Logos will not. You cannot zoom text in and out using gestures on the trackpad. Logos does not utilize the application menu that native Mac programs do, that screen space is wasted unless you enter full screen mode. And the system control buttons on each window to resize/zoom/close are non-standard on Logos. They do not use the native Mac functions.
The good aspect of this is that the program works in almost identical manner on Windows and MacOS. It used to be that there was a performance penalty for using a non-compiled language relying on a runtime system that functions as a platform independent layer. but modern computers have gotten so fast that it is not really noticeable, and the runtime platform itself has been optimized for performance.
Many times Logos has an indexer running as a background process, and it might not respond immediately.
But sometimes it's just asleep. "Wake up, Verbie! Computer wants to rest!" Verbum is also my only hard-close app. Accordance just disappears.
I've occasionally had an issue with Logos becoming unresponsive and needing a Force Quit when using Courses. Most of the time, it's been stable.
@John provides the most accurate answer concerning the underpinnings of Logos for Mac.
I will say that Logos for Mac is different from Wordsearch for Mac for those who came over from Wordsearch. That was the Windows app running under WINE/CrossOver on a Mac, whereas Logos for Mac doesn't have those issues.
I did some research on the Verbum Mac app, I assume the Logos app is the same; my results:On macOS, Verbum/Logos is not a purely native macOS application, nor is it simply the Windows app running under emulation, and it does not use Microsoft’s Windows .NET Framework on the Mac. Direct examination of the installed application shows that it ships with hundreds of managed .NET assemblies (*.dll) and that the macOS executable links against MonoHost.framework, indicating that the application runs a shared .NET/C# codebase hosted via Mono on macOS, with native macOS components handling application hosting and OS integration.
I did some research on the Verbum Mac app, I assume the Logos app is the same; my results:
On macOS, Verbum/Logos is not a purely native macOS application, nor is it simply the Windows app running under emulation, and it does not use Microsoft’s Windows .NET Framework on the Mac. Direct examination of the installed application shows that it ships with hundreds of managed .NET assemblies (*.dll) and that the macOS executable links against MonoHost.framework, indicating that the application runs a shared .NET/C# codebase hosted via Mono on macOS, with native macOS components handling application hosting and OS integration.
In short, Logos/Verbum uses a common managed core across Windows and macOS (Windows on Microsoft .NET, macOS on Mono), rather than maintaining two entirely separate native implementations or relying on Windows compatibility layers. This conclusion comes from inspecting the app bundle and executable with a tool available under MacOS (otool -L, bundle contents). I can provide the exact command output and file paths if anyone would like to see the supporting details.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
i'm on the fence about the pretrib rapture. everyone i know is convinced but i'm not so sure
when i click on the "copy to Microsoft Word" link in the expository sermon prep guide, i get a drop down menu. at this point i click on the Microsoft word choice. Nothing happens. It seems that somehow i must have a setting somewhere that links the 2 applications but i cannot find it
When I have the NA28 and English bible linked. Over a study time, when I bring the mouse over the Greek word to see its morphology. For example Mouse overs over eisin and it automatically parses it. Great tool. However, Over time, say 30 mins, the software slows down and when I attempt the same process, logos seems to…
how do I cast my cares and worries upon the Lord.
Which e-ink devices work with Logos? Will Onyx Boox Go 10.3 work?
