toki wrote:
Or do you seriously think that somebody should put up with a mean time
of 100 seconds to BSOD, in addition to its other known points of
failure, instead of using tools that work as advertised, and is
compatible with tools on other platforms?
jonathon
Obviously, your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/04/2011 11:58, aqualung wrote:
that with MSO97 on Win2K mean time to BSOD was just on 60 minutes.
That's odd. Don't have MSO 2010, but with MSO 2007 under Windows 7 I have
It doesn't matter which version of windows with which version of MSO
On 6 April 2011 12:54, aqualung xfekdcugj...@mailinator.com wrote:
Ian Lynch wrote:
On 6 April 2011 04:41, aqualung lt;xfekdcugj...@mailinator.comgt;
wrote:
Well, how many full-time developers, working 40-hour workweeks, does
Microsoft Office have... and how many OOo and LibO?
If
Mark Preston wrote:
There may be some truth to what you say, but I don't think Microsoft
bashing will advance LibO, which is what we want to do.
Mark, you confirm my suspicions: open-source folks don't really want
Microsoft to stop their outrageous proprietary file-format lock-in, because
A follow up-thought: As I google my way through history catching up on
developments, I come across
http://news.cnet.com/OpenDocument-goes-to-vote-in-Texas,-Minnesota/2100-7344_3-6157245.html
this page reporting on ODF file format being made mandatory (to the
exclusion of proprietary Microsoft
On 6 April 2011 04:41, aqualung xfekdcugj...@mailinator.com wrote:
Well, how many full-time developers, working 40-hour workweeks, does
Microsoft Office have... and how many OOo and LibO?
If the answer for MO is, say, 300... and the full-time equivalent for OOo /
LibO is 50... then it's
Ian Lynch wrote:
On 6 April 2011 04:41, aqualung lt;xfekdcugj...@mailinator.comgt; wrote:
Well, how many full-time developers, working 40-hour workweeks, does
Microsoft Office have... and how many OOo and LibO?
If the answer for MO is, say, 300... and the full-time equivalent for OOo
/
Mark Preston wrote:
That really is not something we can do much about without hiring
Microsoft to make sure they are fixed - and that simply will not
happen, even if we wanted it to.
Okay... while waiting for my two comments from earlier today to be approved
by the mailing list, I thought
Well, how many full-time developers, working 40-hour workweeks, does
Microsoft Office have... and how many OOo and LibO?
If the answer for MO is, say, 300... and the full-time equivalent for OOo /
LibO is 50... then it's pretty much a given that MO will always have a
bigger feature set and be
