Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Comment Re:Why not just base it off Debian? (Score 1) 109

Debian unstable (sid) - up-to-date, but unstable

Sid isn't as up-to-date as the name suggests.
My biggest issue with Debian is that it's only a cyclical rolling release, not a true one. When the feature freeze comes 'round, it affects sid as well as testing. Keep in mind that the freeze lasts for 6+ months (the current one has been 8 so far - http://wiki.debian.org/DebianWheezy), and happens once every 2 years; at least 25% of the life cycle is spent in freeze. This is equivalent to being stuck on the previous release of Ubuntu. e.g. I'm still using KDE 4.8, despite 4.10 coming out last month.

Freezing makes sense for testing, since it becomes the next stable, but there's no reason that sid/unstable should be frozen as well.

Comment Re:Because it isn't ergonomic (Score 1) 298

Squishy doesn't necessarily mean soft - tactile feedback is different to actuation force.

I used to have a Microsoft Multimedia Keyboard, but after half a decade of use, the keys became so stiff that it started hurting my hands to type with it. I tried buying one of the newer Microsoft keyboards to replace it, but the tactile feedback was so horrendous I returned it immediately. I bought a mechanical (Das) keyboard shortly afterwards, and it actually had a lower actuation force that the Microsoft keyboard, and my typing speed has improved significantly since I got it.

I agree absolutely that you need a decent keyboard if you want to type quickly, but I question your assessment of actuation force; I'd say it's more a matter of preference.

Comment Re:Canonical swirling down to irrelevance. (Score 1) 354

Same here. Debian Sid is great when Testing isn't frozen, but then it stops being fun for far too long. If I wanted to run Stable, I'd run Stable, and if I want to run a rolling distro, I'd rather not run some slow-moving, semi-stable slush.

Seconded. I've heard aptosid improves things slightly, but a lot of the packages I'm interested in aren't there (e.g. KDE). I've considered setting up a VM to automatically source packages from the Ubuntu repos and recompile them for Debian - not sure how well that would work. (If there's an existing repo that does this, please let me know.) Even a list of repos like this one would be quite useful.

Comment Re:IP Address, Car... (Score 1) 189

There is a flaw in this analogy that none of the sibling posts seem to have picked up on: only one person can (legally) display a given number plate / be in control of a car at once, whereas multiple people can and do share IP addresses. A better analogy would be "just because a person is on a bus does not mean they are guilty of infringements committed on that bus."

Comment Re:Anyone who doesn't think that... (Score 1) 1313

So, when there's not enough work to go around, what do we do? Do we let 98% starve (lazy bastards), 1% work as slaves and then 1% live like God-Kings? Do you know an alternative? I'm anxious to hear a solution that doesn't boil down to socialism.

What's wrong with socialism? It seems to be working fine for the Nordic countries.

Comment Re:Will they be releasing source? (Score 1) 107

Ubuntu has been surprisingly close to the chest on this effort. I haven't seen any source code come out for this, or for their Ubuntu for Android work. If they release the source for this, it will be ported to a plethora of devices in a very short time period. There is a very active community of developers on xda-developers.com who would be all over this.

So it makes me wonder, if they plan on releasing source at all, or if this will be some closed-source fork, and thus useless.

There's not much that needs to be ported, really. All the Ubuntu-specific stuff is in userspace, so it can be used as is or with a recompile at most. The bit that differs between phones is the kernel, and that's where the bulk of the effort will be in targeting other phones (either in modifying the Android kernel to function like the mainline Linux kernel, or merging the drivers into the mainline kernel).

Comment Re:Not a problem with Ubuntu Phone (Score 1) 92

Gnome used C because there was and is a large group of people who hate C++ and think C a superior language to develop in. It wasn't anything to do with avoiding competition for developers.

I never said that they made the decision for that reason; simply that that was the reason it happened. If KDE had used C, it's likely that many of the people drawn to Gnome during its formation would have been those who preferred C++.

Comment Re:Not a problem with Ubuntu Phone (Score 1) 92

Why do developers seem to pick technologies based on that they ARE NOT what the other guy uses, rather than what benefits they provide? This seems to be the hallmark of the GTK-ish community.

The GTK community was created around that very notion. KDE pre-dated GTK, but used the Qt framework which at the time was published under the controversial QPL (it wasn't until 2000 that Qt was published under the GPL). GTK arose partly as a response to this, and since KDE used C++, using C mitigated the risk of the two projects competing for developers.

The more two competing open source projects use the same technologies, the less distinct their identities. Whether this is a good thing or not depends on how much diversity you prefer.

Slashdot Top Deals

Avoid strange women and temporary variables.