Neither the NeXT nor OS X UI toolkits have ever asked you to specify pixels. They specify everything in PostScript points.

They're still not offering a retina external display, but they're about the only manufacturer that isn't. I just got a 4K 27" display at work (and I'm now back to preferring to read text on the big screen instead of on the laptop screen). The panel quality is nice, but it lacks any bells and whistles. They're only £300 now though, so we're buying them as the standard external displays.

You know that OS X comes with ipfw, right?

Why remove the vertical scrollbars when a mouse is not connected?

Because 99% of the time, that's also when the big external screen isn't connected. I quite like this feature.

It will be interesting to see reviews from all those people who spend most of their day running Pro Tools, Ableton, Final Cut Pro, etc. Anything which reduces screen real estate for those people will be an undeniable net loss.

In the mean time, you can still listen to this.

(Yes, Mike Oldfield is an Arthur C. Clarke fan in case you hadn't guessed.)

Mind explaining this? Cock on close vs cock on open, taking advantage of the more naturally forceful movement?

You can get sued anywhere. Your chances of prevailing in court are astronomically higher in the US.

There are a lot of things wrong with the American legal system, but its attitude toward free speech is not one of them.

Direct3D 10 is very different from DirectX 9. The latter was designed with modern GPUs in mind and so is based around an entirely programmable pipeline. DirectX 9 is predominantly a fixed-function API with various places where you can insert shader programs into the pipeline. This means that DirectX 10 is easier to support because there's less provided by the API.

Supporting D3D 9 is akin to supporting OpenGL 2. You need to expose most of the programmable interfaces but also have a load of fixed-function stuff work, typically (on modern hardware) by providing shader programs that do the same thing. Supporting D3D10 is more similar to supporting OpenGL 3, where most of the complexity is in moving data to and from the GPU and compiling shader programs.

With Gallium, there are two aspects to supporting these APIs. The first is the compiler turning programs from a source language (HLSL, GLSL) into TGIR. The second is the state tracker, which handles API-specific state. The former part is about as complex for D3D 9 and 10, as they have similar shader language support. The latter is a lot simpler for 10, as it is a much less stateful API.

Which still sounds odd to me. I'm running Gentoo on my main desktop (Mint on my laptop) and have never installed systemd. I've decided to stick with OpenRC. GIMP works fine here and I do have dbus installed.

It seems this dbus dependency is not an unsolvable problem.

You will note that the censored phrase is "metric sh*#load". That's because the US still uses imperial f*$ktons.

This.

I do concede that a key word is "most", though a slightly stronger phrase like "the vast majority of" would also be appropriate. There are a very small number of software patents which I would (grudgingly) agree are probably legitimate, like RSA. Software patents like that are remarkable precisely because they are extremely rare.

I don't care if the plane I'm on departs on time, as long as it arrives on time. I've been in a situation once where changing winds meant that delaying takeoff allowed the plane to land earlier. I don't recall anyone on the flight being upset with the decision to depart a bit later...

A navy ship, what about a cruise liner? With cheap energy, you could process the deuterium from sea water for fuel, grow food in artificially lit enclosures below decks and have a self-sustaining artificial ecosystem that could spend years between trips to port.

I was more wondering if they partnered with Bussard's company. The sizes sound similar and Bussard was DoD funded.