Mozilla's Brendan Eich on JavaScript - and Microsoft Buying Netscape

It seems so long ago now, but for those of us lucky enough (and old enough) to have been there, the launch of Netscape's 0.9 version of its Netscape Navigator browser in October 1994 was clearly the beginning of a new era. For a few years, Netscape was the centre of the Internet universe - it's home page was the first you checked each morning for news about what was happening on this strange new Web thing that the company was doing so much to define.

On Open Enterprise blog.

Why Open Source isn't Tiddly for BT

I'd come across TiddlyWiki before, but never really got what it was about....

On Open Enterprise blog.

And RMS Spake, and it Was Good

As well as being a great coder, RMS is a fine writer (he made a number of excellent suggestions when I sent him rough drafts of the relevant chapter of Rebel Code). So it's a pity that he doesn't write much these days.

And it's also a red-letter day when he does, as with his latest missive: "The Javascript Trap". This describes a problem he has spotted: non-free Javascript.

It is possible to release a Javascript program as free software, by distributing the source code under a free software license. But even if the program's source is available, there is no easy way to run your modified version instead of the original. Current free browsers do not offer a facility to run your own modified version instead of the one delivered in the page. The effect is comparable to tivoization, although not quite so hard to overcome.

...

It is possible to release a Javascript program as free software, by distributing the source code under a free software license. But even if the program's source is available, there is no easy way to run your modified version instead of the original. Current free browsers do not offer a facility to run your own modified version instead of the one delivered in the page.

He comes up with some interesting solutions:

we need to change free browsers to support freedom for users of pages with Javascript. First of all, browsers should be able to tell the user about nontrivial non-free Javascript programs, rather than running them. Perhaps NoScript could be adapted to do this.

Browser users also need a convenient facility to specify Javascript code to use instead of the Javascript in a certain page.

RMS: where would we be without him?

Follow me on Twitter @glynmoody

Enter the (Komodo) Dragon

On Open Enterprise blog.

Why Javascript, not Flash? - Ask Zoho

I've only just come across this, perhaps the best summary of why using Flash is the wrong way to create Web apps:

1. Native to the Web

A real web application should natively support web standards - HTML & CSS are pretty much synonymous with “web standards”. The biggest reason we started out with Javascript is that it is native to the web - in the sense its core object model for Javascript is the HTML/CSS Document Object Model. The DOM is a gift to web applications. Even with the annoying browser differences in DOM (which sophisticated libraries increasingly hide), it is still far better to have the DOM than not have it. Flash, for all its advantages, sits in a separate space from the browser. In that sense, Flash is not that different from Java-on-the-client. In fact, Flash is Java-on-the-client-done-right.

I am sure Flash will eventually find a way to natively integrate with the browser but it is not there yet.

2. Open Source Library Support

This is a big one. The depth and variety of libraries available in Javascript just keep getting better. It is mind boggling just how much open source development is going on in Javascript. Developers keep pushing the envelope. For one example, look at the jQuery solar system demo. It shocked me the first time I saw it. Pretty impressive that Javascript could do that, right? The capabilities of Javascript exceed the client requirements of office productivity applications today, and there are tons more innovations coming.

3. Vector Graphics in Browsers

This is another big one. Vector graphics formats like SVG (Firefox, Opera), VML (IE), and HTML Canvas (Firefox, Safari, Opera), are becoming ubiquitous in browsers. Yeah, it sucks that IE doesn’t support SVG, but that can be worked around. Even cooler is the fact that SVG & VML are XML and very Javascript friendly. You can do real magic.

Obviously, number 2 is the heart of the matter: Javascript is just going to keep getting better, faster, thanks to the open development process. With Flash, you're dependent on the skills of one company (now, where have I heard that before?)

How Do You Do, Dojo?

New one on me:

Dojo is an Open Source DHTML toolkit written in JavaScript. It builds on several contributed code bases (nWidgets, Burstlib, f(m)), which is why we refer to it sometimes as a "unified" toolkit. Dojo aims to solve some long-standing historical problems with DHTML which prevented mass adoption of dynamic web application development.

(Via 451 CAOS Theory.)

Under Slashdot's Bonnet

Everybody knows that Google runs on scadzillions of GNU/Linux boxes, but now we also know the details about Slashdot's Penguin power:

Slashdot currently has 16 web servers all of which are running Red Hat 9. Two serve static content: javascript, images, and the front page for non logged-in users. Four serve the front page to logged in users. And the remaining ten handle comment pages. All web servers are Rackable 1U servers with 2 Xeon 2.66Ghz processors, 2GB of RAM, and 2x80GB IDE hard drives. The web servers all NFS mount the NFS server, which is a Rackable 2U with 2 Xeon 2.4Ghz processors, 2GB of RAM, and 4x36GB 15K RPM SCSI drives.

Impressive what you can do with 16 boxes.

Open Designs

Although Web pages are usually regarded as content, there can be a fair amount of code behind them too in the form of scripting and cascading style sheets (CSS). This means that there is a need for shared code in these areas, and the Open Design community aims to help out on the CSS side.

As an aside, it's interesting to note that the majority of stylesheets there use a Creative Commons licence, rather than the GNU GPL, say: this suggests people think of the code more as a form of content in this context. (Via James Tyrrell.)

Enter the Open Komodo Dragon

I've always been struck by how little known the company ActiveState is, given that it's worked with many open source languages such as JavaScript, Perl, PHP, Python, Ruby and Tcl. Now it's opening up its multi-platform, multi-language IDE:

With the Open Komodo Project, the focus is on dynamic languages and the open web. Open Komodo is developed on top of many open source technologies including Mozilla, Python, and Scintilla. The primary development technologies used include XUL, JavaScript, Python, and C/C++. The Open Komodo platform will be entirely open source and licensed under the same terms as Firefox: Mozilla Public License (MPL), GNU General Public License (GPL), and GNU Lesser Public License (LGPL).

The Open Komodo Project aims to create a full-featured web development tool for client-side web development integrated with Firefox, Mozilla's free, open source web browser, and based on the award-winning Komodo IDE. This new tool, codenamed Komodo Snapdragon, will be developed in collaboration with the open source community.

Sounds good, particularly the integration with Firefox.

Is Silverlight for GNU/Linux Moonshine?

Hm, don't know what to think about this:

Over the last few months we've been working to enable Silverlight support on Linux, and today we are announcing a formal partnership with Novell to provide a great Silverlight implementation for Linux. Microsoft will be delivering Silverlight Media Codecs for Linux, and Novell will be building a 100% compatible Silverlight runtime implementation called "Moonlight".

Moonlight will run on all Linux distributions, and support FireFox, Konqueror, and Opera browsers. Moonlight will support both the JavaScript programming model available in Silverlight 1.0, as well as the full .NET programming model we will enable in Silverlight 1.1.

I suppose it depends on how open the specification is - and whether it's just OOXML by any other name....

Anyone any thoughts?

The Secret World of S5

Hm, I'd somehow missed this before:

S5 is a slide show format based entirely on XHTML, CSS, and JavaScript. With one file, you can run a complete slide show and have a printer-friendly version as well. The markup used for the slides is very simple, highly semantic, and completely accessible. Anyone with even a smidgen of familiarity with HTML or XHTML can look at the markup and figure out how to adapt it to their particular needs. Anyone familiar with CSS can create their own slide show theme. It's totally simple, and it's totally standards-driven.

Pity I don't have any familiarity with CSS....(Via Luis Villa's Blog.)

Will Microsoft Be Assimilated?

I knew that I knew nothing about aQuantive. Here, for example, is something rather important that I didn't know I didn't know:

Information available from Atlas' Web site indicates the Internet software company employs extensive use of open source software including Linux, Apache, MySQL, and Solaris.

Software engineers at Atlas' Raleigh office do client/server development in C and C++, software maintenance and "scripting", and developing and maintaining custom reporting capabilities.

Other sought after skills include Unix development, JavaScript, and those for Windows software administration like SQL Server and IIS.

The use of open source is not confined to Atlas with the second significant business unit Avenue A Razorfish boasting "we also frequently utilize open source technologies".

There was a similar situation when Microsoft bought Hotmail, which was running on Apache and FreeBSD for a long time after acquisition. Since aQuantive is much bigger, we can presumably expect Microsoft to have even more difficulty assimilating it.

Open Source: Just the Ticket for Librarians

Here's a well-written story about how librarians have undertaken a major open source project with great success:

The system, Evergreen, whose 1.0 release came in November, is an Integrated Library System (ILS): the software that manages, catalogs, and tracks the circulation of library holdings. It's written in C, JavaScript and Perl, is GPLed, runs on Linux with Apache, uses a PostgreSQL database, Jabber for messaging and XUL as client-side software. The system allows easy clustering and is based entirely on open protocols.

