August 2008

You are currently browsing the monthly archive for August 2008.

Comcast has decided to impose a 250GB/month limit on their customers. I have a lot of friends that use Comcast for their internet service provider and are likely to hit this limit, even counting fully legit data. Linux isos aren’t small. And I know that I do a lot of backups and whoisi testing that uses a decent amount of bandwidth. I’m sure I’m well past this limit. [ Note: I am a very happy Verizon FIOS user. ]

But the real story is about what this does to competitive video services. Want to get access to better, lower-cost video than Comcast cable service from somewhere like Amazon, Netflix or Hulu? Nope, welcome to the world of false scarcity. You will use their video service and you will like it.

Om calls this “the enemy of innovation” and he’s right. Part of the explosion of video, services and data via the web has come because of the growth and availability of broadband into people’s homes. What this says is “growth is fine as long as it doesn’t compete with our video offerings.”

I am reminded of the oldest story of this behaviour when AT&T didn’t want to support the Internet because they didn’t want competition to their proprietary long haul services. And rightfully so. It’s a good thing that AT&T didn’t win that battle, right?

Also, they list how many pieces of email you can send with a 250GB limit. (Huh? Seriously?) I wonder how many youtube videos or hulu videos that amounts to. Anyone know the avg size of one of those? That might make for a more interesting number.







Via the ever-wonderful Andrew Weissman who echos someone who has a somewhat more sarcastic approach than I prefer to music, manufactured or not. Description of the band, the band page, single on amazon and a myspace band page.

Enjoy!

Update: Sigh. I keep thinking it’s Friday. It’s not. I know.

David Humphrey has a post up about the upcoming Mozilla Toronto DevDay. It’s taking place on Monday Sept 15 and Tuesday Sept 16 and is worth checking out if you’re in the Toronto area.

unread on whoisi

I’ve added a new feature to whoisi. It will now keep track of things you haven’t seen:

To see the new items in your follow stream click on the link like the one above that says “318 Unread.” When you’ve read them, click on “Caught Up” and you’re returned to the normal follow page.

Note that right now the update count is only updated when you visit the follow page. And it takes too many clicks to figure out if there’s new unread content and to view it. I’ll be working on that shortly, but having the early feature in place makes things much more useful.

Enjoy!

There have been a pile of posts about the TraceMonkey code that just landed in mozilla-central. mozilla-central is the source code repository we’re using in the lead up to Firefox 3.1. Here are some posts if you want to read about it:

The heart of the story is that we’re seeing performance increases on benchmarks of anywhere from 1.8x to 37.5x depending on the benchmark used.

But the thing that most people don’t realize is that you can take advantage of the work that we’re doing in SpiderMonkey in your program as an embedded JS interpreter. It’s a pretty tiny engine, has a relatively stable API and even has useful documentation. John’s post contains four commands that you can use to build the engine. In fact, it’s so short, I’ll re-paste it here:

hg clone http://hg.mozilla.org/tracemonkey/
cd tracemonkey/js/src
make -f Makefile.ref BUILD_OPT=1
Linux_All_OPT.OBJ/js -j

And you’re in a command line JS interpreter. No fuss, no muss.

Many people don’t realize it but most of what people think of as JavaScript is the browser API, not the JavaScript language. To quote from the JavaScript C Engine Embedder’s Guide:

The word JavaScript may bring to mind features such as event handlers (like onclick), DOM objects, window.open, and XMLHttpRequest. But in Mozilla, all of these features are actually provided by other components, not the SpiderMonkey engine itself. SpiderMonkey provides a few core JavaScript data types—numbers, strings, Arrays, Objects, and so on—and a few methods, such as Array.push. It also makes it easy for each application to expose some of its own objects and functions to JavaScript code. Browsers expose DOM objects. Your application will expose objects that are relevant for the kind of scripts you want to write. It is up to the application developer to decide what objects and methods are exposed to scripts.

The Embedder’s Guide does contain a lot of good information you can use to get started embedding SpiderMonkey into your application. It’s worth a read if you’re looking for a decent scripting engine for your app.

Gecko has long been a leader in supporting web standards but it’s always been hard to tell what we’ve added, when we added it and when it might hit a release. We’ve set up a new web tech blog for people to post about new features in Gecko.

Once nice thing about this blog is that anyone who has commit access to the mozilla hg repo can make a post about a new feature. We’ve hoping to see a lot of great content on that blog. Subscribe and enjoy!

If you have the time I strongly suggest that you take some time and listen to the second edition of the openweb podcast. This episode should really be called the “Brendan show” because he does most of the talking. But if you’re into JS or you’re into programming languages in general it’s worth the listen. There’s lots of discussion of the trade-offs that went into the new ECMAScript Harmony effort and why ES4 and the ES3.1 efforts were rolled up together.

Arun also put up a post on the topic on the Mozilla Standards Blog that’s worth reading. But the podcast is particularly good. Especially if you want to know where the Web is going.

Since Stuart landed the Qt port into mozilla-central the other day and Ryan Paul wrote an article on Qt and Mozilla I thought it might be worth it to add some context to that work.

