About
Daniel StoneX ninja
Melbourne, AU
Links
my websitemy photos at flickr
x.org
eat.fi
Categories
/ (86)tech/ (84)
collabora/ (1)
fdo/ (9)
lca/ (1)
ubuntu/ (6)
x/ (41)
xds/ (3)
travel/ (2)
Archives
2010-Mar2010-Feb
2009-Dec
2009-Oct
2009-Sep
2009-Aug
2009-Jul
2009-Apr
2009-Mar
2008-Aug
2008-Jul
2008-Jun
2008-May
2008-Feb
2007-Oct
2007-Sep
2007-Jul
2007-Jun
2007-May
2007-Mar
2007-Jan
2006-Nov
2006-Aug
2006-May
2006-Apr
2006-Mar
2006-Feb
2006-Jan
2005-Dec
2005-Nov
2005-Oct
2005-Sep
2005-Aug
2005-Jul
2005-Jun
2005-Apr
2005-Mar
2005-Feb
2005-Jan
2004-Dec
2004-Nov
2004-Oct
2004-Sep
2004-Jun
2004-May
2004-Mar
Calendar
| < | April 2006 | > | ||||
| Su | Mo | Tu | We | Th | Fr | Sa |
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | ||||||
Sun, 16 Apr 2006
Everyone on #xorg-devel has seen me harassing people about our current stats
with bugs. If anyone with knowledge of the X codebase felt like coming in and
doing a bunch of really painful, unrewarding, triage work, it'd be massively
appreciated. That NEW line should really continue plummeting down! On that
note, I'd like to publicly big up Erik Andren in particular, for doing a ton
of awesome triage work so far to help us get that graph down, and help beat
our Bugzilla into something usable that helps us, rather than its current
awfulness.
[20:26 | /tech/x |
# | | home ]
Wed, 12 Apr 2006
Joe muses about Xlib and
connection aborts. Two things:
Yes, libX11 is going away. It's unfixably broken (not only is the implementation utterly horrendous, but the concept is exactly what toolkits don't want), and we can't change existing behaviours because libX11 is just one of those API/ABIs you cannot break.
Yes, the ability to recover from connection aborts is essential. D-BUS is broken in the exact same way, yet some people feel inclined to defend it (e.g. mandating reboots when either of the D-BUS daemon, or libdbus, are upgraded; advocating segfaults in client applications when the bus dies as the right thing to do?!?). I don't think either behaviour is in the least bit sensible, and it would be really keen if both could be fixed (by using XCB in toolkits for the former, by fixing libdbus to be less obnoxious for the latter).
[19:44 | /tech/x |
# | | work ]
Yes, libX11 is going away. It's unfixably broken (not only is the implementation utterly horrendous, but the concept is exactly what toolkits don't want), and we can't change existing behaviours because libX11 is just one of those API/ABIs you cannot break.
Yes, the ability to recover from connection aborts is essential. D-BUS is broken in the exact same way, yet some people feel inclined to defend it (e.g. mandating reboots when either of the D-BUS daemon, or libdbus, are upgraded; advocating segfaults in client applications when the bus dies as the right thing to do?!?). I don't think either behaviour is in the least bit sensible, and it would be really keen if both could be fixed (by using XCB in toolkits for the former, by fixing libdbus to be less obnoxious for the latter).