Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index

On April 21, 2014 1:55:21 PM PDT, Girvin Herr wrote:
back then, it seemed that the wine devs were focused on getting proprietary games working, not 
apps such as ms Access.  

In defence of the Wine developers, the focus onproprietary games was due to two factors:
* That is what people were wanting to use WINE for;
* For various reasons, making Wine compatible with those games, made Wine compatibe with more 
non-targetted software, than focussing specifically on MSO, or other business-orientated software 
would make it.

In the last four or so years, the WINE developers have tried to keep WINE compatible with the 
current version of MSO, as well as all the old versions, and all of the proprietary games.  This 
task has not been easy, and compatibility has broken in both targetted and non-targetted software 

'Tis better to go native than to emulate.  

Whilst that is true, in too many instances, not only are there are no viable FLOSS substitutes, but 
the odds of a viable substitute appearing are on a par with  the Chicago Cubs winning the Stanley 

rudeness factor

The closer the software is to being an abstraction that end users may not touch, the ruder the 
developer list, and user-support list is.


Your documents, your language, your way.

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.