Ryan’s article contains this quote from Nokia developer Oleg Romaxa:

“Nokia will use the best browser for the job,” he said. “Currently, we cannot make a full-featured and integrated browser with WebKit in mobile. But with Mozilla, we do not need to do anything, we can take existing models and API’s which are available. Also, NPAPI support is already in the Gecko web rendering engine. They are also concerned that WebKit is, to some extent, controlled by Apple, who are in competition to Nokia with their iPhone.”

There are a few important things to note here. First, that Mozilla is the complete package. We’ve got everything that you need to implement a browser. Disk cache, integrated (and well tested!) networking, a super-fast JS implementation, an XML UI markup language (XUL) and a brand that regular humans recognize. Those things mean you can get to market faster as a mobile integrator or developer instead of having to create them yourselves again.

Second, our neutral stance. We believe in the web over any particular platform. From Nokia’s standpoint if you’re building on the same technology that one of your major competitors is leading vs. working with someone who absolutely wants a web browser to succeed across all of Nokia’s platforms – which partner would you choose? I’ve often said “pick your partners carefully” and this has to be an important part of any technology decision making process.

There’s also another interesting flip side to this: who is WebKit’s other major competitor? Apple itself. Just like Microsoft’s push to get Silverlight out in the world, Apple wants people to write apps to their native platform. In this case, the iPhone. Given the strategic value of the native platform as part of Apple’s offerings, their investment in WebKit will (or at least should) always lag behind. We’re investing everything we have in the web and our platform and it’s starting to pay dividends.

And since I have your attention here are two other very interesting checkins: GTK+ and directfb (which people are actually building products on) and worker threads (ala Gears.)

Look at our current (and planned) platform support: win32, windows mobile, win32 + qt, mac OSX, linux + gtk2, linux + qt, qt embedded, linux + gtk2-directfb, x86, ppc, arm. We’re bringing the web to everyone and we’re doing it with a single coherent project with regular releases. That’s what I mean when I say “for everyone everwhere.” The web is bigger than any platform and we’re the embodiment of that mantra.

Mozilla is moving. It’s fast and furious now. And I think we’re just getting started.

[ Update: It was pointed out to me that what I wrote above might be misinterpreted as announcing that Nokia had picked a platform or something similar. Just to be clear that wasn't what I was doing, and as far as I know they haven't. I don't have knowledge about that decision inside of Nokia. Only they know. I was just pointing out what a decision making process might look like and the importance of picking well-aligned partners. And the fact that we're running on more and more platforms these days which is cool as hell. ]

Updated February 22nd, 2009.

I was inspired by one of Gen’s posts and I thought it would be worth it to make a post that contains some links to some great Clay Shirky talks.

Clay Shirky on institutions vs. collaboration at TED in 2005. Even though this was filmed back in 2005 (before everyone knew what flickr was) he’s clearly talking about Mozilla. He doesn’t know it yet, but he is. As Mozilla is an organization that is an open source project, non-profit corporation and volunteer driven organization all the same time I think that we have come to know as instinct what Clay is talking about here.

Clay Shirky on Love, Internet Style. A short but fun video about Love as a building material. It’s great. Watch it.

Clay Shirky at Web 2.0 Expo SF 2008. Clay talks about the Cognitive Surplus that exists in our modern society. It contains this fantastic one-liner: “Desperate Housewives essentially functioned as a kind of cognitive heat sink – dissipating thinking that otherwise might have built up and caused society to overheat.” I’m not sure if it’s the first mention of what has become a famous fact about the amount of person-time required to build wikipedia, but it’s certainly put into great context and is worth watching for this reason alone.

That perspective made me think about how I spent my time at home and is one of the reasons I stopped watching TV and instead created whoisi. I guess you can thank Clay for it. Or blame him. Up to you.

Clay Shirky talking about his new book: Here comes everybody. He talks about the revolution of the Internet, the building of two-way groups and group action. It’s another great talk.

Clay Shirky talking about brands and keeping things human. Lots of good thoughts here on brand and identity and the right way to think about product design and how people interact with your company.

(Feb 22nd, 2009) Clay Shirky talking about low cost coordination and group action.  Talking about releasing data vs. releasing apps on your own for others to consume, changes in labor patterns, experimentation and a pile of other stuff.

John Lilly pointed people at a really good article in the New York Times by John Markoff about the Olympics as a hook to get Silverlight onto people’s computers. It’s a good overview and is worth reading.

The article covers well tread ground: People are worried that Microsoft will leverage its market power to create a leadership position for multimedia on the web. Replacing the (proprietary) Flash video codecs with the (proprietary) Silverlight video codecs and associated tools. In some ways it looks like a battle between two companies and strategies that no one would care about. More lock-in, more proprietary tools, more opportunities to undermine the main single item that makes the web great: it’s open nature. But those companies have existing market reach and they will do anything they can to convert that into even more leverage over how you interact with the web. If nothing else, they will buy their way with cold hard cash onto your computers. These two industry players should be taken seriously.

