Tag: ubuntu

Next > Last >> Page 1 of 2

Reporting from Ubuntu Global Jam Novosibirsk

Posted by lucidfox.org at

This is my second time now — writing from my netbook. Last time, in March, I was invited to make a presentation about the Ubuntu developer community, process, and technical details of packaging. (Incidentally, this upload was made from there when I was showing the process of fixing a bug in a package.)

The atmosphere is not very different — perhaps more summery, though, as back then it was cold like it always is in early March, and now it’s +30 Celsius outside. There are about 17 people in a local university, most of whom look like your average geeks.

This time, technical details of packaging were explained right before me, allowing me to jump straight to the matter when the time came for practice session. Unfortunately, it turned out wireless wasn’t working on my Eee PC 1000H when I arrived (even though it always worked out of the box here, under Karmic, Lucid and Maverick), but downloading 300 MB worth of Maverick updates fixed that. The attenders were pleasantly impressed with Unity, although it took some time to explain what was “that network thing that replaced Network Manager), and how indicators were better than the notification area.

My presentation was about the relationship between Ubuntu and Debian. I explained the difference in release cycles and the processes by which packages and patches are exchanged between the two distributions. I cited the recent statistics on people who are both Ubuntu and Debian developers, stressing that they can help Ubuntu contributors share their changes with Debian, and get started with Debian developer teams.

Finally, as the second part of my topic, I demonstrated merging package changes with Debian and Ubuntu in the case of a VCS-maintained package, by using xvidcore and git-buildpackage as an example.

I hope that these presentations running together got people interested, if not about joining the Ubuntu and Debian development teams (although one was curious how long it took for me to become a MOTU), then at least about contributing to their packages.

“That Theme with the Orange”

Posted by lucidfox.org at

Some people have asked about the GTK theme on the screenshot in my previous post, wondering if it’s the Radiance Maverick beta.

It’s not. However, while I’ve been waiting for said beta, I applied the color scheme of Ambiance Maverick, with its delightfully pronounced orange, to the excellent Finery theme by iperationer, itself intended to be a “better Radiance”. I’m not really planning to become a long-term maintainer for the modified theme, and it’s rather hackish, but here it is.

You can download the theme from the github fork of iperationer’s Finery, or directly as a tarball here.

To use Finery and derived themes, you will need the Equinox theme engine, which in Maverick is available in the gtk2-engines-equinox package.

And Stay Out!

Posted by lucidfox.org at

The effort of Ayatana and Ubuntu developers has finally paid off. Since the new keyboard indicator has landed in Maverick and I previously replaced network-manager with connman/indicator-network, at last I could ditch the ugly, now-empty notification area on my GNOME panel, and leave only the indicators.

None of the applications I use now make use of the notification area. If I do find some that do, I’ll try to fix that before Maverick release; gwget comes to mind, but really it’s quite old by itself and what I need is a new, slick-looking download manager. Now, if only there was a way to hide individual indicators to reduce clutter… (Hint, hint.)

Netbook “Branding”

Posted by lucidfox.org at

Got my supply of Ubuntu stickers from the Canonical store today. Oddly enough, they shipped faster than goods from the Russian online shop I occasionally order books and DVDs on, go figure.

I like this shade of orange. Just bright enough to make good contrast with white and look interesting, and just subdued enough not to seem rawr-aggressive.

Maverick: Indicators for Liferea and Epiphany

Posted by lucidfox.org at

It’s been a long ride, but support for the messaging indicator for Liferea has finally landed in Maverick, backported to version 1.6.3.

There is now a separate PPA for those wishing to try and test this version on Lucid, rather than the unstable 1.7. One major difference between the version that went in and the 1.7 version in my PPA is that the now-official Maverick version never sets the attention flag (the “green envelope”). To quote Ken VanDine:

I don’t think liferea should set draw-attention at all, the intention of that is for important messages that need somewhat immediate attention. I think of RSS feeds as rather passive, read them when you can as opposed to an IM that might require a response within a few minutes. Setting draw-attention everytime liferea refreshes will make that property less effective for IMs, calls, emails, etc.

Meanwhile, I have patched the Epiphany web browser to replace the download notification area icon with a custom indicator. One more step towards doing away with the tray.

NVIDIA, Cairo, and the Weird Whiteness

Posted by lucidfox.org at

I spent the last two days fixing regressions in the Murrine engine related to the unholy mix of Cairo 1.9 and the NVIDIA proprietary drivers. As a result, I now have a patch that should almost completely fix the dreaded white widgets bug in Maverick. I have prepared a PPA and uploaded the packages to build while I’m waiting for my patch to get reviewed and sponsored into Ubuntu proper. (Isn’t it ironic that I, a MOTU, have to rely on sponsorship for so many of my uploads because they touch packages in main?)

