kinetik

My understanding was that a lock free algorithm could still wait for an unbounded time, and what you're referring to are called wait free algorithms.

A nickel.

(ref. http://dilbert.com/strips/comic/1995-06-24/)

In Firefox, open "about:addons" in the location bar, select "Plugins" on the left, then you can disable/remove as necessary.

Original source: http://seclists.org/fulldisclosure/2012/Jul/375

Web APIs for audio are under active development. The W3C has formed a working group where use cases and two specifications (Web Audio API and MediaStream Processing API) are being developed. Chrome and Safari are shipping experimental versions of the Web Audio API now, and Firefox will soon be shipping experimental versions of the MediaStream Processing API (it's available now in a special build). Firefox 4 onwards also includes the simpler Audio Data API. I believe all of these APIs provide sufficient functionality to build the audio portions of media playback with working audio-visual synchronization.

It was moved to the "Web Developer" menu, not removed entirely.

Linux has defaulted to relatime since 2009.

It's coming. There's a spec here: http://dvcs.w3.org/hg/webevents/raw-file/default/mouse-lock....

Implementations for Chrome and Firefox are bug 72754 and bug 633602, respectively.

ANGLE[0] goes some way to solving that.

[0] http://code.google.com/p/angleproject/

So, the next question is: is the container format (MPEG-4 Part 14) patent encumbered?

There are only two things wrong with the header: the RIFF chunk size is invalid, and the data chunk size is invalid.

Firefox does this by default, but its built-in update mechanism is disabled in Ubuntu-shipped versions in favour of Ubuntu's package management.

Open about:memory and see where the memory is going. And if you think the use is excessive, please file a bug including the about:memory data and any details you know that would aid in reproducing the problem.

...8 months before the iPhone was released.

As others have mentioned, the page loads a Java applet. That'd be my first guess at the cause of the crash.

This is great to see. Another step forward for the open web.

HTTP Live Streaming is fairly high latency (2-10 seconds typically), so I very much doubt it's being used for Facetime.

Averaging the results? They probably discard outliers too. Unusually high output is something you'd want to be aware of rather than hiding it in an averaged result.

The linked article seems to refer to an incorrect star. The correct one (which is also named in the BBC article linked from this article) is BPM 37093: http://en.wikipedia.org/wiki/BPM_37093

All in all, the linked article seems like a direct restatement of the BBC article (with errors added), so I recommend you read the BBC article directly: http://news.bbc.co.uk/2/hi/science/nature/3492919.stm

Especially so given Apple's early adoption of SSD.

The title is deliberately misleading. The linked article clearly refers to this being a different project.

Undisclosed? "It's complicated" seems more appropriate in that case.

Pseudo.

It was more like 1,300 HP in qualifying trim and 850 HP in race trim.

That's because it's an extension, not a plugin.

Container parsing: it's not that hard. Besides which, they can use one of the freely licensed existing parsers to solve that problem.

Trick play is already implemented. If you have to do major rework of that area to support a new format, you're doing it wrong.

Amusingly, the password reset tool at iforgot.apple.com still allows six character passwords.

Try updating your video drivers, that sounds like a crash caused by exercising hardware acceleration.

Incorrect. The Cray T3E used Alpha processors in big-endian mode.