Re: [tdf-discuss] Re: Why LO mobile version should not be ignored

2010-11-19 Thread Ian Lynch
On 18 November 2010 23:05, Harold Fuchs hwfa.libreoff...@gmail.com wrote:

 On 18/11/2010 19:39, Ian Lynch wrote:

 On 18 November 2010 14:27, Florian Reisingerreisi...@live.at  wrote:


  Has anyone in authority asked the PortableApps folk if they'd do a
 portable LibO? Can't hurt to ask ...

 Has anyone in authority asked the Android and/or Apple and/or Symbian

 folk

 if they'd do a mobile LibO? Can't hurt to ask ...

 snip

 --
 Harold Fuchs
 London, England



 That would be a great idea.
 --
 Unsubscribe instructions: Email to 
 discuss+h...@documentfoundation.orgdiscuss%2bh...@documentfoundation.org
 discuss%2bh...@documentfoundation.orgdiscuss%252bh...@documentfoundation.org
 

 Posting guidelines: http://netmeister.org/news/learn2quote.html
 Archive: http://www.documentfoundation.org/lists/discuss/
 *** All posts to this list are publicly archived ***

 I'd be surprised if Google hadn't already thought about it and so they

 probably rejected it. After all they already have Google Docs and my
 Android
 phone has ThinkFree Office. Symbian is using K-office. The barrier of the
 size of LO is a significant issue. If it is slimmed and phones get more
 powerful it can happen but the longer that takes the moore likely it will
 be
 that it is too late :-(. Even a light weight WP based on Writer from a
 workflow point of view and supporting odf would be better than nothing.
 90%
 of people simply don't need all the functions for the things they do most
 often and this likely what they would do on phone technology.


 Your comment about the size of LibO is highly relevant. I've been amazed
 ever since I first encountered OOo that it isn't in separately installable
 modules. Perhaps, if it is to make significant inroads into the developing
 markets, it needs a complete re-design to conform to the Unix philosophy of
 making small tools that each do one job well but can be easily combined.

 ThinkFree seems do do MS Office format only :-( It seems to be able to
 handle doc, xls etc. but *not* docx, xlsx etc.

 K-Office seems to be able to handle ODF.

 Perhaps LibO is too late for the mobile market, which would be a shame, but
 I still think a *portable* version would be an excellent seller.

 --
 Harold Fuchs
 London, England


Really it's down to the Star Office heritage. Star Office originated at a
time when megalithic apps were the in thing. (at least with MSFT) You can
see why. Ever increasing size forces people to upgrade their hardware. New
computer new Windows sale. There was absolutely no incentive to do things
differently. Of course the developers of Star Office didn't have to do it
that way but they probably thought this is the model that is accepted by end
users so we have to have highly integrated to compete. Once it is in the
millions of lines of code it is very difficult to get off that treadmlll.
Personally I'd rather have seen the engineering effort going first for
efficiency with a set of features good enough for 90% of the market starting
10 years ago but we can't turn the clock back. And of course there is the
argument that without certain features some of the large public sector
switches might not have happened.

-- 
Ian

Ofqual Accredited IT Qualifications
The Schools ITQwww.theINGOTs.org +44 (0)1827 305940

You have received this email from the following company: The Learning
Machine Limited, Reg Office, 36 Ashby Road, Tamworth, Staffordshire, B79
8AQ. Reg No: 05560797, Registered in England and Wales.

-- 
Unsubscribe instructions: Email to discuss+h...@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***



Re: [tdf-discuss] Re: Why LO mobile version should not be ignored

2010-11-19 Thread Phil Hibbs
Ian Lynch:
 And of course there is the
 argument that without certain features some of the large public sector
 switches might not have happened.

Back in my teens, my dad and I wrote a Basic interpreter for the PC
based on the Acorn BBC Micro dialect. We went to a computer show, and
I lost count of the number of people who just asked Is it 100%
compatible?, and when I said no, but..., they just laughed and
walked off. It's a hard barrier to break through - there are plenty of
people who will say It doesn't have feature X therefore we'll stick
with Microsoft. Sometimes it's features that can be worked around,
such as only allowing one AutoFilter in a workbook, but someone will
use that as an excuse for declaring a show-stop.

Phil.
-- 
Don't you just hate self-referential sigs?

-- 
Unsubscribe instructions: Email to discuss+h...@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***



Re: [tdf-discuss] Re: Why LO mobile version should not be ignored

2010-11-19 Thread Ian Lynch
On 19 November 2010 15:11, Phil Hibbs sna...@gmail.com wrote:

 Ian Lynch:
  And of course there is the
  argument that without certain features some of the large public sector
  switches might not have happened.

 Back in my teens, my dad and I wrote a Basic interpreter for the PC
 based on the Acorn BBC Micro dialect. We went to a computer show, and
 I lost count of the number of people who just asked Is it 100%
 compatible?, and when I said no, but..., they just laughed and
 walked off. It's a hard barrier to break through - there are plenty of
 people who will say It doesn't have feature X therefore we'll stick
 with Microsoft. Sometimes it's features that can be worked around,
 such as only allowing one AutoFilter in a workbook, but someone will
 use that as an excuse for declaring a show-stop.


Thing we don't really know is whether a very efficient and compact version
of Writer that supported excellent filters for all the commonly used things
like tables, headings etc  and worked in a cell phone would outweigh
anything missing. After all the versions of MS Office for handhelds is only
a subset of the full MS Office. In phones it is not the same barrier as in
PCs,


 Phil.
 --
 Don't you just hate self-referential sigs?

 --
 Unsubscribe instructions: Email to 
 discuss+h...@documentfoundation.orgdiscuss%2bh...@documentfoundation.org
 Posting guidelines: http://netmeister.org/news/learn2quote.html
 Archive: http://www.documentfoundation.org/lists/discuss/
 *** All posts to this list are publicly archived ***




-- 
Ian

Ofqual Accredited IT Qualifications
The Schools ITQwww.theINGOTs.org +44 (0)1827 305940

You have received this email from the following company: The Learning
Machine Limited, Reg Office, 36 Ashby Road, Tamworth, Staffordshire, B79
8AQ. Reg No: 05560797, Registered in England and Wales.

-- 
Unsubscribe instructions: Email to discuss+h...@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***



Re: [tdf-discuss] Re: Why LO mobile version should not be ignored

2010-11-18 Thread Alexandro Colorado
On Thu, 18 Nov 2010 17:05:03 -0600, Harold Fuchs  
hwfa.libreoff...@gmail.com wrote:



On 18/11/2010 19:39, Ian Lynch wrote:

On 18 November 2010 14:27, Florian Reisingerreisi...@live.at  wrote:




Has anyone in authority asked the PortableApps folk if they'd do a
portable LibO? Can't hurt to ask ...

Has anyone in authority asked the Android and/or Apple and/or  
Symbian

folk

if they'd do a mobile LibO? Can't hurt to ask ...

snip

--
Harold Fuchs
London, England



That would be a great idea.
--
Unsubscribe instructions: Email to  
discuss+h...@documentfoundation.orgdiscuss%2bh...@documentfoundation.org

Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***

I'd be surprised if Google hadn't already thought about it and so they
probably rejected it. After all they already have Google Docs and my  
Android
phone has ThinkFree Office. Symbian is using K-office. The barrier of  
the

size of LO is a significant issue. If it is slimmed and phones get more
powerful it can happen but the longer that takes the moore likely it  
will be

that it is too late :-(. Even a light weight WP based on Writer from a
workflow point of view and supporting odf would be better than nothing.  
90%
of people simply don't need all the functions for the things they do  
most

often and this likely what they would do on phone technology.


Your comment about the size of LibO is highly relevant. I've been amazed  
ever since I first encountered OOo that it isn't in separately  
installable modules. Perhaps, if it is to make significant inroads into  
the developing markets, it needs a complete re-design to conform to the  
Unix philosophy of making small tools that each do one job well but can  
be easily combined.


OOo is in different modules, but is a bit irrelevant since the core still  
ocuppies 90% of the overal size.
When you install in linux you  are faced with a folder with up to 17  
different rpm packages. Also a distro will upgrade on different package  
set. Then again the same is true if you want a KDE app, the core libs will  
take a very large and pulverized ammount of packages.


ThinkFree seems do do MS Office format only :-( It seems to be able to  
handle doc, xls etc. but *not* docx, xlsx etc.


Google Docs do ODF there is a whole list of apps that handle ODF. This is  
more of an ODF conversation but the level of adoption is very big now.


Check this graph:  
http://216.220.37.188/uploadedImages/About_Adlib/Adlib_Software_Blog/http---www.odfalliance.org-resources-ODF5yr_050110.pdf%20-%20Adobe%20Reader.jpg




K-Office seems to be able to handle ODF.

Perhaps LibO is too late for the mobile market, which would be a shame,  
but I still think a *portable* version would be an excellent seller.




LibO is already being targeted to be bundled with the WeTab which is a  
meego driven app. I think mobile development will soon reach the computer  
specs faster than developing for a mobile specs. There are remote desktop  
solutions to manage apps from your mobile as well. Mobile custom OS don't  
allow new toolkits like the one of OOo/LibO which makes it practically  
impossible to port. As opposed to open OS that allow you to just compile  
the new toolkit for it.


Android might allow our toolkit but the lack of support of big  
dependencies like X11 might make it hard to compile for it.


Open mobile platforms like Meego/maemo might have a better choice for the  
port.


--
Alexandro Colorado

--
Unsubscribe instructions: Email to discuss+h...@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***



[tdf-discuss] Re: Why LO mobile version should not be ignored

2010-11-17 Thread Harold Fuchs

On 17/11/2010 18:22, jonathon wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/17/2010 04:25 PM, Mirek M. wrote:


I'd say that a web app should have higher priority here,


This should be an independent project.

In an ideal world, the code would be modular and clearly commented, so
that any developer could pick up  various pieces, either to port it to a
new platform/OS, or to refine them a specialized function.


web apps work on all platforms with a modern browser


The Internet is not always available.  And where it is available, it is
not always cheap.
[ The data plan for my smartphone costs double that of my cable
connection, but only offers 1/10,000 of the data transfer that my cable
connection offers. Data transfer surcharges can reach US$1.00 per
kilobyte.  (Data transfer, not data speed.) ]


an open-source web app has many more possible uses than a desktop app;


The number of potential users is meaningless. What counts is the number
of people that can, and will use it.


the mobile OS market is still pretty unstable: there's no clear

platform to develop for.

If you are waiting for a clear platform to develop for, you will wait
forever.

At best, there will be three dominant platforms for mobile devices, and
three dominant platforms for desktop devices, and three dominant
platforms for gaming consoles, for a total of ten different platforms to
code for.

The worst case scenario is that there will be five dominant mobile
device platforms, with another five dominant desktop platforms with
another five dominant gaming consoles, for a total of sixteen different
platforms to code for.

In either instance, you are looking at between twenty and thirty
different platforms, in order to support user-expectations, in terms of
cross-platform availability.


all the other mobile operating systems haven't yet reached the level of

marketshare that iOS and Android have.

2010 2Q Marketshare
Symbian: 41.2%
RIM: 18.2%
Android: 17.2%
iOS: 14.2%
WinMO: 5%
Linux: 2.4%
Other: 1.8%

Source: http://www.gartner.com/it/page.jsp?id=1421013 (August 2010)

To call Android and iOS marketshare leaders, when they are more than
twenty percentage points behind the OS with the highest market
penetration reveals a lack of knowledge of mobile device marketshare.

Compared to 2009 2Q the marketshare is not there either:
Symbian: 51.0%
RIM: 19.0%
iOS: 13.0%
WinMo: 9.3%
Linux: 4.6%
Android: 1.8%
Other: 1.2%

* Symbian will probably retain first position, but it won't have the
thirty percentage point advantage in marketshare that it used to have;
* Due to manufacturing issues, iOS won't get above 20% --- if it can
even get that high;
* Android will flatten out at between 20% and 25%.
* Assuming RIM can satisfy the voyeurism that afflicts government
agencies, it should hold steady at between 15% and 20%.
* The other platforms will be holding their breath, wondering if their
oxygen supply will extinguish them;

jonathon


I think there's another consideration here: security.

What guarantees do cloud service operators give about the security of 
any document I may store on its server? What prevents the operator's 
employees or ex-employees accessing my documents? What prevents drive-by 
hackers accessing my documents? What prevents someone targetting me 
accessing my documents? What prevents someone targetting the service 
provider accessing my documents? Can I set passwords on my documents? I 
suppose I could encrypt my document but most people probably don't have 
this technology readily available (see below).


What guarantees do cloud service operators give about the backing-up and 
subsequent recovery of any document I may store on its server?


What guarantees do cloud service operators give about the availability 
of any document I may store on its server?


A large part of the point of a portable app is that I can put the whole 
kit and caboodle on an encrypted device if I want. Even without going to 
such lengths, the security, availability and back-up/recovery is up to 
me, not up to some unknown company whose procedures I cannot trust 
(based on fairly recent history in many cases) whatever its policies may 
say.


In several cases, storing documents on a server outside the owner's 
country (or geographic region) could well be illegal.


I'm not at all convinced that people and, more particularly, 
corporations, have really analysed the implications of web apps and 
cloud computing. When they do I don't think web apps will prove all that 
popular.


Call me a Luddite if you like but ...


--
Harold Fuchs
London, England


--
Unsubscribe instructions: Email to discuss+h...@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***



[tdf-discuss] Re: Why LO mobile version should not be ignored

2010-11-17 Thread Harold Fuchs

On 17/11/2010 18:54, Harold Fuchs wrote:

On 17/11/2010 18:22, jonathon wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/17/2010 04:25 PM, Mirek M. wrote:


I'd say that a web app should have higher priority here,


This should be an independent project.

In an ideal world, the code would be modular and clearly commented, so
that any developer could pick up various pieces, either to port it to a
new platform/OS, or to refine them a specialized function.


web apps work on all platforms with a modern browser


The Internet is not always available. And where it is available, it is
not always cheap.
[ The data plan for my smartphone costs double that of my cable
connection, but only offers 1/10,000 of the data transfer that my cable
connection offers. Data transfer surcharges can reach US$1.00 per
kilobyte. (Data transfer, not data speed.) ]


an open-source web app has many more possible uses than a desktop app;


The number of potential users is meaningless. What counts is the number
of people that can, and will use it.


the mobile OS market is still pretty unstable: there's no clear

platform to develop for.

If you are waiting for a clear platform to develop for, you will wait
forever.

At best, there will be three dominant platforms for mobile devices, and
three dominant platforms for desktop devices, and three dominant
platforms for gaming consoles, for a total of ten different platforms to
code for.

The worst case scenario is that there will be five dominant mobile
device platforms, with another five dominant desktop platforms with
another five dominant gaming consoles, for a total of sixteen different
platforms to code for.

In either instance, you are looking at between twenty and thirty
different platforms, in order to support user-expectations, in terms of
cross-platform availability.


all the other mobile operating systems haven't yet reached the level of

marketshare that iOS and Android have.

2010 2Q Marketshare
Symbian: 41.2%
RIM: 18.2%
Android: 17.2%
iOS: 14.2%
WinMO: 5%
Linux: 2.4%
Other: 1.8%

Source: http://www.gartner.com/it/page.jsp?id=1421013 (August 2010)

To call Android and iOS marketshare leaders, when they are more than
twenty percentage points behind the OS with the highest market
penetration reveals a lack of knowledge of mobile device marketshare.

Compared to 2009 2Q the marketshare is not there either:
Symbian: 51.0%
RIM: 19.0%
iOS: 13.0%
WinMo: 9.3%
Linux: 4.6%
Android: 1.8%
Other: 1.2%

* Symbian will probably retain first position, but it won't have the
thirty percentage point advantage in marketshare that it used to have;
* Due to manufacturing issues, iOS won't get above 20% --- if it can
even get that high;
* Android will flatten out at between 20% and 25%.
* Assuming RIM can satisfy the voyeurism that afflicts government
agencies, it should hold steady at between 15% and 20%.
* The other platforms will be holding their breath, wondering if their
oxygen supply will extinguish them;

jonathon


I think there's another consideration here: security.

What guarantees do cloud service operators give about the security of
any document I may store on its server? What prevents the operator's
employees or ex-employees accessing my documents? What prevents drive-by
hackers accessing my documents? What prevents someone targetting me
accessing my documents? What prevents someone targetting the service
provider accessing my documents? Can I set passwords on my documents? I
suppose I could encrypt my document but most people probably don't have
this technology readily available (see below).

What guarantees do cloud service operators give about the backing-up and
subsequent recovery of any document I may store on its server?

What guarantees do cloud service operators give about the availability
of any document I may store on its server?

A large part of the point of a portable app is that I can put the whole
kit and caboodle on an encrypted device if I want. Even without going to
such lengths, the security, availability and back-up/recovery is up to
me, not up to some unknown company whose procedures I cannot trust
(based on fairly recent history in many cases) whatever its policies may
say.

In several cases, storing documents on a server outside the owner's
country (or geographic region) could well be illegal.

I'm not at all convinced that people and, more particularly,
corporations, have really analysed the implications of web apps and
cloud computing. When they do I don't think web apps will prove all that
popular.

Call me a Luddite if you like but ...




Sorry to reply to my own post but there's something I forgot:

What guarantees do I get that a document I prepare today will be 
properly processable by the web app provider's software tomorrow? Do I 
have any control over the version of the software I use?


--
Harold Fuchs
London, England


--
Unsubscribe instructions: Email to discuss+h...@documentfoundation.org
Posting guidelines: 

Re: [tdf-discuss] Re: Why LO mobile version should not be ignored

2010-11-17 Thread Mirek M.
2010/11/17 Harold Fuchs hwfa.libreoff...@gmail.com

 On 17/11/2010 18:54, Harold Fuchs wrote:

 On 17/11/2010 18:22, jonathon wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 11/17/2010 04:25 PM, Mirek M. wrote:

  I'd say that a web app should have higher priority here,


 This should be an independent project.

 In an ideal world, the code would be modular and clearly commented, so
 that any developer could pick up various pieces, either to port it to a
 new platform/OS, or to refine them a specialized function.

  web apps work on all platforms with a modern browser


 The Internet is not always available. And where it is available, it is
 not always cheap.
 [ The data plan for my smartphone costs double that of my cable
 connection, but only offers 1/10,000 of the data transfer that my cable
 connection offers. Data transfer surcharges can reach US$1.00 per
 kilobyte. (Data transfer, not data speed.) ]

  an open-source web app has many more possible uses than a desktop app;


 The number of potential users is meaningless. What counts is the number
 of people that can, and will use it.

  the mobile OS market is still pretty unstable: there's no clear

 platform to develop for.

 If you are waiting for a clear platform to develop for, you will wait
 forever.

 At best, there will be three dominant platforms for mobile devices, and
 three dominant platforms for desktop devices, and three dominant
 platforms for gaming consoles, for a total of ten different platforms to
 code for.

 The worst case scenario is that there will be five dominant mobile
 device platforms, with another five dominant desktop platforms with
 another five dominant gaming consoles, for a total of sixteen different
 platforms to code for.

 In either instance, you are looking at between twenty and thirty
 different platforms, in order to support user-expectations, in terms of
 cross-platform availability.

  all the other mobile operating systems haven't yet reached the level of

 marketshare that iOS and Android have.

 2010 2Q Marketshare
 Symbian: 41.2%
 RIM: 18.2%
 Android: 17.2%
 iOS: 14.2%
 WinMO: 5%
 Linux: 2.4%
 Other: 1.8%

 Source: http://www.gartner.com/it/page.jsp?id=1421013 (August 2010)

 To call Android and iOS marketshare leaders, when they are more than
 twenty percentage points behind the OS with the highest market
 penetration reveals a lack of knowledge of mobile device marketshare.

 Compared to 2009 2Q the marketshare is not there either:
 Symbian: 51.0%
 RIM: 19.0%
 iOS: 13.0%
 WinMo: 9.3%
 Linux: 4.6%
 Android: 1.8%
 Other: 1.2%

 * Symbian will probably retain first position, but it won't have the
 thirty percentage point advantage in marketshare that it used to have;
 * Due to manufacturing issues, iOS won't get above 20% --- if it can
 even get that high;
 * Android will flatten out at between 20% and 25%.
 * Assuming RIM can satisfy the voyeurism that afflicts government
 agencies, it should hold steady at between 15% and 20%.
 * The other platforms will be holding their breath, wondering if their
 oxygen supply will extinguish them;

 jonathon


 I think there's another consideration here: security.

 What guarantees do cloud service operators give about the security of
 any document I may store on its server? What prevents the operator's
 employees or ex-employees accessing my documents? What prevents drive-by
 hackers accessing my documents? What prevents someone targetting me
 accessing my documents? What prevents someone targetting the service
 provider accessing my documents? Can I set passwords on my documents? I
 suppose I could encrypt my document but most people probably don't have
 this technology readily available (see below).

 What guarantees do cloud service operators give about the backing-up and
 subsequent recovery of any document I may store on its server?

 What guarantees do cloud service operators give about the availability
 of any document I may store on its server?



 A large part of the point of a portable app is that I can put the whole
 kit and caboodle on an encrypted device if I want. Even without going to
 such lengths, the security, availability and back-up/recovery is up to
 me, not up to some unknown company whose procedures I cannot trust
 (based on fairly recent history in many cases) whatever its policies may
 say.


I agree -- security is definitely an issue. But it's always going to be an
issue, with everything that's online. There's always going to be a host that
has access to everything you upload.

However, with an open-source web app, you get the options of:
a) hosting the web app yourself, so that no third party has control over
your files
b) downloading the web app and running it offline


 In several cases, storing documents on a server outside the owner's
 country (or geographic region) could well be illegal.

 I'm not at all convinced that people and, more particularly,
 corporations, have really analysed the implications of web apps and
 

[tdf-discuss] Re: Why LO mobile version should not be ignored

2010-11-17 Thread Harold Fuchs

On 17/11/2010 21:45, Mirek M. wrote:

2010/11/17 Harold Fuchshwfa.libreoff...@gmail.com


On 17/11/2010 18:54, Harold Fuchs wrote:


On 17/11/2010 18:22, jonathon wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/17/2010 04:25 PM, Mirek M. wrote:

  I'd say that a web app should have higher priority here,




This should be an independent project.

In an ideal world, the code would be modular and clearly commented, so
that any developer could pick up various pieces, either to port it to a
new platform/OS, or to refine them a specialized function.

  web apps work on all platforms with a modern browser




The Internet is not always available. And where it is available, it is
not always cheap.
[ The data plan for my smartphone costs double that of my cable
connection, but only offers 1/10,000 of the data transfer that my cable
connection offers. Data transfer surcharges can reach US$1.00 per
kilobyte. (Data transfer, not data speed.) ]

  an open-source web app has many more possible uses than a desktop app;




The number of potential users is meaningless. What counts is the number
of people that can, and will use it.

  the mobile OS market is still pretty unstable: there's no clear



platform to develop for.

If you are waiting for a clear platform to develop for, you will wait
forever.

At best, there will be three dominant platforms for mobile devices, and
three dominant platforms for desktop devices, and three dominant
platforms for gaming consoles, for a total of ten different platforms to
code for.

The worst case scenario is that there will be five dominant mobile
device platforms, with another five dominant desktop platforms with
another five dominant gaming consoles, for a total of sixteen different
platforms to code for.

In either instance, you are looking at between twenty and thirty
different platforms, in order to support user-expectations, in terms of
cross-platform availability.

  all the other mobile operating systems haven't yet reached the level of



marketshare that iOS and Android have.

2010 2Q Marketshare
Symbian: 41.2%
RIM: 18.2%
Android: 17.2%
iOS: 14.2%
WinMO: 5%
Linux: 2.4%
Other: 1.8%

Source: http://www.gartner.com/it/page.jsp?id=1421013 (August 2010)

To call Android and iOS marketshare leaders, when they are more than
twenty percentage points behind the OS with the highest market
penetration reveals a lack of knowledge of mobile device marketshare.

Compared to 2009 2Q the marketshare is not there either:
Symbian: 51.0%
RIM: 19.0%
iOS: 13.0%
WinMo: 9.3%
Linux: 4.6%
Android: 1.8%
Other: 1.2%

* Symbian will probably retain first position, but it won't have the
thirty percentage point advantage in marketshare that it used to have;
* Due to manufacturing issues, iOS won't get above 20% --- if it can
even get that high;
* Android will flatten out at between 20% and 25%.
* Assuming RIM can satisfy the voyeurism that afflicts government
agencies, it should hold steady at between 15% and 20%.
* The other platforms will be holding their breath, wondering if their
oxygen supply will extinguish them;

jonathon



I think there's another consideration here: security.

What guarantees do cloud service operators give about the security of
any document I may store on its server? What prevents the operator's
employees or ex-employees accessing my documents? What prevents drive-by
hackers accessing my documents? What prevents someone targetting me
accessing my documents? What prevents someone targetting the service
provider accessing my documents? Can I set passwords on my documents? I
suppose I could encrypt my document but most people probably don't have
this technology readily available (see below).

What guarantees do cloud service operators give about the backing-up and
subsequent recovery of any document I may store on its server?

What guarantees do cloud service operators give about the availability
of any document I may store on its server?




A large part of the point of a portable app is that I can put the whole

kit and caboodle on an encrypted device if I want. Even without going to
such lengths, the security, availability and back-up/recovery is up to
me, not up to some unknown company whose procedures I cannot trust
(based on fairly recent history in many cases) whatever its policies may
say.




I agree -- security is definitely an issue. But it's always going to be an
issue, with everything that's online. There's always going to be a host that
has access to everything you upload.

However, with an open-source web app, you get the options of:
a) hosting the web app yourself, so that no third party has control over
your files
b) downloading the web app and running it offline