There is also Docky, and it’s most certainly also Cairo-related, but it’s a separate problem and I’ll look into it alter. As for Pinta, the grey canvas problem I mentioned in my previous post was also not Murrine-related (but it was Cairo-related), and is now actually patched in Maverick, along with the upgrade to version 0.4.

On an unrelated note, I fixed (in Maverick) the bug with the Epiphany bookmarks menu not being updated in the application menu. Epiphany users, rejoice!

Upgraded to Maverick

Posted by lucidfox.org at

Almost everything works fine, the upgrade went more smoothly than I expected. However, half my GTK widgets are now white in all themes, and the Pinta canvas is grey and doesn’t work. I suspect it might be due to the large number of custom PPA packages previously installed on my Lucid system.

Going to do a fresh install from the daily ISO, to get btrfs. Also, it’s going to be a 64-bit ISO. This will be my first time trying 64-bit Ubuntu, after spending four and a half years on 32-bit. Wish me luck!

Dear Canonical

Posted by lucidfox.org at

This “closed fonts beta” thing was a big PR mistake.

It’s not enough for you to push a proprietary font into Ubuntu in the default install. No, you can’t even release it publicly. You just had to release it as a closed-doors, “members-only” beta.

Think about it. Canonical develops one of the world’s flagship free operating systems. Now they have made a decision that runs contrary to the entire spirit of free software. They are going to bestow their free operating system with a proprietary font (because apparently using any of the better free fonts instead of DejaVu isn’t cool enough). Why a closed beta? Did Canonical suddenly become Blizzard?

They try to sweeten the pill by saying words like “It will be free for everyone to use and share”, adding, of course, that the license is not finalized. Judging by Canonical’s prior history with such “exclusive initiatives” ([coughubuntuonecough]), know what this means: we won’t get the source until the heat death of the universe.

And then I saw the package name: “ubuntu-private-nda-fonts”.

NDA?

That dreaded TLA that you never mention in the free software community, lest you get bombarded by rotten tomatoes?

Wait a minute. I have never signed any NDAs in my life. Did Canonical make me implicitly sign one just by being a member? Ow.

And before I get comments like “don’t use it if you don’t want to”: not only will I be forced to do that on default installations starting with Maverick, but I feel dirty just for having access to that PPA. I would like to have a way to get this privilege, which I feel embarassed for having, revoked.

Idea: File Operation Indicator

Posted by lucidfox.org at

Disclaimer: I’m not a member of the Ayatana team. I’m not affiliated with Canonical. I cannot guarantee that they’ll ever find this idea interesting enough to implement, or even read this thing.

Indicators are becoming more and more common with each Ubuntu release, as a part of the desktop notification mechanism, and a way to group alike applications running in the background. This is an idea of what I think could make a good generic indicator: file operations.

On today’s desktop, there are many applications doing file transfer in the background. Nautilus already uses an indicator for its file copy operations, but it’s specific to Nautilus. Other applications — web browsers, P2P clients, FTP clients, download managers — usually display progress in their main window, without a way to see the progress without switching to the application.

So, why not have a single menu where applications can add their entries when file operations are in progress? It can include information on the percentage completed, and maybe provide buttons to cancel and (if the application supports it) pause an operation. And an application whose sole purpose is to download files, like transmission or gwget, can live entirely in that indicator without cluttering the notification area with its own custom icon.

I hate Twitter

Posted by lucidfox.org at

This post really shouldn’t be here, but… gah…

I’m sick of Twitter. I’m fed up to the brink with it, raging with enough passion to fuel a thousand suns and incidentally provide a long-term solution to Earth’s energy concerns.

It is my berserk button. Worse even than reading about stupid Internet memes, or immature testosterone-overdosed conversations, or watching Doctor Who fansites sing odes to Steven Moffat and realizing I’m basically alone in my grudge against him for breaking a series I used to enjoy, or sitting late at night wondering why my love hasn’t woken up yet on the other side of the planet, or finding out that the shop is out of my favorite kind of chocolate.

No, this is all survivable. There is a special, raw, undistilled kind of hatred reserved for Twitter, enough to cause swollen veins every time I see references to it on every single website I visit, in every single IRC community I chat in. And I’m so sick of “not getting it” that my nasty side causes me to vent against people using it, bringing out my worst qualities that I usually keep locked up, or at least try to.

The worst thing about Twitter is not even that it’s a solution in search of a problem; that it’s basically asking you to justify using it; that for most of uses that its proponents defend, there are better, tried and true solutions that are open standards to boot rather than centrally controlled websites; or that most of it seems to be shallow, self-absorbed, pointless drivel or noise that’s incomprehensible unless you’re immersed in the Twitter subculture. (“RT @” anyone? What does that even mean?)

