jd:/dev/blog - Commentaires

Fuck you GNOME - Frans

Frans — Sat, 06 Mar 2010 17:27:19 +0100

It is one of the most inconvenient crash for all the active terminals to just disappear. I tend to organize my work by the open terminal tabs (in different virtual desktops). I have experienced the same happen with KDE 4 (Kubuntu 9.10) - konsole crashing, I think also because configuring it... KDE3.5 was so much more stable... Fuck KDE4... made me want to switch to GNOME... But now not so sure any more...

On media players: 2 years after - Amir

Amir — Sat, 23 Jan 2010 08:08:09 +0100

I found gmpc much better than Sonata. Did you try it? And as a long time mpd user, I found mpdscribble the best scrobbler out there (if you are into scrobbling).

On media players: 2 years after - Mauro

Mauro — Fri, 22 Jan 2010 16:54:53 +0100

I must agree with '_deepfire', after a couple of years using sonata+mpd, the other day I tried quodlibet and so far I'm satisfied with the results.
The only thing I miss about these two is the 'sort by date added' type of ...sorting that Rhythmbox has.

On media players: 2 years after - _deepfire

_deepfire — Fri, 22 Jan 2010 09:57:24 +0100

Have you seen Quodlibet? I'm also a xmms-style (ok, winamp-style) player lover, so I'm currently split between audacious and quodlibet. The nice thing about the latter is that it has multiple, easily accessible, winamp-style playlists which you can drag-and-drop between.

I'm going to see Sonata, though.

Fuck you GNOME - Diego

Diego — Sat, 26 Dec 2009 18:11:20 +0100

Fuck gnome, long live KDE.

Python cairo and XCB support - jd

jd — Wed, 23 Dec 2009 07:47:23 +0100

I've an ITP on xpyb, but did not have the time to work on it.

matt, this are side projects for now.

Python cairo and XCB support - matt

matt — Tue, 22 Dec 2009 22:06:19 +0100

Reading your last two posts it seems that python might be used in feature awesome development? Or are these side projects?

Python cairo and XCB support - me

me — Tue, 22 Dec 2009 21:16:45 +0100

does the mentioning of xpyb in a debian related blog mean we'll see a debian package any time soon?

Teething troubles - juli1

juli1 — Tue, 22 Dec 2009 13:49:35 +0100

jd, you always was a great storyteller, I like this one

Teething troubles - jd

jd — Mon, 21 Dec 2009 08:41:04 +0100

Enrico, I totally agree.

Teething troubles - Enrico

Enrico — Sun, 20 Dec 2009 23:15:09 +0100

For some reason, the core python community has always come across to me as a bunch of arrogant people that would not take any criticism without framing you like an idiot first. For that reason, I've never posted to a python list, nor reported a python bug outside of Debian. Which is funny, because since I've never interacted with the core python community ever in my life, I have no reason or personal experience that makes me say that they are bad.

It's just some impression I have constructed out of I don't know what. Maybe it's just the way python insults you when it's wrong (sys.stdout has different encodings if it's on terminal or on a file, which easily gives you a utf8 backtrace which when googled gives lots of answers like "if you get this backtrace you're an idiot"), or the major design issues in the python standard library (datetime.datetime and timezones? configparser?) or annoying everyone with TIOOWTDI and then having two versions of at least StringIO and Pickle and urllib in the standard library. I don't know. But still, python's a decent tool to get the job done once you get to know its quirks.

Such quirks are not documented, and if you try to raise a concern about them you'll be treated like an idiot because obviously everyone knows them except you. Sometimes one is documented like a cool thing (for x in range(10): do yield lambda x=x: x**2 -- I do not think that is a cool way to do closures, I think even javascript's more elegant in that).

But still, there's worse things to get a job done.

Teething troubles - glandium

glandium — Sun, 20 Dec 2009 22:45:06 +0100

It's so much better to close bugs without even giving a reason, then marking it wontfix when the bug is reopened, still without a reason, and still fail to give a reason when asked for one, again... and then also ignore other users adding to the bug. http://bugs.debian.org/cgi-bin/bugr...

Teething troubles - Titus Brown

Titus Brown — Sun, 20 Dec 2009 15:03:04 +0100

I sympathize with your irritation, but I would ask you to think a bit more about the situation. Yes, it's a ten line fix; so are many others. What does it break? Does it cause new problems? Does it change any behavior? Given where it is and what it changes, the answer may well be "yes", and I think this was clearly stated in the followup e-mails.

python-dev strives to produce quality software, and part of that is not causing new bugs while fixing old ones.

That having been said, python-dev is overextended these days, which doesn't help.

--titus

Teething troubles - A. Reuleaux

A. Reuleaux — Sun, 20 Dec 2009 13:49:37 +0100

Just wondering: What are you trying to
use Python for?

Various news: what happend durring summer - web design miami

web design miami — Fri, 11 Dec 2009 00:12:21 +0100

Looking forward for the 3.5 . thank u for sharing the information

Fuck you GNOME - Helgim

Helgim — Thu, 26 Nov 2009 08:53:17 +0100

Every day is another step towards Gnome/Linux.

Fuck you GNOME - xhater

xhater — Wed, 11 Nov 2009 03:22:13 +0100

yeah, fuck you gnome.

Fuck you GNOME - Jon

Jon — Tue, 10 Nov 2009 11:14:12 +0100

@mike: thanks -- that does the trick! Perhaps someone will hack a gconf key at some point to toggle this as default behaviour.

Fuck you GNOME - anon

anon — Tue, 10 Nov 2009 00:27:28 +0100

harsh

Fuck you GNOME - mike

mike — Mon, 09 Nov 2009 22:52:14 +0100

That happened on me too, with the Xfce terminal. It crashed on settings changes (the version 0.2.x quite often, the newers having been fixed). And yes it sucks but I didn't blame Xfce for it.

@Jon Terminal (Xfce) has the option --disable-server to not use DBus to check for running instances. gnome-terminal has --disable-factory.

echo blacklist pcspkr > /etc/modules/blacklist.conf (or something like that) tho I have a Beep channel in my mixer card lately.