Aptana: Apt for Success?

The line-up of cross-platform open source apps is pretty impressive, except in one area: Web design. Until now, all we've really had is Nvu, which is certainly very easy to use, but rather limited in terms of more advanced features.

But now here's Aptana, a "robust, JavaScript-focused IDE for building dynamic web applications". It's still early days yet, but judging by the screenshots, it looks promising. (Via Digg).

The Blogification of the Cyber Union

I suppose it was inevitable that Google would go from being regarded as quite the dog's danglies to being written off as a real dog's breakfast, but I think that people are rather missing the point of the latest service, Google Page Creator.

Despite what many think, Google is not about ultra-cool, Ajaxic, Javascripty, XMLifluous Web 2.0 mashups: the company just wants to make it as easy as possible for people to do things online. Because the easier it is, the more people will turn to Google to do these things - and the more the advertising revenue will follow.

Google's search engine is a case in point, and Blogger is another. As Blogger's home page explains, you can:

Create a blog in 3 easy steps: (1) Create an account (2) Name your blog (3) Choose a template

and then start typing.

Google Page Creator is just the same - you don't even have to choose a name, you just start typing into the Web page template. In other words, it has brought the blog's ease of use to the creation of Web sites.

This blogification of the Internet is a by-product of the extraordinary recent rise of blogs. As we know, new blogs are popping up every second (and old ones popping their clogs only slightly more slowly). This means that for many people, the blog is the new face of the Web. There is a certain poetic justice in this, since the original WorldWideWeb created by Tim Berners-Lee was a browser-editor, not simply a read-only application.

For many Net users, then, the grammar of the blog - the way you move round it and interact with its content - is replacing the older grammar of traditional Web pages. These still exist, but they are being shadowed and complemented by a new set of Web 2.0 pages - the blogs that are being bolted on by sites everywhere. They function as a kind of gloss explaining the old, rather incomprehensible language of Web 1.0 to the inhabitants of the brave new blogosphere.

Even books are being blogified. For example, Go It Alone!, by Bruce Judson, is freely available online, and supported by Google Ads alongside the text (like a blog) that is broken up into small post-like chunks. The only thing missing is the ability to leave comments, and I'm sure that future blogified books (bloks? blooks?) will offer this and many other blog-standard features.

Update: Seems that it's "blook" - and there's even a "Blooker Prize" - about which, more anon.

Open Source's Best-Kept Secret

Ajax is short for Asynchronous Javascript + XML; it enables a Web page to be changed in the browser on the fly, without needing to refer back to the original server. This leads to far faster response times, and is behind many of the most interesting developments on the Web today; Gmail is perhaps the most famous example. Essentially it turns the browsers into a lightweight platform able to run small apps independently of the operating system (now where have we heard that before?).

The news of an Open Ajax project that will simplify the creation of such sites is therefore welcome. However, what is most interesting about the announcement is not the luminaries who are lining up behind it - IBM, Oracle, Red Hat and Yahoo amongst others - but the fact that it is yet another Eclipse project.

To which most people would probably say, Who? For Eclipse is open source's best-kept secret. It stands in the same relation to Microsoft's Visual Studio development tools as GNU/Linux does to Windows, and OpenOffice.org to Microsoft Office. Where these address respectively the system software and office suite sectors, Eclipse is aimed at developers. It is another example of IBM's largesse in the wake of its Damascene conversion to open source: the project was created when the company released a large dollop of code under the Eclipse Public License.

What's interesting is how Eclipse has followed a very similar trajectory to GNU/Linux: at first it was ignored by software companies, who preferred to stick with their own proprietary rivals to the Microsoft juggernaut. Later, though, they realised that divided they would certainly fall, and so united around a common open standard. The list of "Strategic Members" and "Add-in Providers" reads like a Who's Who of the world's top software companies (bar one).

This illustrates another huge - and unique - strength of open source: the fact that it represents neutral ground that even rival companies can agree to support together. The mutual benefit derived from doing so outweighs any issues of working with traditional enemies.

Even though Eclipse is relatively little known at the moment, at least in the wider world, it is not a particular bold prediction to see it as becoming the most serious rival to Microsoft's Visual Studio, and the third member of the open source trinity that also includes GNU/Linux and OpenOffice.org.