The worst thing is that it’s become self-perpetuating and self-sustaining, “famous for being famous”. From my experience, most people use it not because they have evaluated its sensible uses and decided it solves some of their genuine needs, but “because everyone else does”.

And with most other “trendy” things, I feel left out of the loop. But none of the others are regularly poked in my face with such prominence and persistence as this abomination of a website.

What to Expect in Pinta 0.4

Posted by lucidfox.org at

The next version of the Pinta image editor is still quite far away apparently (this depends on the project leader, Jonathan Pobst), but here’s a sneak peak of what to expect (and what is currently landed in git):

  • Support for opening and saving in OpenRaster (.ora), a simple multi-layered bitmap format compatible with Krita, MyPaint, and GIMP (with a plugin).
  • Saving in BMP, ICO and TIFF in addition to the already supported JPEG and PNG.
  • Docking tool windows.
  • Better, non-pixelated resize algorithm.
  • Improved text tool, with full Unicode input and no more pesky squares.
  • Zoom by mouse wheel and hotkeys.
  • Better GNOME integration: toolbar respecting system settings, and open/save dialogs remembering the directory and file name and suggesting the Pictures directory by default.
  • And bugfixes, of course!

True Transparency for xchat-gnome

Posted by lucidfox.org at

My earlier patch for the xchat-gnome userlist setting was accepted upstream some months ago, but sadly, version 0.26.2 is still unreleased, so the code is only in git and didn’t make it into Lucid. Ah well.

For now, have another patch — this one turns the transparency slider in xchat-gnome settings into true alpha transparency, a la gnome-terminal, if desktop compositing is enabled (like with Compiz). As a bonus, it prevents xchat-gnome from crashing if the transparency setting is enabled with Murrine RGBA support turned on.

The PPA for Karmic and Lucid is here. It has both the user list and transparency patches applied.

Customizing notify-osd

Posted by lucidfox.org at

We have had three stable Ubuntu releases featuring notify-osd, and yet, not a single one allowed the user any configuration. I don’t know why, really — it seems to fit the Ayatana team’s “our way or no way” general disposition, but who am I to judge them?

Then I stumbled upon this post. It’s in Russian, and quite old (2009-12!), but it gets the job done. To make notify-osd customizable, you need to add Roman Sukochev’s PPA to your Software Sources, do a system update, and then restart notify-osd (by relogging, or executing pkill notify-osd).

After installing the patched version, you can tweak notify-osd by creating a .notify-osd file in your home directory. A version replicating the Karmic/Lucid defaults can be copy-pasted from here. You can tweak it from there — it should be self-evident.

After I’m finished polishing the Liferea patch, I’ll look for a way to make this patch less hackish. Perhaps move from text settings to gconf, and then write a GUI configuration utility.

As for the only non-obvious setting: “slot-allocation” controls the placement of bubbles. By default, it uses the Jaunty behavior (“dynamic”): all bubbles in the upper-right corner. For the Karmic behavior, where there’s a gap reserved for confirmation bubbles (volume, etc), set it to “fixed”.

Indicators for Liferea

Posted by lucidfox.org at

If you’re as fond of the messaging indicator as I am, you will appreciate the news. I have made a patch for Liferea as a functional replacement for the old tray icon.

It is not in Ubuntu yet, and I haven’t actually tested the patch on the stable 1.6.x version yet. However, for 1.7.x, it is here, available in my PPA for Lucid, and I’m about to send it upstream. Like with Pidgin, the regular tray icon is not displayed at all if the indicator applet is present.

Russell T Davies: A Retrospective, Part Two

Posted by lucidfox.org at

“I honestly couldn’t care less if Martha falls for the Doctor or not. And I don’t want any more references to Rose. I don’t want Martha compared to Rose. I don’t want Martha insulted because she isn’t Rose. I just want Martha and the Doctor to explore and battle bad guys. Is that really too much to ask?”
~ Kevin Lahey, review of “Gridlock”, pagefillers.com

Davies’ venture was inherently paradoxical, dualistic. This was noted by many. One Mike Taylor noted correctly that Davies, at times, seemed “not to get it”, made the Doctor too human, with too much emphasis on Twue Wub. And yet, it was his show and his writing that hammered the idea of the lonely Time Lord being alien, inhuman, other; following his own logic and moral code, often seen as weird by his human companions, but emerging right and victorious in the end — except the times he went too far, and needed the human factor, in the form of the companions, to stop him.

Davies was, on one hand, a producer and brainstormer interested in seeing the show blossom and prosper; but on the other hand, he was an old-time Doctor Who fan. But wait a minute, so is Moffat!

