Robert Accettura's
Fun With Wordage

Ran across this quote today which I just had to blog from WordPress.com’s Matt Mullenweg since I found it funny:

“We decided to show ads only on certain pages, only to the people who were sort of random drive-by visitors…if you use Firefox, you’ll never see an ad, no matter what, mostly because I like Firefox.”

Also kinda interesting from a business perspective. There’s been some suggestion over time that Firefox users are prone to ignore ads. Partially because of extensions that block ads (though products to block ads on the OS level, and in IE exist too BTW), but partially because they are said to be more technical.

I wonder if a practice like this actually provides a higher click through rate. Because they only show ads in certain places, it’s not about total impressions (they control that by picking where to show ads, and when). They control how many impressions they run in a given period. By targeting those more inclined to click on ads, theoretically your ratio should be higher.

I’ve heard of quite a few different ways to target ads over the years, but this is a new one.

Ok, I promise to slow down on the use of X vs. Y on this blog, but after this post. CNet has an interesting blog post by Stephen Shankland essentially asking is public domain software open source? A very interesting question.

This little bit of information from Richard Hipp, founder of SQLite, I found to be particularly interesting:

“…The consensus there seems to be that ‘public domain’ is valid and is a proper subset of ‘open source’–except in France and Germany where the concept of ‘public domain’ is not recognized…”

In my opinion, as long as the project stipulates that all contributions be released as public domain (defined as intellectual property not owned or controlled by anyone, and available for use by anyone for any purpose without restriction) for perpetuity, I think that in itself is an open source license. It’s also the cleanest and most easy to read.

Vlad wrote about his work on improving Mac OS X performance (which is awesome by the way), and his findings from looking at WebKit code. To summarize WebKit utilizes some undocumented API’s (ironically from the same company that makes Mac OS X ) that give it an advantage over other software which can’t use them. This is pretty anti-competitive, and Microsoft-like in behavior. For a company that built it’s modern OS on an open source core, and it’s flagship browser (which is key to their mobile initiative) on an open source rendering engine (KHTML), you would think they would be a little more understanding about crippling platforms. Then again, look at the iPhone controversy regarding it being a closed platform (though that’s supposed to change next week, and I’ll be sure to blog about that).

Robert O’Callahan’s got a got a great blog post on some of his observations of things Mozilla would likely make good use of. He also mentions one thing worth quoting:

It’s worth reflecting that if Microsoft was doing this, they’d likely be hauled before a judge, in the EU if not the US. In fact I can’t recall Microsoft ever pulling off an undocumented-API-fest of this magnitude.

This is a very valid point which I 100% agree with. Microsoft wouldn’t get away with this.

Safari developer David Hyatt (former Mozilla developer from when Lizards roamed the earth) commented about this issue. Essentially he justifies the decision based on it not being a good practice to use some of these methods, and other aren’t even used anymore. This of course raises the question: Should Apple be deciding what other software developers can do, when they themselves can’t follow the same standards? I’d say that if WebKit feels it has to use it, there’s likely others out there in the same situation regardless of “best practice”.

See, I’m not too much of an Apple fanboy to criticize them .

So the format war of Blue-ray vs. HD-DVD is over. There are still several other rather significant battles going on in the tech world right now that aren’t Microsoft vs. Apple or Yahoo vs. Google. For example:

Adobe Air vs. Mozilla Prism vs. Microsoft Silverlight

Google Gears vs. HTML5 Offline support

Android vs. iPhone SDK vs. Symbian

Ruby On Rails vs. PHP

Not every case will have a true “winner”. That’s not really a bad thing. Choice is good. In some cases they will merge to form one standard, such as what’s likely for offline web applications.

What is interesting is that SQLite really dominates right now. Adobe Air, Mozilla Prism, Google Gears, Android, iPhone SDK (likely through Core Data API), Symbian, Ruby On Rails (default DB in 2.0), PHP 5 (bundled but disabled in PHP.ini by default). It’s becoming harder and harder to ignore that SQL survived the transition from mainframe to server, and now is going from server to client.

No longer is the term “database” purely referring to an expensive RAID5 machine in a datacenter running Oracle, MySQL, DB2 or Microsoft SQL Server. It can now refer to someone’s web browser, or mobile phone.

This has really just begun to have an impact on things. The availability of good information storage, retrieval, and sorting means much less of these poorly concocted solutions and much better applications. Client side databases are the next AJAX.

Edit [2/27/2008 9:14 AM EST]: Added Symbian, since they also use SQLite. Thanks Chris.

From Fake Steve:

BTW, firebug dude? Stop writing to me.

Joe Hewitt harassing Steve Jobs ?

There are a few goodies in the new java plugin that will be available for Firefox 3.0 and later that I’m really glad to see:

• Improved reliability. The JVM running the applet is isolated from the web browser at the operating system level. If something should go wrong while running the applet, or if an uncooperative applet refuses to shut down, the new Java Plug-In detects and handles the error condition gracefully; the web browser is unaffected.
• Improved user experience. The new Java Plug-In starts applets in the background, so the web browser always remains responsive. Applets appear on the web page as they become ready to run.

A major criticism of java applets has always been their impact on browser performance. This should do a lot to remedy the problem. Another great addition is that you can now use an animated loading gif by using a new image param such as:

<applet archive="large_archive.jar"
           code="MyApplet"
           width="300" height="300">
    <!-- Use an animated GIF as an indeterminate progress bar
           while the applet is loading -->
    <param name="image" value="animated_gif.gif" />
    <!-- Turn off the box border for better blending with the
           surrounding web page -->
    <param name="boxborder" value="false" />
    <!-- Center the image in the applet's area -->
    <param name="centerimage" value="true" />
</applet>

There’s other great stuff, but these are my personal favorites as they resolve long time gripes. You can find the above plus more in the release notes.

[Hat Tip: Henrik Gemal]

As mentioned elsewhere, 500+ Million downloads have been reached! That’s one hell of a milestone. I love the idea of plugging a good cause with the celebration. I heard of FeedRice, but didn’t try it until tonight. I might need to try and make a habit of playing that at least once a week. Seems like a good cause and improving vocabulary isn’t such a bad idea. 500 Million grains of rice is an achievable goal.

Also be sure to digg it to spread the word.

What better way to celebrate a monumental goal than to help your fellow man?