Showing posts with label apache. Show all posts
Showing posts with label apache. Show all posts

29 May 2007

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.

24 May 2007

IBM Opens Up - A Little More

One of the most important journeys in the world of software has been undertaken by IBM. Its early support for first Apache, and then GNU/Linux, were critical in establishing open source as viable for business. Then came the donation of code to Eclipse, and many other smaller acts of openness.

Here's the latest one:

IBM is kicking off an experiment to open up its software development process in a way that mirrors the creation of open source applications.

"The reward of getting our information out there is going to be amazing and critical to the future of IBM's software," Jerry Cuomo, chief technology officer of IBM's WebSphere middleware suite, told vnunet.com in an interview at the IBM Impact 2007 conference in Orlando.

Cuomo is planning to publish the source code control system of software projects and encourage lead engineers to start blogs.

This will allow them to engage in conversations with outside developers and IBM customers and poll them on planned features and technologies.

I'm sure this will become the standard way to develop commercial software. Just think: one day, even Microsoft will be doing it.

04 April 2007

Oh: And I Thought IBM Got It

One of the key moments in the rise of open source was IBM's announcement on 10 January 2000 that it would be supporting GNU/Linux across all its hardware. This seal of approval from Big Blue suddenly made free software respectable.

A the time of writing Rebel Code, I spoke to several people from IBM, all of whom seemed really clued up about the deeper implications of open source, how and why it worked, and how companies could work with it and benefit from it. I was really impressed.

And now I read this:

"At some point you become so shrill and beyond what's required that you lose the audience and the audience moves on to something else," he said.

"We'll have to see what finally evolves through the [GPL] process, it's going through an update and the Free Software Foundation has a particular view of free software. Free software is a wonderful thing but there's also a business model."

"We think there are other licensing techniques, the Apache license and others are somewhat less onerous. We use them ourselves. We don't use the GPL for reasons of its restrictions," Mills said.

That was Steve Mills, as in IBM Software General Manager. Seems like the message hasn't quite got through there, Steve. Pity: I obviously need to revise my view of IBM.

07 February 2007

Windows: Rat's Nest and Dog's Breakfast

As Edward Tufte has explained far more eloquently than I can, images are able to convey information far more compactly and efficiently than words. So you don't have to be a geek to appreciate the two images in this posting:

Both images are a complete map of the system calls that occur when a web server serves up a single page of html with a single picture. The same page and picture.

Well, not quite. The upper picture shows Apache running on GNU/Linux; the lower, IIS running on Windows. The former looks like a motherboard: complicated but orderly; the latter is simply a rat's nest.

As the post says:

A system call is an opportunity to address memory. A hacker investigates each memory access to see if it is vulnerable to a buffer overflow attack. The developer must do QA on each of these entry points. The more system calls, the greater potential for vulnerability, the more effort needed to create secure applications.

Now, some have criticised this on the grounds that people don't attempt to attack systems through static Web pages. This is true, but the point is, if this is the difference for a simple operation like displaying a Web page, imagine the contrast for more complex tasks. It is precisely those tasks that offer the greatest scope for finding weaknesses. Thus the images in the post above offer a graphic, if not literal, representation of the dog's breakfast that is Windows security. (Via Slashdot.)

27 December 2006

More than Academic?

I'm always a bit sceptical about academic studies of open source, since they tend to tell what you already knew, but five years late and dressed up in obfuscatory language. That said, there seems to be some genuine content in this specimen, entitled "Two Case Studies of Open Source Software Development: Apache and Mozilla". Worth a quick gander, at least. (Via AC/OS.)

22 December 2006

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.

21 November 2006

Sweet as Sugar FastStack

This kind of thing is the future of open source in business:

Sugar FastStack, a software support and delivery service that provides a fast and simple way to install a complete open source software solution, including Sugar software, the Apache Web Server, PHP and the MySQL database.

Out-of-the-box solutions, full of stack goodness. (Via TheOpenForce.com.)

02 November 2006

MySQL: My, My, My

This post notes that the site www.mysql.com is now in the Alexa 500. Although Alexa is a deeply-flawed measure - it's biased against GNU/Linux systems for a start - it's a measure of sorts. But what is really fascinating is this comment:

Interestingly enough, there are tons of MySQL powered websites among the top 500 including Yahoo, Google, YouTube, WikiPedia, Amazon, Craigslist, AOL, Flickr, Mixi.jp, Friendster, The Facebook, LiveJournal, Digg, CNet, Weather.com, TypePad, Neopets, WebShots, Slashdot, GoDaddy, NetFlix, iStockPhoto, Travelocity, Lycos, PriceGrabber, FeedBurner, CitySearch, Evite and more.