“I am incapable of contradicting an established fact of Doctor Who lore. I just can’t do it, any more than Russell. Russell sticks in little tiny bits of dialogue to account for the fact he might have vaguely contradicted a William Hartnell story in 1965.”
~ Steven Moffat

So, where lies the difference? We’ll get to that.

You could indeed argue that Davies wrote a good show, if you take “show” in the sense of spectacle. Let’s take his typical episode: everything is loud, things go boom, people are running and talking non-stop, there is some not-so-subtle postmodern commentary linking the exotic alien environments to the present day, and in the end… something happens. But what’s the problem? The problem is that these episodes are too absorbed in their own self-awareness, the author’s smug overview of the setting, and the mandatory “character development bits” disjointed from the main plot that they don’t tell good stories.

For an episode to be a story, it has to have, like, plot, with, like, cause and effect narrative — where the end conditions can be reasonably inferred from the starting conditions. When it breaks down, it accounts to the plot being little more than a chain of contrivances to drive the characters from one scene to the next one. This especially shines in episodes like “Boom Town” or “The Stolen Earth/Journey’s End”, where the plot is just a paper-thin pretext to get the characters to interact and either foreshadow things for future episodes or showcase the Cool Action Scenes. The often-noted “disjointed”, clip-show nature of RTD scripts (best exemplified by his final farewell to the series, “The End of Time”) stems exactly from this: writing individual scenes first and adding the plot as an afterthought. Of course, after all the Important Dialogue is delivered and the Great Revelations are made, the plot becomes a hindrance (best example: “Doomsday”) rather than the main point of the episode, and is quickly dispensed with, usually with a quick application of the magic TARDIS, magic sonic screwdriver, or some technobabble invented on the spot.

In fan circles, the words “RTD script” have almost become synonymous with “deus ex machina”. (In this sense, “The Parting of the Ways”, one of the worst offenders, is interesting in its own right: an almost-literal “god” steps out of a literal machine, the TARDIS, and sets things right.) Granted, this is not always the case. “Tooth and Claw” is ranked high among RTD episodes, presumably exactly because the resolution is adequately foreshadowed in addition to the episode itself being atmospheric. “Midnight” was good, but it was good by virtue of Davies abandoning the usual Doctor Who format in favor of writing something he’s actually good at: suspense drama.

And this is his second paradox: we’re dealing with a Doctor Who fan who despises Doctor Who fans, and a television producer who makes jabs at his own audience. An example of the two aspects of his personality reinforcing rather than contradicting each other.

“We already knew that Davies had a low opinion of his audience. They are too thick to understand scientific explanations; too unimaginative to be able to deal with stories set on the Planet Zog; too ignorant to have heard of any but the most iconic historical characters; and so shallow that if there is even two minutes of exposition, they’ll get bored and switch channels.”
~ Andrew Rilstone

Well, that may be too harsh. He did comment on “planet Zog” in defense of every season 1 episode being set within Earth orbit at some point in time, only to boldly go into that territory with the dreadful “New Earth” and later, less dreadful episodes. He does make in-story jabs at the Doctor Who audience, both the nerdy fandom (the even more dreadful “Love & Monsters”) and the mainstream (pre-character-development Donna). He wrote directly about hating Internet forums discussing him.

It would be easy to say that Davies “doesn’t get SF”. It seems more complicated than that. I’d say his main problem is that, and this is his producer side speaking, he underestimates his audience — an offense never committed by his Japanese “spiritual counterpart”, Nagaru Tanigawa, who also writes “soft” SF stories with a touch of romance for the “Internet generation”, yet manages to do it in a way that emphasizes both his skill as a writer and his respect for his readers. Davies thinks he can get away with nonsensical technobabble and lack of verisimilitude in his settings (“Gridlock”, anyone?) because it’s supposedly not what the mainstream audience cares about. So he goes out of his way to make his settings “relatable” to the modern audience by making them bizarre, grotesque pastiches of the present day (“The Long Game”, “Bad Wolf” and the aforementioned “Gridlock”), and he gets points for nailing the idea that the residents of these dystopias treat them as perfectly normal and the only possible states of living — while nevertheless depriving them of any degree of believability.

Note that I don’t ask for realism. Heck, I like some of the boldest, most “unrealistic” ideas from the new series, as long as it makes logical sense and is internally consistent. (For example, speaking of Moffat, I don’t mind the effing space whale, but I don’t see how anyone in their right mind would design peacekeeping androids on an Earth starship to look like the Smilers.) We have the 1984 effect: there is no way these societies can work, simply because of the human factor, even with all the advanced technology you want, and ignoring the pop culture references. (It’s telling how often “Bad Wolf” was praised for being allegedly a clever satire of mind-numbing reality shows, while in fact those were never intended as satire and RTD inserted them as a tribute to them.)

