Basically they’re saying that H.264 is the superior format but there are concerns that MPEG will begin to levy larger fees for its usage.
The primary concern with Ogg is that it will be impossible to improve it without hitting the wall made by patents from other codecs.
And in the end it doesn’t matter because Microsoft won’t support <video> until 2025, when MPEG’s copyrights are set to expire.
Imported from Last.fm Tumblr by JoeLaz
United States Declaration of Independence (via massivehappiness:un)
Great rhetoric, but also remember this is the Declaration, not the constitution.
Mint’s Justin Maxwell describes a cross-browser solution for trimming long strings using pure CSS (and a Firefox XML binding). How did I not know about this? Already implemented in one project today.
I wonder if “Firefox.next” will be able to print reliably without crashing. Because that’s still a problem in the latest 3.5 builds, along with most of the interface bugs and incorrect OS X behaviors.
But that’s not fun for developers to work on. So they don’t. And the same annoying bugs persist in Firefox for years. Printing hasn’t worked reliably since 3.0. The interface, especially context menus, window placement, and tooltips, has been extremely buggy for Firefox’s entire existence.
They keep making things Awesome™ for the fringe of uber-power-users instead of fixing the common issues that frustrate everyone else and drive average users away from Firefox every day.
I find Marco’s interest in printing to be strange. I’ve never had any problems with Firefox printing, but that probably has a lot to do with the fact that I almost never print anything. Printers seem to be anathema to what Apple stands for.
There are some bugs in Firefox, but Safari has historically been much more unstable for me. I will admit that Firefox is much less polished than Safari, but for the functionality you gain, it’s more than worth it.
I just set up a new Mac and was looking at all my software thanks to an awesome software management system called AppShelf. I saw all of the software had virtually the same licensing system.
I was thinking, the OS X operating system offloads a lot of programming requirements from the developer to the operating system. The most relevant to my thoughts has been the keychain. For those who are unaware the keychain on the mac, securely stores passwords for applications to use without the developer having to create their own secure storage system.
What if Apple was to develop an API to allow for a system based licensing system. This would allow for developers to use a robust licensing system for their software.
The downside of this is that it would provide a single point of failure. It would probably also be overly onerous, being a pain for users. On the upside it would allow for easier portability and management of software. You wouldn’t have to re-register after uninstalling and reinstalling.
Let me know what you think of something like this?
My friend Gareth comes up with some great shit to share on facebook
This is how I plan on showing my respect.
sigh… firefox doesn’t understand that the only reason anyone would ever use
text-shadowis to compensate for the terrible rendering of light text on a dark background.same property applied in both browsers:
text-shadow: #000 0 0 0;
The top is more readable to me but inconsistent rendering is an issue.