It's not just Apache that's running the Web.

17 October 2006

And Now, the Community's MySQL

MySQL's success is impressive, and provides a handy example of pervasive corporate open source that isn't Apache. Although I'd seen about its new Enterprise offering earlier today, I must confess I hadn't picked up on the complementary Community product until I read this post by Matt Asay. It's a shrewd and necessary move that will doubtless be imitated by others.

21 September 2006

Opening Up Open Source

We know it works, and we know why it works, but somebody would like to know exactly how and why it works:

A group of UC Davis researchers has just received a three-year, $750,000 grant from the National Science Foundation to study how open source software such as the Apache Web server is built.

...

The researchers will focus on the Apache Web server, the PostgreSQL database and the Python scripting language. They will collect information from the message boards, bug reports and e-mail discussions to understand how design teams organize themselves and interact.

Am I the only one who finds it slightly ironic that $750,000 is being spent to write some papers about something that is written for nothing? (Via LXer.)

18 September 2006

Open Source Enterprise Stack: It's Official

I and several thousand other people have been writing about the open source enterprise stack for a while; now free software's Eminence Rouge has given its benediction:

Red Hat Application Stack is the first fully integrated open source stack. Simplified, delivered, and supported by the open source leader. It includes everything you need to run standards-based Web and enterprise applications. Red Hat Application Stack features Red Hat Enterprise Linux, JBoss Application Server with Tomcat, JBoss Hibernate, and a choice of open source databases: MySQL or PostgreSQL, and Apache Web Server.

29 July 2006

Open Source Evo-Devo

In the early days of free software in business - say ten years ago - there was a natural tendency to think of it as a monolithic entity. But rather as chromatography can be used to separate out the constituent parts of an apparently uniform blob, so time gradually teases out the different elements that go to make up the rich and complex world of open source.

Thus we have projects like Apache and GNU/Linux, which are so much a part the mainstream now that it probably hard for most people to imagine that they were never part of it. Then there are the projects like MySQL and JBoss that are fast establishing themselves as second-generation leaders. Finally there is the new wave - the SugarCRMs, the JasperSofts and Alfrescos - that are coming through fast.

I found a nice representation of this evo-devo in a post on Matt Asay's blog, where it is attributed to Robin Vasan. I'm afraid I've never heard of him (I obviously lead a sheltered life), but I see from his bio that he's involved with Alfresco, as Matt is, so this is obviously the connection.

Aside from the graphic - which diverges in detail from my view of things, but is broadly the same - Matt's post contains several other interesting slides (and ideas) from his recent presentation at OSCON 2006. It's well worth taking a look at.

11 July 2006

Apache Starts to Patch the Holes

The latest Netcraft survey shows that Apache has pulled back some of the ground it lost to Microsoft's Web server last month. There have been some pretty massive swings recently, as the oscillations in the graph show: these are largely due to switches in the hosting sector, which can often involve millions of Internet names at a stroke. For example, Go Daddy moved over 1.6 million hostnames from Apache to Microsoft's IIS platform in June.

These new gains for Apache are important, because it suggests that Microsoft's relentless campaign to "convince" hosting companies to switch to its products (and who wouldn't love to be a fly on the wall for those conversations?) may finally have run out of steam. It will be interesting to see what happens next month.

27 April 2006

Apache Now Leader in Secure Web Servers Too