Davies is at his best when he drops his “viewers are morons” assumptions and writes intelligent stories for intelligent people. I haven’t watched it, but I was told that Torchwood: Children of Earth is really good, part of it because it drops all the random, inorganic, forced silliness that in Doctor Who specifically exemplified by two things: creating “kid appeal” species that fall flat, such as the Slitheen, Adipose and especially the dreadful Abzorbaloff, and inappropriate pop culture jokes where drama should be. (His pet character is specifically guilty of that, which is one of the reasons that contributes to the annoyances of season 2.) Doctor Who always oscillates between silly and seriousness, between comedy and drama; but in Moffat’s case, for instance, both tie together organically, without random bits of either sticking out like sore thumbs.

As for internal consistency, let’s just look at all the times he made familiar concepts exhibit many previously completely unseen functions, exceptions and corner cases, including such core ones as the TARDIS, sonic screwdriver and regeneration. (Regeneration can be either quiet or violently explosive, sometimes it plain doesn’t trigger when the plot demands it, you can refuse it at will — something never seen before — you can regrow limbs for as long as the plot says, you can suppress regeneration by channeling it into said severed limbs, which will cause copies of you to grow from them, etc etc etc.) Really, the phrase “it works that way except when it suddenly doesn’t” describes just about anything about RTD’s pervasively used plot devices: while the basic concept stays the same, intricacies appear, disappear, and are plain handwaved in with no foreshadowing when the story demands it.

No review of RTD, even a very informal one, would be complete without mentioning his pet character, Rose Tyler, and the tackled-on George Lucas love story (at least the creators were smart enough not to make the Doctor mention love explicitly, not even Rose’s personal Doctor Clone For Shippers, thus allowing viewers to make their own interpretations). Indeed, that’s his fanboy side kicking in, and it’s best said by TV Tropes: sometimes it feels like he’s writing a fanfic of his own show, making all the same mistakes that make most fanfiction look bad (as opposed to stories written by authors who actually “get” the setting and the characters). The adventure-of-the-week format is both a strength and a weakness: a weakness because it forces writers to squeeze plots and interesting settings into 45-minute straightjackets, and a strength because if you didn’t like this week’s episode, chances are, next week’s will be completely different. The same story is with characters, the constant cast turnover lets you pick favorites. Don’t like Martha? Try Donna’s season. Can’t stand Ten? Chances are, Nine or Eleven will appeal to you more.

And this is where Rose stands out from the other companions. Not because she’s inherently better or worse, mind you. But her creator tries to force us to think she is, with all the subtlety of an anvil. While my opinion of Rose as a person is less than rose-colored, to put it mildly, what makes her particularly annoying is that the show couldn’t shut up about her even long after she was stranded on Earth-2 — notwithstanding even her temporary return, purely to appease shippers, cheapening the drama of that separation. Yes, we get it — RTD thinks she was the Best Companion Ever, and wants to portray her and the Doctor as an item. (The fact that he didn’t give a 900-year-old Time Lord any legitimate logical reason for attachment to a completely random average companion is another story.) Now, can we please move on and see him saving the universe with someone else without the obligatory reference to Rose every episode?

Whoosh. This was a lot of text. Hopefully, I’ll be free of accusations of hating Russell T Davies. I hope I demonstrated that it’s not the case, I don’t hate him. As for love (in a non-romantic sense)… If I were to describe my complicated, multi-faceted opinion of him with a list of single words, perhaps that one would have a place on the list too, and maybe not even the last.

Russell T Davies: A Retrospective, Part One

Posted by lucidfox.org at

“I don’t want to go…”
~ The Tenth Doctor, last words

This is going to be a strange post. Strange because I don’t really know enough about RTD to judge him. Of his work, I’ve only seen his venture in the new Doctor Who series (2005-2009) and the pilot episode of Torchwood, “Everything Changes”. But I’m not going to speak of Torchwood (which I have no opinion about, although I’ve heard mostly negative comments about it) and his earlier works like Queer as Folk. This is an attempt to look, in retrospect, at his impact on the series that he spearheaded for five years.

Fan opinion on Russell T Davies is polarized. Some believe he ruined the series forever, or alternatively, did nothing throughout his years but spitting on the grave of the Good Ol’ Classic™ Series. Others regard him as the second coming of insert favorite producer here and worship the ground he walks on. This is to be expected, particularly since it’s a fandom we’re talking about. I said before that I don’t call myself a fan of anything, and part of the reason is that for every relatively recent work of fiction that I happen to enjoy, I eventually end up disliking its fandom. Or rather, disliking the loudmouth “yer doin it rong” factions that constantly bicker against each other, or focus on shallow, superficial traits of the characters and write kiloscreens of slashfiction with blatant disregard for plot, characterization and background themes (especially prevalent in anime fandom, for example Haruhi Suzumiya — a fairly clever teenage SF series by a competent author and maybe the closest thing thematically that anime has to Doctor Who, turned into a joke by its own fandom).