John Lilly is quoted in the article as talking about the “generative Web” (via Jonathan Zittrain.) I like this phrase quite a bit. I think that might be an even be a better way to describe what we (as in the Mozilla Project) think is the most important part of the open web. That is, by the act of creation on the web you are also creating things that other people can build on. Everything from scraping data to create a search engine like Google to being able to look at other people’s HTML and JavaScript to discover how they do something clever. Transparency and openness creates innovation – innovation by thousands and thousands of people, each of which has a positive impact on the millions who use the web.

Think about it another way. The main metric that I would use to describe the health of a truly open web is this: That as the ecosystem expands, the raw number of people, companies or groups who hold power inside the ecosystem, and can affect its direction, grows as the ecosystem grows. Put another way, the power center is decentralized over time. Change inside of that ecosystem require more voices to agree that change is good. That’s healthy. And that’s an open web.

Then there’s the other side of the metric. That as an ecosystem expands it enhances the power of a single player in the market instead of creating many players in the market. Change in that market requires the permission of only that one player and that one player can make decisions on behalf of everyone who is also part of it. That’s not healthy. And it’s not the open web.

Based on those metrics for health the battle is between those who would expand for the sake of expanding the opportunity for everyone vs. those who would expand for the sake of centralizing their own market power. In one phrase: it’s expansion vs. centralization. That’s what you should be looking for and what you should be thinking about when you hear someone talking about the open web.

All of this is nice, of course, but it doesn’t really describe what we have to do to create the world we want to live in. It talks about the nature of the marketplace but it’s not really a roadmap for people to understand how, as the good guys in this picture, we can continue to compete and win against much larger competitors. I first word in the title for this post is “competing” for a reason. Because that’s what we really need to do.

Recently at the Firefox summit I was reminded in one of Mitchell’s talks about how Firefox is a mechanism. Firefox is the best representation of our vision for an open + generative web that we can come up with: As a rule our users love it, we’ve built an ecosystem of thousands of add-ons, we continue to protect our users from the worst aspects of the web, we continue to both compete and collaborate with other browser vendors and we manage to do all that in an open forum with open source code. Firefox is a reflection of our larger view of the transparency that we want to see in an open web. Put simply: We are the change we want to see on the web.

So that’s a lot of talk. Back to the issue at hand. Silverlight, video, adobe, multimedia, market power. How do we compete? Or, really, how do you compete? Because Mozilla isn’t going to create this change alone. We’re very very small by any standard in the tech marketplace. Our reach is pretty good with Firefox 2 + Firefox 3, and we’re starting to have real market effects, but we’re not going to be able to buy our way onto millions of computers by sponsoring the olympics.

People who have talked to me have heard me talk about two things on this topic. I usually say something like “you need to learn how to build a product” or “you need to find out what you can lead at and go do that.” There’s usually more than that, but that’s the main part of the message. And I think that if we want to make sure that the web isn’t overtaken by the acts of industry giants, that there are real actionable things we can do to make that happen.

I’ll use video on the web as a simple example. Here are the things that I think need to happen to make Theora a player in the real world.

1. Make sure there’s a really great video plugin for Apple Quicktime that delivers the OGG Theora video format to people who use the video tag in Safari. When I tried to play the ogg theora video from my post the other day the ogg plugin jumped around, showed a white screen for long periods, paused for a few seconds at a time – bad!

2. Create a control that brings the video tag to IE like Vlad did for the canvas tag. The world is much bigger than just Firefox. This would make it very easy to deliver and build content and make it easy for consumers to get access to it. Bring ubiquity to content like Adobe was able to do with Flash. (Note: Cortado isn’t good enough – it’s still stuck in the plugin prison!)

3. Make a super-easy, consumer-focused, high-quality encoder for ogg theora that anyone can use to encode their videos for the web. (Here’s a hint: Handbrake is still too hard to use.) Hook it up to the various video camera providers on mac and windows so that it’s super easy to create content, encode it, and with the tools listed above, upload it and make it available to others.

4. Even better, build a business around the tools above. Or even a service for people to upload to. Sustainability is an important component and it should not be left behind.

5. Create awesome demos of what you can do with the video tag, or even better mixed with the recent stuff we’ve been showing off with video + svg filters. Blur effects, video driven by content, content people can create and overlay onto existing videos, etc. Some of this stuff is out there, some of it isn’t. But it’s a start. Try mixing video with other content on the web – mash it up, cover it up, add value and context to otherwise boring videos. Its easier to do with the video tag than it is when it’s hidden inside of Flash or Silverlight.

So that’s just a short list of things people can do to help with video. There are lots of other things that people can do in other areas, other than just video, but I wanted to give an example of my thinking around OGG Theora as an example.

People seem excited about us including OGG Theora in our next Firefox release. But keep in mind it’s only a start. If the same ecosystem that we’ve seen develop around the open + generative web doesn’t grow around open video like it has around the web then we will end up with the status quo: a vibrant growing web but with large parts that are hobbled by a model that doesn’t grow on itself. Mozilla isn’t going to be able to do this job entirely on its own, but we’re doing our part. It’s going to take others to understand how we do what we do, copy its model and try to create the same effects in the other important parts of the ecosystem.

I wonder what the world will look like five years from now. It’s going to be an interesting ride.

« Older entries