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


On 4/17/19 9:11 PM, Roland Hummel wrote:

"Yes, LO is nice but it won't beat MS Office because in MSO we will have artificial intelligence".

If the battlefield is functionality, and AI is important,in 2018, the
five most important AI programming languages were:
* Python;
* LISP;
* C++;
* Java;
* Prolog;

Two (Three? I'm not sure about C++) are built-in macro languages. LISP
and Prolog are easy enough to add.

There is documentation on installing and using R as a macro language.

Which underscores that the big issue in the functionality war, is not
what is available, but rather, the knowledge that the features are
available, and how to use them.

_TL;DR: Documentation, not implementation._

I'm not sure why being able to grab LinkedIn resumes from within Excel
is a good thing, but that is the type of functionality that Microsoft is
adding. IMNSHO, this type of functionality is best provided by extension
developers.

End users can more easily customize LibO, than MSO, etc.

base of any argumentation because it is the only superior starting position LO has.

For most organizations, ethics is nothing more than a feel-good talking
point. Something that is neither implemented, nor observed.
As such, appeals based on ethical principles fall upon deaf ears.

Starting from software freedom any further argumentation will convince (at least in societies 
claiming freedom as fundamental part of a society):
-because LO is freedom respecting it is secure
-because LO is freedom respecting it is privacy respecting
-because LO is freedom respecting it serves the user
-because LO is freedom respecting it is sustainable

Neither people nor organizations are concerned about those things, until
they discover that their data has been passed on to nefarious third
parties, by their software vendor.

A white paper showing how LibO meets requirements for various privacy
related legislation might be useful here.

Whilst such a paper might make LibreOffice Cloud Edition look bad, the
quasi-redeeming feature is that the user can control the cloud that it
is installed on.

In this way LO will convince governments, companies, the educational sector and NGOs, 

The question to be addressed here, is "Who can be sued, if things go
wrong?"

Whilst Microsoft's _Terms and Conditions_ claim no liability, that
doesn't prevent support companies from being sued, when things go wrong.

This is where a lawyer is needed, to explain either who could
sucessfully be sued, if LibO goes wrong, or why such a lawsuit would not
be filable in the first place.

not by trying to convince users in a perspective that is already totally lost to the proprietary 
sector ("functionality" 

The functionality issue will be over, when you can pick up _LibreOffice
For Managing you Futures Portfolio: Shorts, Straddles, Puts, and
Candlesticks_ at your local Office Depot, or _Asteroid Hunting using
LibreOffice_ at your local _Books a Million_.

(I've only slightly changed the titles of books about Excel, that I've
seen in bookstores.)

aka "but MS Office is so easy to use").

Familiarity, not ease of use.

jonathon







-- 
To unsubscribe e-mail to: marketing+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/marketing/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


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.