So, as a non-fan who just happens to be interested in Doctor Who, I’ll try to present a Cliff Notes version of my strange, complex love-hate attitude to the man behind the 2005 revival, Russell T Davies. As a disclaimer, I never saw any of the old series episodes (I honestly tried to watch the First and Fourth Doctor, but found them too cringeworthy by modern standards — although I did read a lot about the old series on the TARDIS Wiki, complete with screenshots), so all I can compare the RTD series to is the Eighth Doctor movie and the three episodes of Series 5 released so far.

First things first: RTD is a brilliant marketer. He succeeded in the seemingly impossible: not only did he bring back an old SF series, fairly obscure outside the UK and mostly remembered as low-budget and over-the-top silly (after a failed revival attempt in 1996, no less), the new series turned into an unprecedented worldwide success, ensuring its bright future for years to come. He seemed to know just the right actors; Eccleston, Piper, Tennant, Agyeman and Tate were all regarded as questionable choices at best when the casting was announced, yet these naysayers quickly drowned in cries of praise when the new Doctors and companions hit the screens.

He knew how to stir and bait the press (with pretentious titles like “The Next Doctor”) and ensure publicity for the show, how to keep the wheel of speculation and rumors (sometimes outright incorrect ones, intentionally so) running, and fuel the interest in both the series and its backstage revolutions for viewers and journalists alike. And here we see one of RTD’s persistent qualities: everything around him screams loudly. “Look at me! I’m an important piece of information! I’m here for a reason!”

He knew that simply bringing the show back in its original format wouldn’t bode well with a 21st century audience, and to survive, it had to adapt and evolve. Hence the new 45-minute format and the new in-universe aesthetics: under various pretexts, the new series “modernized” such dated (“retrofuturistic”) elements as the TARDIS interior, the sonic screwdriver, the Daleks and the Cybermen, although the police box exterior proved to be too iconic to touch in any significant way. It almost feels like a “reimagining” that’s oddly in-continuity with the previous show; granted, Doctor Who evolved quite a lot over its original 26-year-old run (heck, the series as originally conceived didn’t have the Time Lords, regeneration and the sonic screwdriver, now considered iconic elements of the mythos), but the changes between the old and new series were the most drastic modification the franchise ever faced.

And amazingly, with such drastic changes, complete with the allegedly “un-Doctorish” Christopher Eccleston, Doctor Who remained recognizably Doctor Who — whereas the 1996 movie is often claimed to be “not really Doctor Who“. (And indeed, my first impression of it, after exposure to the RTD series, was that a recognizably Doctorish Doctor somehow ended up in an alternate universe of an American cop movie.)

At the same time, the series became more self-aware, if not necessarily “darker” — a definite plus in an age where a detailed analysis of every episode’s goofs and plot holes appears on the Internet within minutes after the episode finishes airing. The first season alone explored such themes as:

  • The Doctor’s loneliness and survivor’s guilt following the Time War (by itself, a good catalyst to rebuild mystery around the Doctor after we found out too much about him).
  • The companion’s ties back in their place of origin, and the consequences of traveling with the Doctor for the companion and those around them. (“Aliens of London”, “Father’s Day”, “Boom Town”)
  • The two reasons the Doctor needs companions. (“The End of the World” and “Dalek”)
  • What distinguishes a good companion from a bad one. (“The Long Game”)
  • The drastic consequences of temporal paradoxes, and the justification of the idea that you only get one attempt to change history. (“Father’s Day”)
  • The consequences of careless meddling with history and “setting right what once went wrong”. (“Bad Wolf”)

While it was loud, fast-paced and zany, the new series was clever enough to occasionally employ deconstruction (in the TV Tropes sense, that is, showing a grittier side of a plot device by playing it seriously and realistically). The finale nailed the inherent wrongness of the Doctor just waltzing into a dystopia, removing the reason for its existence, and expecting things to magically get better as he carelessly hops to his next adventure. Looking ahead, I should add it would be even nicer if these themes were consistently followed.

Self-awareness expanded to concepts that were originally intentionally overlooked, of the “elephant in the living room” variety. The pervasive TV SF phenomenon of aliens speaking English, which remains to this day unexplained in the Stargate franchise, not only got an in-universe explanation that was consistently followed on, but became a plot point in a couple of episodes. Regeneration, originally just a plot device invented to allow changing actors, became its own theme explored in detail. (There is speculation that Davies hired Eccleston with the specific intent to change him into Tennant at the end of his Doctor’s arc.)

