Stuff Michael Meeks is doing
|
|
This is my (in)activity log. You might like to visit
Collabora
Productivity a subsidiary of Collabora focusing on LibreOffice support and
services for whom I work.
Also if you have the time to read this sort of stuff you could enlighten
yourself by going to Unraveling Wittgenstein's net or if
you are feeling objectionable perhaps here.
Failing that, there are all manner of interesting things to read on
the LibreOffice Planet news
feed.
Older items:
2023: (
J
F
M
A
M
J
),
2022: (
J
F
M
A
M
J
J
A
S
O
N
D
),
2021,
2019,
2018,
2017,
2016,
2015,
2014,
2013,
2012,
2011,
2010,
2009,
2009,
2008,
2007,
2006,
2005,
2004,
2003,
2002,
2001,
2000,
1999,
legacy html
-
Up, J. still in a bad way, call from Sanmarie - tap broken
and leaking; took H. to school - set off to fix tap - realised MOT
is today - set off for Cambridge.
-
Sat in the car show-room, experiencing '3' 3G mobile internet,
distinctly sub-optimal in terms of bandwidth it seems. Chewed through
older mail at some length.
-
Back, lunch, successful emergency plumber impersonation - back
to work.
-
Amused by Florian's post
on API design - very true; the real problem I see with using UNO
interfaces (for which read COM), is that migrating existing code to them
incrementally is abominably hard and inefficient, and never gets finished.
Put simply - it is easy to design the perfect API, what is more difficult is
to re-work the old code into the shape of that API. If you choose as a
pre-requisite an (essentially) viral technology like UNO that makes
incrementalism impossible: your entire API surface has to be UNO or not
at all (modulo evil 'tunnel'ing) - then you instantly turn the problem
into a "all or nothing" disaster area - whereby you have to re-write
"everything" all at once, and inevitably you do that either very badly
( and given the way UNO exposes concurrency issues on every single
call, this is almost inevitable ), or you take a very long time to
do it. By far a better way, is to design the new interfaces you want
(I assume there will be more than one interface), pick them off one by
one, and re-factor the code incrementally to them - testing for regressions
constantly. As/when that is done (if you can be bothered), providing a way
to add UNO-isation is then easy (modulo the legion concurrency hazards
you don't need to care about if you don't use it).
My content in this blog and associated images / data under
images/ and data/ directories are (usually)
created by me and (unless obviously labelled otherwise) are licensed under
the public domain, and/or if that doesn't float your boat a CC0
license. I encourage linking back (of course) to help people decide for
themselves, in context, in the battle for ideas, and I love fixes /
improvements / corrections by private mail.
In case it's not painfully obvious: the reflections reflected here are my
own; mine, all mine ! and don't reflect the views of Collabora, SUSE,
Novell, The Document Foundation, Spaghetti Hurlers (International),
or anyone else.
It's also important to realise that I'm not in on the Swedish Conspiracy.
Occasionally people ask for formal photos for conferences
or fun.
Michael Meeks (michael.meeks@collabora.com)
