Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Submission + - Google Chrome to drop support for H.264 codec. (chromium.org)

nickserv writes: The Chrome development team has announced today that it will discontinue support for the H.264 codec in favor of WebM, Theora and possible future "high-quality open codecs." From the Chromium blog, "Though H.264 plays an important role in video, as our goal is to enable open innovation, support for the codec will be removed and our resources directed towards completely open codec technologies." What will be the short and long-term implications of this move for the future of HTML5? Web developers may now prefer to wait for the dust to settle before re-encoding video for HTML5 so, is this a boon for Adobe's beleaguered Flash Player? One thing is for sure, the move is a bold one.

(My 1st submission here editors so feel free to edit or spice it up as you see fit)

Submission + - What Happened To The Bay Bridge? (sci-experiments.com)

farnsworth writes: Tony Alfrey has put together a fascinating page with some history, analysis, and possible explanations for what ultimately went wrong with the recent emergency repair of the San Francisco-Oakland Bay Bridge. The bridge has been closed for days and is not scheduled to open for days to come, hugely inconveniencing more than 250,000 people a day. His analysis touches in possibly poor welding, possibly a fatally flawed kludge, and a the absence of a long-term fix or adequate follow-up by Caltrans, who are responsible for the bridge. This is a great engineering community, what other info do you have?

Slashdot Top Deals

If God had not given us sticky tape, it would have been necessary to invent it.

Working...