“Eccleston then apparently released a statement through the BBC, saying that he would be leaving the role at Christmas for fear of being typecast. Fan reaction to the news ranged from disappointment to irritation to outright anger. Some did point out, however, that the series is uniquely suited to deal with cast changes. The number of angry postings on the popular Outpost Gallifrey fan forum was enough for Shaun Lyon, the owner of the website, to close down the forum for two days to allow tempers to cool.”
~ Wikipedia, “History of Doctor Who”

Davies laid the groundwork, the overall thematic direction, and the threads to follow on — which largely continue to be followed, as his successor Moffat has retained the overall format: self-contained adventure-of-the-week episodes with overarching season-long plots and personal arcs for the companions. As a long-term Doctor Who fan himself, Davies has preserved (bar some exceptions) the overall series mythos, going as far as to veto Children’s BBC idea of the near-assured disaster that would a young Doctor series. (The idea of a Doctor Who spin-off for kids, however, survived and became The Sarah Jane Adventures). Granted, this was offset by the creation of Torchwood, whose reception was… mixed, to put it mildly.

A marketing ace, a competent producer, a rebuilder and a preserver, the engineer of Doctor Who‘s worldwide success. Why, then, all the fan hate? Mainly, it stems as a criticism of the one thing that Davies, in charge of Doctor Who, wasn’t good at.

He was not a good Doctor Who writer.

But that requires a second part to analyze in more detail — one that will follow soon enough, where I’ll get to looking at Davies’ writing for the four and a half seasons he produced.

On Apple Software

Posted by lucidfox.org at

As if I didn’t have enough reasons to hate that company already.

I have taken a personal vow not to use any Apple products, hardware or software. However, sometimes I have to interact with less ideologically zealous people, like my father, a “proud” owner of an iPod 5G who now sometimes curses his acquisition.

Previously, at his request, I uploaded a bunch of .m4v videos to his iPod using gtkpod. They all played correctly. This time (in Lucid), there was something funky with mountpoint permissions when I attempted to write to the iPod, so I tried to upload the new pack of videos from his Windows laptop, where he has iTunes installed. While iTunes did upload the new videos, it silently wiped the old ones without any prompts or warning messages.

I don’t know if this was some misguided attempt at customer care, or an active attack against third-party iPod software, but the fact remains: the files would have been lost if I hadn’t kept backups on my computer. Now I’ll have to re-add them.

Apple may be an easy target, but apart from all it DRM crusades, this illustrates my point: if you want to be in control of your own data, don’t use Apple products. As for me, my HTC Hero communicator doubles as a media player (with a nice UI, I should add) at the rare times I actually (gasp!) listen to music. I synchronize the music with it using Banshee, but the file storage uses no arcane filesystem conventions like the iPod/iTunes compatibility nightmare, and music files can simply be copied to the device with a file manager.

The Zoo of Rampant Sexism

Posted by lucidfox.org at

Apparently, the time has come for me to invoke the Unicorn Law.

As a disclaimer, I think the Ubuntu community in particular has been doing a great job in raising gender awareness, and most Ubuntu members I talked to leave a very good impression in this regard. That being said, I only communicate online and don’t know how things go when Ubuntu members meet in person — perhaps things are different there, and ugly incidents may happen.

In general, these days, resources like the Geek Feminism Wiki can quickly name and shame major incidents regarding sexism — and make the problems harder to simply handwave away as systematic patterns are easily seen. At least in the English-speaking world, these issues are easily exposed.

Not so behind the barriers of communication known as “foreign languages”.

Within the Russian open source community, there is an atrocity. No, worse — an Atrocity with a capital A. When seeing the discissions (usually known by a less family-friendly word) on that site, a sane person would be disgusted or horrified, or at best, assume the detached attitude of an observer looking at monkeys throwing feces at each other in a zoo cage.

I’m not going to speak about their attitudes towards LGBT people (myself included) — that kind of tolerance would be, perhaps, too much to demand from this crowd of mostly imageboard-level users. That aside, the wild, untamed sexism in that place is too much to bear. This Russian Linux website linux.org.ru, or LOR for short, is almost completely male-dominated, with only two or so women remaining there who learned to stay detached; the rest are scared away by 1990s-era demands like “tits or gtfo”, talks about “chicks” and “females” (using the Russian biological term reserved for non-human species), and outright doubting their gender and accusing them of being bearded admins.

Even that aside, every news entry that somehow mentions women gathers metric tons of annoying, disgusting, repulsive sexist comments. For me, this one was the last straw. Starting now, I feel ashamed that I ever posted on that site, and withdraw from it. In fact, it almost makes me feel ashamed to be a Russian Linux user.

