$ aptitude show gnome-session-fallback
[snip]
Description: GNOME Session Manager - GNOME fallback session
  The GNOME Session Manager is in charge of starting the core components of the
  GNOME desktop, and applications that should be launched at login time. It also
  features a way to save and restore currently running applications.

  This package contains the required components for the GNOME 3 fallback session,
  based on the GNOME Panel. It can be started from a display manager such as GDM,
  and doesn’t have specific hardware requirements.

The GNOME 3 fallback session uses the same interpretation of the desktop metaphor as GNOME 2 (the panel). I think it shows up in the DM session list as ‘Gnome Classic’.

I've been using KDE as long as I've been using GNU/Linux (~7 years), and Kubuntu as long as I've been using an Ubuntu-based distro. I still love KDE.

That said, I've installed Unity/Oneiric on my secondary/guest computer in the main room, and I'm very impressed with it. I think it's a really cool system. I'm comfortable using it, and I'd recommend it to anyone. I like it much better than Gnome. You should give it a shot. Just install it alongside KDE and log into it once or twice to try it out.

Thank you! Finally someone who gets it. We can't pretend that services like healthcare are free, but at some point we have to acknowledge that a for-profit healthcare system can only succeed by maximizing revenue and minimizing payouts — i.e., by providing as little actual healthcare as possible.

There is plenty of space between recognizing that the capitalist model doesn't succeed in providing certain services on the one hand, and magical thinking about ‘free’ public services on the other.

That's kind of the point of a combative (that may not be the correct legal term) justice system. Each lawyer does everything they can for one side, and hopefully the truth comes out when they each push one-sided versions of the story. Each attorney only gets to select two persons to be removed from the jury. I'm not sure how big the jury is, but the impact should not be huge. The goal is to remove people with biases which would prevent them from ruling fairly. I guess it's supposed to prevent things like mistrials, based upon the idea that there will only be a handful of people with extreme, relevant prejudices in any jury pool.

I'm not sure I totally agree with that reasoning, but I don't think your characterization of it was very complete or fair, either.

As silly as this sounds, there are actually reasonable times this should happen. Depending on the local law, legally blind persons can keep or earn a driver's license provided that they go through some approved adaptive driving program. These programs involve the use of accessibility devices like special glasses featuring mounted bifocal binoculars (yes, they are as hard to use as it sounds). Without these devices, the driving would be both illegal and unfeasible. In an effort not to lose them, I'd imagine most legally blind people, not much suited to searching for things, leave them in the car rather than take them inside to work or wherever they go. (I know some people who leave them in their car just to avoid the stares.)

This all sets you up for a situation where a legally blind employee (without an assigned parking space) who drove to work exits the building, enters the parking lot, and has a very hard time finding their car. If employees of their rank don't usually get designated parking spaces, depending on the size of the campus, this can be seriously hopeless. It seems to me that the easiest thing to do in that scenario (esp. granted that they have a registered disability since they need to go through some registration process to even get their special driver's license) is to just give them a handicapped space. Being closer to the building is also helpful.

There's also the case that the legally blind person isn't even the driver or car owner. Think of the wheelchair painted on those spaces: does the person in the wheelchair always (or even usually) actually drive that car?

(Sorry for strangling your joke.)

Resizing a terminal causes hard lockups with version 270.* drivers on my machine. It happens not only on Konsole, but also on Gnome Terminal. Apparently drivers, especially newer drivers for newer cards, can do some very strange/bad things in response to normal API calls. It happens, and it's not the KDE or Gnome developers' job to work around it, mostly because it's not even their job to own Nvidia hardware. That said, ordinary users and developers of these desktop environments do work hard to (a) provide workarounds and explanations to ordinary users and (b) determine the precise nature of the problem and work with upstream driver developers to resolve issues. Many an Nvidia driver bug has been hunted down by developers on downstream projects like KWin.

In any case, simply working around non-compliant behavior on the part of upstream libraries and drivers is never the right thing to do. All that creates is some kind of bizarre shadow-API that developers have to then learn by trial and error. Another important point to consider here is that much of the time all it takes to solve the problem is simply to revert to an older version of the very same drivers. When a new version of an Nvidia driver introduces problematic behavior during typical application use that was previously benign (as in my case, with the terminal resize hard freeze), it's absurd to hold downstream developers responsible for that.

