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

On 07/18/2015 05:29 PM, Tom Davies wrote:

If programs plan to become cross-platform then initially writing for Linux seems to be the 
optimum route. 

If a programming team delivers a usable Linux product in one year, then
for a second platform, it will take the same team six months to deliver it.

If a programming team delivers a usable Windows product in one year,
then it will take a second team that is twice the size of the first
team, two years, to deliver the program on a different platform.

FWIW, writing to WINE/LibWINE is equivalent to writing a program for
Windows, in terms of overall productivity, and cross-platform support.

Furthermore, with WINE/LibWINE, your program won't have the same look
and feel as other software on the same platform.


  * English - detected
  * English

  * English

 <javascript:void(0);> <#>
Writing for Wine is a neat trick that i have not heard of before.  It
sounds like it neatly avoids any need for porting at all.

It also means that bug fixing is an order of magnitude more
difficult,because bug isolation requires looking at:
* your source code;
* The WINE/LibWIN library;
* The OS that the bug was reported on;

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.