In several cases, storing documents on a server outside the owner's
country (or geographic region) could well be illegal.

I'm not at all convinced that people and, more particularly,
corporations, have really analysed the implications of web apps and
cloud computing. When they do I 

Re: [tdf-discuss] Re: Why LO mobile version should not be ignored

2010-11-17 Thread jonathon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/17/2010 06:54 PM, Harold Fuchs wrote:

 What guarantees do cloud service operators give about the security of
 any document I may store on its server?

Personal cloud servers: The cloud that _you_ run in your home, office,
or SOHO.

 What guarantees do cloud service operators give about the backing-up and
 subsequent recovery of any document I may store on its server?

Any individual or organization that thinks that a non-personal cloud
offers viable long term storage of anything is delusional.

 A large part of the point of a portable app is that I can put the whole
 kit and caboodle on an encrypted device if I want.

The point of the web application is to _supplement_ existing apps, not
replace them.

corporations, have really analysed the implications of web apps and
cloud computing.

Corporations have been using cloud apps for decades. The only thing that
is new about them is a sexier name.

jonathon
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJM5FYZAAoJEOpnmQXT8Ln/2VoIAJZDuZB6VsRfXyYcgyw4d/SL
6dZJv0yqhCmKdgF+hYTDtnriyl/LywF8Ah3WOj+0pyH2zhuBzF2sFFAuuS/VdZqJ
kiwMbcFnzfdarkz6h+4ogjDglO4DzjluDONm2CG3XyZW5pRc7q9dO8fSpJF6Yrh9
w2DoHrbiRlaMzhzlJy5PCrOcnc28svPp7JGifa2b/N6IU6MseIlR1fSuBOU0I+X3
XFdc/foOhXdIK1qmHAeibwsmlI+L8H1UhhgaCkD5CLmhpS3TisIUFirdGNHxseuB
Ig2Af+a0mw7zzNxQ4H1nFGXVxkERFmOFCtUFMIi7iVFfN+xB9CM6j64E3M2YoSs=
=fPn3
-END PGP SIGNATURE-

