Since I wrote about the H.264 vs. WebM a year and a half ago, basically nothing has happened. WebM has been cordoned off to test implementations of Aurora/Chromium and never slipped out to the public eye. No precedents have been set, no patent infringement cases, no royalties paid. Beyond the web, H.264 is exploding and WebM is growing flaccid. Where is WebP?
In my previous post, I declared Mozilla was in a tough spot due to patent infringement and lack of indemnification no matter which way they turn. That still seems to be the case, but as Ars puts it, pragmatism is beating out idealism and Mozilla is dipping a toe into the H.264 water (with B2G as a testbed, sigh). But still, this is a good thing and we’ll all be better of for it.
Better hurry and decided on something. That 2022 deadline is approaching fast. Or is it 2014?
The WHATWG just needs to take over.
The link:
Predictions for 2012
The meat:
I have none to offer.
People who really know what is going on are not going to prognosticate in public. Secrets will be held, profits will be made.
Posted from San Diego, California, United States.
The link:
Amazing Kickstarter Project Twine: Cheap and Easy Internet of Things
The meat:
The sensors, so far, include an temperature sensor and an accelerometer – with external sensors planned, including magnetic and moisture sensors.
I had imagined nano-particle magic dust… but we’ll have to wait until IPv6 for that. This is a great concept, but the devices are a bit bigger than I’d like. The day is coming and this is a great start.
Posted from San Diego, California, United States.
The article:
The MicroPHP Manifesto
The meat:
Finding lightweight libraries that don’t pull in lots of additional code dependencies is much harder than it should be. Mostly I think that’s attributable to PHP devs being more interested in framework-specific development.
I’m seeing more and more of this “framework-specific development” out there. There are job listings for Symfony coders, Cake coders, Drupal coders (hah), but in the end, isn’t it all PHP with the occasional template engine thrown in? Don’t get me started on template engines for PHP, I think Smarty and the others have left the building with js engines kicking ass and taking names.. More on that later.
Posted from San Diego, California, United States.
The link:
Quality Coding Takes A Break For The Holidays. But Why?
The meat:
For the time period I looked at (the last 24 months), January through September is relatively flat and in line with the average flaw density. Then, there is a big bump in flaw density in October and November. Things begin to settle down once we go into December. The jump in application flaws is easy enough to spot. But what could cause this?
As a commenter points out, this probably has to do with deliveries schedule for Jan. 1. Seems like October and November are big push months with a lot of testing/debugging. December is polish and deployment.
Posted from San Diego, California, United States.
Page 1 of 2212345»...Last »
