Linked by Kroc Camen on Thu 29th Apr 2010 23:04 UTC
I am almost flabbergasted by the spin and blunt-face upon which this news is delivered. We were just discussing the pot calling the kettle black with Apple / Adobe and now Microsoft have also come out in favour of a closed video format for an open web--IE9's HTML5 video support will allow H264 only. Update Now that the initial shock is over, I've rewritten the article to actually represent news rather than something on Twitter.
Permalink for comment 421767
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 15:53 UTC
The new WebKit Opera for Android has been released. "Opera 14 for Android is built on top of Chromium 26, with a total overhaul of the UI in native code, making it fit well with the latest Android design guidelines. Go get the build from Google Play or point your browser to m.opera.com, and give it a spin!"
Linked by Thom Holwerda on 05/20/13 22:43 UTC
The Verge pointed me to a blog post by Leap Motion - which reveals how their Kinect-like motion control works with Windows 8. "From the second you plug in your Leap Motion Controller, you'll be able to browse the web and interact with your computer just by moving your hands and fingers in the air. With Leap Motion technology and Windows, you can do everything that's possible with multi-touch inputs - without actually touching anything. This also means that existing applications in Windows 7 and 8 will respond to your natural hand and finger movements. Soon, we'll show you how Leap Motion will work with Mac OS X." Quite cool.
Linked by Thom Holwerda on 05/20/13 21:50 UTC
PocketNow interviews Marc Dillon, and there's an interesting note about why Jolla is keeping the display properties under wraps: "We're leaving some of those details out because we do understand that there are a lot of really big players in the market and they tend to take certain components in the market and dominate them. We created the ability to actually be able to run Sailfish on multiple hardware displays and be able to swap components, so this is part of the demand and supply planning phase. We are committed to this industrial design which is a 4.5-inch display, an 8 megapixel camera on the back and a front-facing camera at the front, and the exact specs of the display we'll provide when we're close to delivery." Something you rarely hear anything about.
Linked by Thom Holwerda on 05/19/13 23:15 UTC
"This is my NeXTstation Turbo Color booting the Mac System 7.1 Operating System using a hardware add-on called 'Daydream'. The Daydream has a Mac ROM and a few custom ICs in it and hooked up to the NeXTs DSP port. Turns your NeXT into a full fledged 68k powered Mac." So cool.
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
"The NetBSD Project is pleased to announce NetBSD 6.1, the first feature update of the NetBSD 6 release branch. It represents a selected subset of fixes deemed important for security or stability reasons, as well as new features and enhancements. Please note that all fixes in the prior security/bugfix updates (NetBSD 6.0.1 and 6.0.2) are also in 6.1."
Linked by Thom Holwerda on 05/18/13 21:06 UTC
"At the end of a week in which Electronic Arts confirmed it wasn't developing a thing for the Wii U, one of the software engineers in EA Sports' Canada studio, in a series of since-deleted tweets, disparaged the console as 'crap' and suggested Nintendo should give up on hardware altogether. 'The Wii U is crap. Less powerful than an Xbox 360. Poor online/store. Weird tablet', tweeted Bob Summerwill, listed as a senior software engineer at EA Canada, in a reply to a tweet posting a link about EA's no-Wii U news. 'Nintendo are walking dead at this point'." The Wii U is turning into the 21st century's Virtual Boy.
Linked by Thom Holwerda on 05/18/13 7:37 UTC
"In NixOS, the entire operating system - the kernel, applications, system packages, configuration files, and so on - is built by the Nix package manager from a description in a purely functional build language. The fact that it's purely functional essentially means that building a new configuration cannot overwrite previous configurations. Most of the other features follow from this." Interesting approach. A Linux distribution, sure, but with some very refreshing ideas about system configuration.
Linked by fran on 05/18/13 1:38 UTC
Appfour added, among other features, C/C++ support to its new version of AIDE. From Android-IDE, "Now you can write parts of your app or your whole app in C/C++ on your device. AIDE supports the Standard Android NDK toolchain (GCC 4.6 + Bionic, STL, ...). No changes are necessary if you want to build an app developed on a PC with Eclipse. C/C++ development is fully integrated: Build errors appear in the error list and files can easily be navigated to with Go to file. The editor supports C/C++ syntax highlighting."
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Ars nails it: "The answer is that Google did announce what amounts to a fairly substantial Android update yesterday. They simply did it without adding to the update fragmentation problems that continue to plague the platform. By focusing on these changes and not the apparently-waiting-in-the-wings update to the core software, Google is showing us one of the ways in which it's trying to fix the update problem."
Linked by MOS6510 on 05/17/13 22:22 UTC
"It is good for programmers to understand what goes on inside a processor. The CPU is at the heart of our career. What goes on inside the CPU? How long does it take for one instruction to run? What does it mean when a new CPU has a 12-stage pipeline, or 18-stage pipeline, or even a 'deep' 31-stage pipeline? Programs generally treat the CPU as a black box. Instructions go into the box in order, instructions come out of the box in order, and some processing magic happens inside. As a programmer, it is useful to learn what happens inside the box. This is especially true if you will be working on tasks like program optimization. If you don't know what is going on inside the CPU, how can you optimize for it? This article is about what goes on inside the x86 processor's deep pipeline."More News »
Sponsored Links
Member since:
2005-07-12
A point I've made over and over again. There is ZERO legitimate excuse for not supporting whatever codecs the host OS has installed apart from lazy developers... and yes, in my mind that includes the 'alleged' security issues. (Chrome has been proving that a lie it is with it's sandboxing of just about everything! Sandbox the **** codecs too!)
This is doubly true for Windows - if they were making it cross-platform they could at least use that excuse; but it's a bit likely not even making an XP version of IE9 just as they didn't make a 2k/98 version of IE7 & 8. Every other browser maker can code cross-platform; this isn't even a REAL cross-platform issue!
That they are even TALKING about what codecs to support/not support in each browser with the VIDEO tag is pure bull - and frankly should be enough to send most developers back to the intent of HTML 4 STRICT / XHTML 1.0 STRICT; SIMPLIFYING the specification by having just ONE tag - OBJECT - replace APPLET, EMBED, IMG, etc... So with HTML5 do they finally ride Microsofts case about not implementing OBJECT properly, or do they tack on even MORE tags that nobody is going to bother using?
All this in-fighting malarkey about what codec is in the specification is just more of the bullshit that HTML5 is being turned into. Honestly, I'm so fed up with it I have NO PLANS to code websites in HTML 5 until sometime around 2020 if ever.... It's the exact OPPOSITE of all the progress STRICT gave us - people can't even be bothered to learn how to use TH, CAPTION, LEGEND, FIELDSET, LABEL, ACRONYM - **** sake the only people who even try to use ABBR are the microformat junkies; so to make it even 'better' let's slap on a bunch more 'new tags' that are nothing more than overglorified DIVisions and replication of **** we can already do with less tags? Yeah, right!
HEADER - we have heading tags, we don't need more of them. Silly bull for people who can't bother learning proper heading orders... or just for people who don't realize that just like not every ejaculation needs a name, not every element needs a DIV wrapped around it.
NAV - Not just another extra wrapping element around UL's for no good reason, wouldn't it have been simpler to undeprecate MENU?!?
Etc, etc, etc...
A recently departed friend of mine
http://www.danschulzrip.com/
Used to make the joke that the same people who made endless nested table rubbish layouts now just make endless nested div layouts - net change zero.
I get the feeling much of HTML 5 seems like little more than legitimizing the use of excess containers around elements that don't need them - net change zero. I'm half hoping crap like this codec nonsense will lead to the eventual implosion of HTML5 so we can get back to it's original intent of making it SIMPLER, not the overcomplicated train wreck it's devolved into when compared to it's immediate predecessor.
NOT that anyone bothers using STRICT... much less use it PROPERLY. See Youtube's alleged HTML5 demo which was little more than slapping the VIDEO tag into a non-validating XHTML 1.0 tranny document - that's NOT HTML5... or the nutjobs running around with HTML 5 demo's that barely use HTML5, don't use it properly, then claim to use and be about CSS3 - with NO TRACE of any ACTUAL CSS3. News flash, -moz and -webkit are NOT CSS3 properties.
How many idiots can there be... they say it's 1 out of 3...
Edited 2010-04-30 10:36 UTC