The thread is about the announcement of Amber Graner being elected. Elizabeth Krumbach had the misfortune of having her name attached to the original announcement, and that’s where the feces hit the rotating air cooler. For a few hours, the news entry (checked and approved by a moderator!) erroneously claimed that Elizabeth announced herself being elected, before eventually being corrected by another moderator. The comments are a whole other story. Ranging from accusations of a “transvestite conspiracy” to utterly off-topic discussions of art and photography, they fit the aforementioned monkeys metaphor to a T. Most of this (almost exclusively male) crowd started discussing and ridiculing Elizabeth’s appearance in a very derogatory way.

Let me cite some specific examples of the general mindset of those users — ones that do not insult a specific person just for appearing in the news.

  • “To make it less scary for the fair sex to enter FOSS development, some men will have to pretend to be women to break stereotypes <…>”
  • “Ooooooo how I miss a woman!!! I want to howl!!! <…> I’d screw them all, but nobody gives me sex…”
  • “I’d do her.”
  • “These ones can cook, and their brains are fine. And they give sex more often, which is important.”
  • “This is what I’m talking about. These dames with negro homosexuals have eaten the baldness out of the normal man. Nobody left to screw.”
  • “Do these chicks not have enough herdness? I don’t understand.”

I’ll stop here — there are much more, but the general mood is clear. This is far from a solitary case, too. The last such news comments, about Valerie Aurora, made one of the two remaining female users temporarily quit the site.

“Get the Facts” Right, Microsoft…

Posted by lucidfox.org at

Usually I don’t pay attention to Microsoft’s “Get the Facts” style propaganda, but this one was so silly that I just couldn’t pass by when pointed to it.

Basically, there are two WMV screencasts “comparing” the easiness of installation of Perl and PHP on Windows and Linux. Notwithstanding the fact that the Linux screencast uses a three-year-old version of Ubuntu and the makers apparently didn’t hear of Synaptic and the Applications menu, what is it supposed to prove? If anything, that it’s easier to type a single command to “apt-get install” a package and get it working out of the box, than to run an installer (predownloaded from a third-party site and hopefully prescanned for viruses before the screencast begins) and making them work with IIS through a configuration window.

Or if it’s supposed to be aimed at Windows users to begin with (“I’d rather click Next into oblivion and then use the command line anyway to set up directories than just install everything with this unintuitive apt-get thing!”), who are they hoping to convince? If anything, it ends up looking like an advert for Linux instead.

Nice job breaking it, heroes.

Dear GNU Autohell…

Posted by lucidfox.org at

…could you please die?

In all seriousness, I don’t understand why in our age of cross-platform considerations, distribution packages, scripting languages and refactoring, so much Linux software still uses a stone-age build system.

I could list the advantages of CMake over GNU autohell… sorry, autotools for hours. I’ll just list the ones I submitted to the gtkpod developer who argued about its advantages, after I wrote a full CMake replacement for its autotools-based build system in one day.

  • autotools only generate makefiles; cmake can generate makefiles, project files for various IDEs, and has (from my experience) better support for hooking into IDEs in the first place.
  • There is only one command to learn to generate makefiles, regenerate the build system after making changes, etc. No need for autogen.sh.
  • cmake is well-documented and easily extensible. For nearly every dependency, you can either find the way to hook it in the base bundle, or find an existing project that has a .cmake file for it. And it’s easy to write new ones.
  • Strict checking of behavior between versions, compared to the constant problems with behavior mismatches depending on which versions of autotools were used to generate the configure script.
  • All configuration is in one place (but easily splittable into included files), rather than all throughout the source tree in various .am and .in files.
  • No difference in the steps to build from the VCS (which has no configure script) or tarball.
  • Includes only the files with relevant configuration and nothing else. autotools installs lots of additional files used in configuration and building, and while it allows one to build without autotools installed, cmake is a single binary available as a package in all major distributions.
  • Arguably more concise, intuitive and easy to learn. This is subjective, but compare the new CMakeLists.txt for gtkpod with its own configure.in and tell me which one you consider more concise and intuitive.
  • Faster, since it, again, only checks for dependencies directly relevant to the build, and caches the results.
  • Supports out-of-source builds. Cleaning up is as simple as deleting the build directory.

The only drawback is that cmake needs to be installed to build the software from the source tarball (autotools don’t even have this advantage for VCS builds). This may have mattered ten years ago, but not in modern desktop systems. Building from source (including installing all dependencies besides cmake) is not a task for the typical end user to begin with – they are expected to use distribution packages. And for package maintainers, cmake is a blessing – very customizable and patchable. I say that as an Ubuntu developer. :)

Next > Last >> Page 1 of 2