One of the statistics most often trotted out to demonstrate open source's rise and reach is Apache's total dominance of the public Web server sector (I should know, I've done it often enough myself). This has always stuck in Microsoft's craw, and their standard response is "Well, it doesn't really count since it's mostly mickey-mouse Web servers, whereas we are the tops for grown-up secure Web servers" (not their phraseology, but you get my drift).

The news that Apache is now the leading secure Web server as well as the leading Web server overall rather blows this story out of the water. It also means that all that hard work Microsoft has been doing converting domain registrars in a desperate attempt to boost its market share - that is, gaining share among the mickey-mouse Web servers it so pooh-poohed before - was a complete waste of time and money.

27 March 2006

The Science of Open Source

The OpenScience Project is interesting. As its About page explains:

The OpenScience project is dedicated to writing and releasing free and Open Source scientific software. We are a group of scientists, mathematicians and engineers who want to encourage a collaborative environment in which science can be pursued by anyone who is inspired to discover something new about the natural world.

But beyond this canonical openness to all, there is another, very important reason why scientific software should be open source. With proprietary software, you simply have to take on trust that the output has been derived correctly from the inputs. But this black-box approach is really anathema to science, which is about examining and checking every assumption along the way from input to output. In some sense, proprietary scientific software is an oxymoron.

The project supports open source scientific software in two ways. It has a useful list of such programs, broken down by category (and it's striking how bioinformatics towers over them all); in addition, those behind the site also write applications themselves.

What caught my eye in particular was a posting asking an important question: "How can people make money from open source scientific software?" There have been two more postings so far, exploring various ways in which free applications can be used as the basis of a commercial offering: Sell Hardware and Sell Services. I don't know what the last one will say - it's looking at dual licensing as a way to resolve the dilemma - but the other two have not been able to offer much hope, and overall, I'm not optimistic.

The problem goes to the root of why open source works: it requires lots of users doing roughly the same thing, so that a single piece of free code can satisfy their needs and feed off their comments to get better (if you want the full half-hour argument, read Rebel Code).

That's why the most successful open source projects deliver core computing infrastructure: operating system, Web server, email server, DNS server, databases etc. The same is true on the client-side: the big winners have been Firefox, OpenOffice.org, The GIMP, Audacity etc. - each serving a very big end-user group. Niche projects do exist, but they don't have the vigour of the larger ones, and they certainly can't create an ecosystem big enough to allow companies to make money (as they do with GNU/Linux, Apache, Sendmail, MySQL etc.)

Against this background, I just can't see much hope for commercial scientific open source software. But I think there is an alternative. Because this open software is inherently better for science - thanks to its transparency - it could be argued that funding bodies should make it as much of a priority as more traditional areas.

The big benefit of this approach is that it is cumulative: once the software has been funded to a certain level by one body, there is no reason why another should't pick up the baton and pay for further development. This would allow costs to be shared, along with the code.

Of course, this approach would take a major change of mindset in certain quarters; but since open source and the other opens are already doing that elsewhere, there's no reason why they shouldn't achieve it in this domain too.

28 February 2006

Open Source, Opener Source

Brian Behlendorf is an interesting individual: one of those quietly-spoken but impressive people you meet sometimes. When I talked to him about the birth of Apache - which he informed me was not "a patchy" server, as the folklore would have it, just a cool name he rather liked - he was working at CollabNet, which he had helped to found.

He's still there, even though the company has changed somewhat from those early days. But judging from a characteristically thought-provoking comment reported in one of ZDNet's blogs, he's not changed so much, and is still very much thinking and doing at the leading edge of open source.

In the blog, he was reported as saying that he saw more and more "ordinary people" being enfranchised as coders thanks to the new generation of programming models around - notably Ajax and the mashup - that made the whole process far easier and less intimidating.

If he's right, this is actually a profound shift, since ironically the open source model has been anything but open to the general public. Instead, you had to go through a kind of apprenticeship before you could stalk the hallowed corridors of geek castle.

If open really is becoming opener, it will be no bad thing, because the power of free software depends critically on having lots of programmers, and a good supply of new ones. Anything that increases the pool from which they can be drawn will have powerful knock-on effects.

01 February 2006

Spreading Spread Firefox

Most computer users by now have heard of the Firefox browser. This is hardly surprising given the extraordinary rate at which it is still being downloaded and diffused around the world well over a year since its formal launch.

Given that there have now been nearly 150 million downloads (converting that into a meaningful number of users is probably impossible), it is only natural that people think of Firefox as an incredibly successful free browser. It is that, certainly, but it is also much more.

After all, the open source community has shown time and again it can write great code: Linux, Apache, The GIMP, OpenOffice.org - choose your own favourite. But Firefox has done something else - something that has never been done before by a free software project.

It has translated the secret of open source's power - a huge, distributed and connected development team - into the sphere of marketing. The Spread Firefox site has mobilised tens of thousands of users - not as beta testers, as has been the custom previously, but as a guerrilla marketing force.

Most famously, that force was mobilised to pay for the double-page ad in The New York Times. Through the aggregation of many relatively small donations it was able to take out some high-price advertising. In other words, the approach scales.

But the real achievement of Spread Firefox is much subtler, and more diffuse. The tens - hundreds? - of thousands of active Firefox supporters are Microsoft's worst nightmare: a completely invisible - because distributed - team of product evangelists that it can never hope to pin down, let alone match.

This is such an important step beyond the traditional open source process that it is tragic not more has been done with it. For example, although there is a Spread OpenOffice.org, it is only now that a Spread KDE site has been created; both seem in their early stages. But where are all the others? Where are Spread Linux, Spread Thunderbird, Spread GIMP, Spread Audacity and the rest?

All these programs have enthusiastic users who could be directly mobilised across the Internet to spread the word about how good these applications are. Relying on old-fashioned, uncoordinated word-of-mouth is simply to throw away everything that has been learned from Spread Firefox - and to discard one of the strongest trumps in the free software hand.

27 January 2006

Wolfgang Amadeus Mozart, Hacker

Today is the 250th anniversary of the birth of Wolfgang Amadeus Mozart. Most people know him as one of the world's greatest composers: a child prodigy, creator of over 600 works, and – if you believe some of the wilder rumours - fatally poisoned at the age of 35 by a rival composer. Few, though, are aware that Mozart was also a hacker.

Computers may not have existed in the eighteenth century, but the musical machines called orchestras and choirs are conceptually identical to synthesisers, which are themselves specialised music computers. Just as programming code specifies how a computer should act (and a MIDI file controls a synthesiser), so musical code – in the form of a score – directs what instruments and voices should do and when.

Conductors are largely superfluous in all this (at least for Mozart's music): they do not create the output, which is specified by the score. All they do is interact with the score “loaded” on the orchestral or choral machine, in the same sense that someone might interact with a video game loaded on a console. The incidental nature of humans in the performance of classical music is shown by some pieces that Mozart wrote at the end of his life for a clock with built-in mechanical organ. Here the scores completely determined the audio output: there was no human intervention once the music had been converted to a kind of piano roll – a forerunner of the punch cards employed a century and a half later by the early commercial mainframe computers.

More generally, though, hacking is a state of mind, a way of understanding and exploring the world, independent of a particular technology (and not to be confused with “cracking”, which is the correct name for the kind of digital smash and grab too often in today's headlines). Richard Stallman, perhaps the greatest hacker of modern times, has defined the essence of hacking as “playful cleverness” - as good an encapsulation of Mozart's genius as any.

The cleverness showed itself early. Mozart started learning the piano when he was three, began composing when he was five, and wrote his first symphony and opera at the age of eight and 11 respectively. Like many top coders, he frequently worked out everything in his head before consigning it to paper at a single sitting (often just hours before a deadline – again, just like some programmers), and usually without the need for revisions (that is, bug-free). He could also multi-task: he is supposed to have written one of his finest works during a game of skittles.

Like any red-blooded hacker, Mozart adored mathematics as a child (and gambling as an adult), found word-play irresistible (email would have been perfect for him) and loved setting himself puzzles. His Musical dice game uses dice throws and pre-composed short fragments of music to form compositions created by random numbers; the challenge was writing fragments that would fit together whatever the throws. At one point in his opera Don Giovanni, in addition to the main orchestra accompanying the singers, there are three more orchestras on stage, each playing completely different music. It all fits together so perfectly that most opera lovers are unaware of the compositional tour-de-force they are witnessing.

Mozart's playfulness was a key facet of his character. The musical form he seems to have enjoyed writing most – opera buffa – is simply Italian for “funny opera”. In several concertos composed for a horn-playing friend, Mozart added jocular comments to the music - “Slowly, Mr Donkey”; “Breathe!”; “Go on!”; “Oh, filthy swine!” - an early example of commented code. He sometimes employed different coloured inks in a score, rather as modern programming tools do to differentiate various elements. Another piece, called A musical joke, includes notes that are blatantly wrong. If the musicians play them as written, they sound incompetent; if they play the “right” notes, they have failed to perform the piece as the composer intended, and so are indeed incompetent.

Significantly, Mozart was a big fan of a key hacking concept known as recursion, whereby something refers to itself to create a kind of infinite loop. For example, a core hacking project started and led by Stallman is called “GNU”, an acronym for “GNU's Not Unix”, which uses itself in its own explanation. (Recursion is another example of playful cleverness).

Recursive music is created by employing a delayed version of a tune as its own accompaniment. Formally, this is known as a “canon” (simpler versions, like the song “London's burning”, are called “rounds”), and Mozart wrote dozens of them, mostly for himself and his friends to sing at purely private performances. They are notable not only for their fine music, but also for the texts Mozart chose to set: “Lick my bum” is one memorable line that crops up more than once. Today's hackers, too, enjoy dubious lyrics, and have an earthy turn of phrase: the injunction “RTFM” - often thrown at hapless newbies - does not stand for “Read The Flipping Manual”.

Another notable characteristic of hackers is their fondness for science fiction. Overt references to Star Wars may be thin on the ground in Mozart's works, but many of his operas written in the older, “serious” style are based on the same eternal themes of good versus evil and love versus duty that lie at the heart of George Lucas's epic.

The science-fiction writer Arthur C. Clarke once suggested that any sufficiently-advanced technology is indistinguishable from magic; the corollary is that magic is indistinguishable from sufficiently-advanced technology. So Mozart's last opera, The Magic Flute - full of other magical objects, too - is, from this viewpoint, a work of science fiction. It is also a Masonic opera, steeped in mysterious symbols and rituals that will be nonetheless be familiar to the hackers who participate in MMORPGs (Massively Multiplayer Online Role-Playing Games), where characters join guilds, complete quests and seek to gain experience points - just like the hero in The Magic Flute.

The close links between music and hacking run both ways, and many of today's top coders are highly musical. Richard Stallman – whose dedication to the cause of freedom is positively Beethovenian - carries with him a soprano recorder wherever he travels. The profoundly-religious and frighteningly-cerebral Donald Knuth – a kind of hacker J.S.Bach - was moved by his love of music to have an 812-pipe baroque organ built in a specially-designed room in his house. Appropriately enough, Knuth's life-work is called The Art of Computer Programming (Bach called his The Art of Fugue). Representing a different musical tradition, Brian Behlendorf, the prime mover behind the Apache Web server program that runs two-thirds of the Internet, DJs ambient and dub music. And it is well known that for most hackers the crucial first step when they start working is to fire up some particularly loud and inspirational music on their computer. Mozart would have approved.

10 January 2006

Open Source's Big Blunder

It is easy to be fooled by the success of open source software. High-profile applications like Apache and Firefox are routinely cited for their absolute market dominance or relative technological superiority. GNU/Linux is going head-to-head with Microsoft Windows Server, while many are predicting that 2006 will be the year GNU/Linux on the desktop makes its breakthrough (just like 2005 and 2004). The bitter fight over the OpenDocument Format in Massachusetts is an indication that for the first time there is real rival to Microsoft's Office formats, and the Eclipse development platform continues to gain support among coders, corporate IT departments and software companies.

So what's missing from this rosy picture of free software's inexorable rise?

The one area that everyone seems to forget about is education. While it is true that GNU/Linux and open source applications are popular among the more tech-savvy users at university, younger students are exposed almost exclusively to Microsoft's products (except in a few enlightened regions of the world).

The failure of open source to devote significant energies and resources here is a serious problem. As Microsoft learned from Apple, whose initial rise was largely thanks to the widespread use of the Apple ][ in education, if you get them young, you get to keep them (most of them, at least). It is all very well trying to put open source solutions on the desktop, but if the people coming through the educational system have been conditioned to use only Microsoft's products, they will resist any moves to force them to touch anything else. The users become Microsoft's fiercest advocates.

The corollary is that broadening the use of free software in schools will automatically lead to increased use in the home and business markets. Indeed, there is a double benefit if schools routinely deploy programs like Firefox, OpenOffice and GNU/Linux. It ensures that tomorrow's consumers, workers and leaders will be completely comfortable using them, and encourages today's parents to find out more about the software that their children are using at school. One of the huge advantages that open source software enjoys over proprietary applications is that parents can make free copies of a school's software, rather than "borrowing" office copies, say, of Microsoft's products.

Against this background, it is heartening that the UK government body BECTA is carrying out a review of the licensing programme it signed with Microsoft in 2003. Significantly, the report will examine the risks of "lock-in" to Microsoft's products, and "focus on ways to improve access to alternatives to Microsoft products to ensure that there is a freedom of choice". This review therefore takes place in a very different context from the one in which BECTA negotiated its previous deal. In 2003 there was no question about changing supplier - it was taken for granted that Microsoft was the solution: the question was the price reductions that could be won from the company.

As I've noted elsewhere, Microsoft is very adept at bowing to "pressure"” and making "sacrifices" during negotiations. In this case, BECTA could proudly announce that its 2003 deal would save the UK taxpayer £46 million. But for this sum, Microsoft not only retained it grip on the British educational system, but had that stranglehold more or less enshrined in official policy.

It remains to be seen what BECTA comes up with, but its two previous reports in this area, on the use of open source software in schools, and on the possible cost savings of doing so, were notable for their intelligence and even-handedness. This gives some hope that open source may at last be given the opportunity to prove its worth in the British schools.

Helpfully, BECTA has said of its work that "“recognising the increasing relevance of this issue to educators in the EU and indeed globally, an international exchange of views will be facilitated."” This "exchange of views" might provide those living in other areas where there is no significant use of free software in schools with a good opportunity to push for similar reviews in their own countries.

One thing seems certain: if something is not done soon, an entire generation will grow up around the globe that equates the Web with Internet Explorer, email with Outlook, productivity software with Office and computers with Windows. In such a world, open source will at best be marginal, and at worst, irrelevant.