-- 
Unsubscribe instructions: Email to discuss+h...@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***



Re: [tdf-discuss] Re: Why LO mobile version should not be ignored

2010-11-17 Thread jonathon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/18/2010 12:00 AM, Harold Fuchs wrote:

 Personal cloud servers: The cloud that _you_ run in your home, office, or 
 SOHO.
 Name one.

Ubuntu for one
In Synaptic, select mark packages by task, then scroll down to cloud
computing cluster and cloud computing node.

 offers viable long term storage of anything is delusional. 
 Tell that to Google.

Google is acutely aware of the problems with long term storage in the cloud.

 or the names of their kids, on the web.

Not the Internet, but your _personal_ cloud.   The thing that you access
at home using your PDA, e-Book reader and the like.

 This concept completely negates the idea of a local cloud.

Thin clients almost mandate a local cloud.

#

Computers for home and SOHO usage are going in two contradictory directions:
* Smaller - thin client only;
* Bigger - network clusters/Beowulf clusters;

The thin client is what you'll take when you go out.
The network cluster that functions as your cloud, where your real data
will be stored.

jonathon
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJM5Ho1AAoJEOpnmQXT8Ln/WDwH/2/r2zCV16xwqoLCgDZDiCQF
jxOrlkFhFcrjcmlZ05tN1SrMwq3Jk/tH0hTGhFancD8fpxaIZ+DwXBOK2ONLVVvK
Us9J9bCQcarrXi+ziHjtKZmEJQnE8frguLnqJe3S+D6VbWf7hZVihzQ6LZIv5FaK
IoFjrxIIDVw97a/ZeYi3pXabHydn+tZMvbmjDaasGxVnllt+r40YZZHuZJ/Vf1Ev
IjYrHoxWEr7pYpoBWF5tmSNYvMrHC3FYSQC9ohX/QIWGVmocxBqQ9I222LC8/lIC
rXKtOMmvIDYAlv0ilj1TJ6b9fis6X0piSlVHKPHQPzTsHZA3Xu53koajMuA8Whk=
=YDet
-END PGP SIGNATURE-

-- 
Unsubscribe instructions: Email to discuss+h...@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***