This. I did some bitching about specialization ruining the cooperative capacity of today's workers, and this is probably the best solution to it. We need managers who are good at managing, but have at least enough experience with the work of their team to be sympathetic to their workload, and in better cases, a realistic understanding of it.

There's nothing evil about business skills, but there is something terrible about a very narrow skillset.

I think you hit the nail on the head here. What a business needs in terms of management is someone who isn't necessarily a geek at all, but simply someone who has respect for the work of those he manages, even with an understanding that it is different work. Geeks likewise ought to accommodate their managers, knowing at least that as empathetic as their own manager might be, he has to answer to people that are even further abstracted from the problems sitting on the geek's desk.

Truly, it's specialization that's killing us. The lack of support for generalist studies in today's society leaves most of the population unable to understand, or even merely perceive as valid, the work of others. Geeks might actually be the worst offenders here. Being a computer science major and a philosophy minor (I highly recommend the studies of semantics and philosophical logic to all people interested in compuer science), I see this a lot in my computer science peers. We need to remind ourselves: our skills are not the only useful skills; our paradigms are not the only valid paradigms.

I agree. I'm not much of a visual learner myself, so maybe I just can't appreciate it... I feel like an asshole for saying it, but Scratch looks to me as if it is quite literally child's play, and totally out of place in a university. I would be more inclined to simply teach students to draw their own diagrams when planning out their design, but maybe that's supposed to be some of what this software does.

I just don't know. Anyone can be tripped up by a new concept just because of that novelty; someone currently struggling to understand programming concepts may go on to be a good programmer. But what kind of a programmer does a student become when that struggle to understand would have caused them to quit if they hadn't been given this 'drag and drop programming language'? Who wants to work with the guy who gives up unless he's spoonfed to this degree? The stated purpose just seems wrong.

Well, those things really belong under two different degree designations: Computer Science and Software Engineering. In either case, the electives should leave you some room to place additional emphasis on either the practical or the theoretical.

It's also here on my installation of Ubuntu Natty, but it still doesn't actually _fix_ any errors, although it's happy to tell you about them. :-P

But it is good to see that it exists in some form by now. :-)

I've actually been running the system I'm typing from with Btrfs on the root partition for some time now. Since I always have an ext2 /boot partition, I didn't have to worry about this.

I still wouldn't recommend using Btrfs for / unless you have a separate /home partition, though: there is not yet any fsck.btrfs! In addition to a separate /home partition, I'd recommend having another Linux install with ext4 alongside it, so if something does go wrong with your Btrfs partition, you can boot a fully functional OS without having to reach for a LiveCD. That said, the Btrfs filesystem has handled several hard shutdowns without issue (there's some problem with my Nvidia graphics card that's been causing intermittent/unpredictable hard freezes, impervious even to the Magic Sysrq key).

The cool thing about using Btrfs for the root partition on an ordinary system (this is why I'm trying it) is for fast, transparent filesystem compression. I have an OLPC XO-1, and a bootable FSF membership card, neither of which has much free space. The traditional solution to such space issues is to have a SquashFS (read-only) root partition to save space, and use a persistence file to store changes. But if the changes become too great, the persistence file will reach the size of the partition that holds it, and you have to recreate the SquashFS image to start using the system again. While the compression factor isn't quite as good for Btrfs compression (it can do gzip and lzo), it's still very handy when trying to get a full system into 2GB, and it lets you have read-write access with good performance, too.

Fair enough with regards to WebM vs H.264, but its worth noting that due to numerous patent restrictions, there are significant legal obstacles for WebM to overcome before it can acquire feature parity with H.264. It's not as simple as a failure on Googe's part to devise a technically equivalent format, but to develop one that matches H.264's capabilities while circumnavigating patent landmines from proprietary video technologies including H.264 and others. It may not be feasible to create something that remains free-as-in-freedom, unambiguously non-infringing on the patents of others, and technically superior to H.264 without some major innovation in video compression algorithms that is either originated in F/OSS, or explicitly placed in the public domain, or something similar.

Incidentally, KDE 4.5 introduced tiling support for kwin. So KDE's WM *is* a (basic) tiling window manager.

With the release of KDE 4.6, KDE has also finally incorporated oxygen-molecule, which is a very complete Oxygen theme for GTK+.