L6 .NET translation layer for Mac

Page 1 of 1 (3 items)
This post has 2 Replies | 1 Follower

Posts 215
Tim | Forum Activity | Posted: Thu, Oct 30 2014 7:45 AM

Please forgive my flawed and less than technically accurate subject title. I'm not a developer and my language almost certainly reflects my ignorance in that realm. I seem to recall reading on the forums somewhere that much of the performance issues for Logos on Mac were related to a third party layer that was necessary for translating the .NET code that was/is the underlying framework for L4/L5 into something functional on Mac OS. The benefit of this third party software was that it allowed Faithlife to focus their development resources on more core issues, but the downside was that they simply could not improve performance significantly because of the need for translation and having to wait for updates from the third party licenser. 

Can anybody tell me if that situation has been altered or improved with L6 on Mac? Was Faithlife (ok that still sounds odd, too used to Logos!) able to utilize a more platform neutral code base? Or did they have to continue with a similar arrangement for the Mac?

Posts 8601
TCBlack | Forum Activity | Replied: Thu, Oct 30 2014 7:48 AM

L6 for mac is still developed on the Mono platform.  I'm not sure when it changed, but it is now the 64 Bit Mono.

Truth Is Still Truth Even if You Don't Believe It

Check the Wiki

Warning: Sarcasm is my love language. I may inadvertently express my love to you.

Posts 215
Tim | Forum Activity | Replied: Thu, Oct 30 2014 8:23 AM

Thank you. I thought that was likely to be the case. Wish it were otherwise, but I am pretty sure that there are lots of practical constraints they are dealing with. 

Page 1 of 1 (3 items) | RSS