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 later, breakfast, chat with Tomas about moblin &
various window manager hints; good stuff.
-
Prodded at my boot-chart; it seems that there may be up
to three lots of the 500ms second wait in my boot-chart, previously
hidden by the lame-ness of the old-style bootchart rendering. Fixed
a couple of bootchart2 bugs.
-
Wrote up meeting notes on the train, poked at various bits
of code. Read some nice Cg code doing IDCTs in pixel shaders - nice,
I wonder if (perhaps with suitable annotation of methods & data
structures to identify promising targes) we could persuade the Mono
JIT to generate code to run on the GPU.
-
Amused to read the FT this morning; China's foreign ministry's
spokes-woman Jiang Yu said: "China's internet is open." - a
whole new meaning of 'open'ness - or is it ? open-ness with a hard
edge ? ...
-
Interesting and accessible talk Not
your Father's Von Neumann Machine - from the JavaOne conference.
NB. the slides update below the video. Sadly, he doesn't mention
callgrind's sexy cache simulation, though he should. Also, the horrendous
irony of pointing out that "Memory is the new disk" at a Java
conference; Java is a case-in-point of hobbling by excessive pointer chasing
(cf. .Net's value-class 'struct' concept). Some interesting thoughts though,
one of my pet peeves is eg. that most 'sax2' parsers do their parsing
incrementally, rather than parsing a big chunk ( nicely warming the branch
predictor for the parsing code-paths, the hash tables for interning
etc.) and queueing the result to emit; they often parse a single element,
then emit that: not a good idea. Volunteers to fix the OO.o 'FastParser'
to do this more intelligently (and/or preferably use a different
thread to parse, vs. emit the callbacks) appreciated.
-
Slogged away at Tax / accounting fun in the evening. Out to
visit Solomon & Peace.
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)
