Follow Slashdot stories on Twitter


Forgot your password?

Comment Re:There may be some at a loss for sympathy (Score 3) 693

a lot of what the GNOME hackers do, goes into the base for many other projects as well.

I think a lot of the hostility comes from seeing GNOME developers take an actively hostile attitude to non-GNOME projects using components like GTK+ that we used to think of as vital infrastructure everybody used.

Comment Re:Nine, eh? (Score 1) 153

The Mozilla Suite (codenamed "SeaMonkey") was discontinued. A new project, outside of (but not on bad terms with) the Mozilla Foundation, was started to continue development under the name "SeaMonkey" (now as a brand, not just as a codename). As far as I know, they use recent upstream versions of Gecko and thus automatically support HTML5 and so on.

This is only confusing to people who followed Mozilla development closely enough to have seen "SeaMonkey" used to refer to the Suite. I'd guess that it was somewhat inspired by the origins of the Mozilla project - "Mozilla" was the old codename for Netscape Navigator.

Comment Re:Countries do this all the time (Score 2) 245

True, but Switzerland takes it up a level. Permanent tank traps in farmers fields, hidden military installations all over the country, bomb shelters, and a huge military reserve with regular training.

It seems to work for them, though. How many countries have had nearly 200 years of peace?

Comment Re:Dumb Management (Score 1) 205

Canonical decided to write their own Mir display server instead of adopting the existing Wayland. They stated their reasons for doing so, but I'm not convinced they really had to start their own project instead of modifying Wayland.

The nice thing about Wayland is that, because all the real work is being done by things like evdev, KMS and widget toolkit the actual display server is *much* simpler than Xorg. Weston is only a reference implementation of a Wayland compositor, and it's expected that desktop environments will implement their own that work the way they want them to (for example, work is underway to let KWin function as a Wayland compositor).

So it's not even a question of having to do some hackish modification of upstream to get their own way - they could have just implemented Wayland in Unity's WM, like other major DEs have done. The concerns about running on Android drivers are weird - the Wayland protocol doesn't care how you actually do your compositing and display the finished screen (there is already a modified version of Weston for the Raspberry Pi, which uses the device's video scaling hardware to do the actual composition work), so a seperate client protocol (as opposed to rendering backend) makes no sense.

Comment Re:BS Detectors at Maximum, Mr. Sulu (Score 1) 433

(Apologies if the linked video is edited and does not include the quote - I'm on mobile right now and haven't watched that copy. Search for Patrick Clawson to find the rest.)

Comment Re:New MP isn't great for big jobs (Score 1) 372

Flash drives seem to be characterized by very high failure rates. Changing the drive? Unclear this is a user operation. All real drives -- the ones you use for your data -- would have to be external bricks.

Hard drives are also prone to high failure rates. If your "real data" lives only on a single magnetic disk (in a portable device, FFS) you're already asking to lose it.

Two is not equal to three, even for large values of two.