Showing posts with label perl. Show all posts
Showing posts with label perl. Show all posts

10 March 2013

Python Trademark At Risk In Europe: Python Software Foundation Appeals For Help

The open source programming language Python -- named after the British comedy series "Monty Python" -- became popular in the 1990s, along with two other languages beginning with "P": Perl and PHP. Later, they formed a crucial part of the famous "LAMP" stack -- the GNU/Linux operating system + Apache Web server + MySQL database + Python/Perl/PHP as scripting languages -- that underpinned many of the most successful startups from this time. 

On Techdirt.

19 March 2009

It's *Not* The 15th Birthday of Linux – and Why That Matters

Last week, I wondered whether I'd gone back in time. Everywhere I went online – on news sites, blogs and Twitter – people were celebrating the 15th birthday of Linux, it seemed. “How is this possible?” I asked myself. “Since Linux was started in 1991, that must mean we are in 2006: have I fallen through a wormhole into the past?”

On Linux Journal.

Follow me on Twitter @glynmoody

29 May 2008

Er, Yes, and What About the AGPL?

Here's a post explaining Google's support for just seven open source licences:

The trend around licensing is obvious: GPLv2/GPLv3 represent 42.6% of the projects, and Apache is 25.8%. MIT, BSD, and LGPL are at about 8% each, Artistic at 3.5%, and MPL 1.1 at a mere 2.7%. This follows my own observation about how people license their projects. If they are advocates of Free Software, they will choose GPL; advocates of Open Source will choose Apache (a more modern and thorough permissive license, compared to BSD or MIT). And this is exactly what I recommend to people: choose GPLv3 or Apache v2 based on your personal philosophy.

Well, actually, there's another rather important trend that is conspicuous by its absence: adoption of the Affero GPL. To which Google seems strangely allergic....

19 December 2007

06 September 2007

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.

29 August 2007

Will Free Software Licences Be Derailed?

Upholding licences is crucial to the success of free software, so potentially, this looks really bad news:

Open-source software and the licenses that govern it suffered a serious setback in a San Francisco District Court earlier this month, following a preliminary decision that could effectively deprive open source licensors from being able to get a court injunction to stop the violation of the terms of their license going forward.

Although the judge's analysis is superficially worrying for the way he interprets the licence, there is an important fact in this particular situation, which has already involved tussles over software patents:

At issue was model train software code that Jacobsen and some other open source developers wrote, called the Java Model Railroad Interface, or JMRI, which is licensed under the Open Source Initiative approved Artistic License.

Now the Artistic Licence, originally drawn up by Larry Wall for Perl - and whose name was chosen purely for the pun it allowed - is a notoriously loose licence. IANAL, but it seems to me that the problem the judge has with granting an injunction against the model train software company is that the Artistic Licence simply gives, well, too much licence.

I may be wrong, but I think the far more demanding GNU GPL would avoid this problem - another good reason for choosing a more rigorous licence. We shall see whether I am right....

26 January 2007

The Apotheosis of VisiCalc

If the name Dan Bricklin means nothing to you, you obviously missed out on the PC revolution's prehistory (or maybe I'm just showing my age). Bricklin is one of the Ur-hackers, author of the almost mythical VisiCalc, the first spreadsheet (yes, there was one: the idea has not been present since the dawn of time).

But more than being a mere coder-god, Bricklin is a man with his heart in the right place. He did not attempt to "patent" the idea of a spreadsheet, and for that deserves our eternal thanks. Continuing this fine tradition of altruism, his latest program goes even further, and is being released under the GNU GPLv2. It's called wikiCalc: it combines the best of Bricklin's past with today's increasingly trendy wikis.

As its home page at Software Garden explains:

The wikiCalc program lets you make web pages with more than just paragraphs of prose. It combines the ease of authoring and multi-person editing of a wiki with the familiar visual formatting and calculating metaphor of a spreadsheet. Written in Perl and released under the GPL 2.0 license, it can easily be setup to run on almost any server as a web application or on a personal computer to publish by FTP.

There's also a fuller explanation, as well as the code itself. Whether you do it out of a sense of historical piety, or because you want to play with tomorrow's cool - and open - toys, it's really worth taking a look at.

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.

11 July 2006

How the Stacks Stack Up

The ever-interesting Steven Vaughan-Nichols, who goes back a long way in the free software world, has a fascinating article about a comparison of two application stacks, one open source, the other from Microsoft. The results were surprising:


The tests showed that such vanilla LAMP (Linux, Apache, MySQL, PHP/Python/PERL) stacks as SLES (SUSE Enterprise Linux Server) 9, Zope, ZODB, and PHP and a pure LAMP based on SLES, produced "C" results. They weren't bad, but they weren't anywhere near as good as an out of the box .NET stack based on Windows Server 2003, IIS (Internet Information Server), SQL Server 2005, ASP (Active Server Pages), and SharePoint Portal Server 2003.

The results mirror those of the Mindcraft tests back in the late 1990s, when GNU/Linux found itself whupped by Microsoft. But the consequence was a range of improvements that soon took free software past Windows. However disappointing the current outcome for the stack tests may be, I'm sure that the same will happen here.

Remember: every bug report makes open source stronger, and the same goes for adverse benchmarks.

10 February 2006

Scrying an Oracle

This story has so many interesting elements in it that it's just got to be true.

According to Business Week, Oracle is poised to snap up no less than three open source companies: JBoss, Zend and Sleepycat Software. JBoss - which calls itself the "professional open source company", making everyone else unprofessional, I suppose - is one of the highest-profile players in this sector. Not least because its founder, the Frenchman Marc Fleury, has a tongue as sharp as his mind (you can sample his blog with this fab riff on genomics, Intelligent Design and much else).

His controversial remarks and claims in the past have not always endeared him to others in the free software world. Take, for example, the "disruptive Professional Open Source model" he proudly professes, "which combines the best of the open source and proprietary software worlds to make open source a safe choice for the enterprise and give CIOs peace of mind." Hmm, I wonder what Richard Stallman has to say about that.

JBoss has been highly successful in the middleware market: if you believe the market research, JBoss is the leader in the Java application server sector. Oracle's acquisition would make a lot of sense, since databases on their own aren't much fun these days: you need middleware to hook them up to the Internet, and JBoss fits the bill nicely. It should certainly bolster Oracle in its battle against IBM and Microsoft in the fiercely-fought database sector.

While many might regard the swallowing up of an ambivalent JBoss by the proprietary behemoth Oracle as just desserts of some kind, few will be happy to see Zend suffer the same fate. Zend is the company behind the PHP scripting language - one of the most successful examples of free software. (If you're wondering, PHP stands for "PHP: Hypertext Preprocessor" - employing your standard hacker recursive acronym naming convention).

Where JBoss is mostly key for companies running e-commerce Web sites, say, PHP is a core technology of the entire open source movement. Its centrality is indicated by the fact that it is one of the options for the ubiquitous LAMP software stack: Linux/Apache/MySQL/PHP or Perl or Python. The fact that Oracle will own the engine that powers PHP will be worrying for many in the free software world.

About Sleepycat, I can only say: er, who? - but that's just ignorance on my part. This article explains that Sleepycat's product, Berkeley DB, is actually the "B" in LAMP. Got that? The Sleepycat blog may throw some more light on this strange state of affairs - or maybe not.

Whatever the reason that Oracle wants to get its mitts on Sleepycat as well as Zend and JBoss, one thing is abundantly clear if these rumours prove true: Oracle is getting very serious about open source.

In the past, the company has had just about the most tortuous relationship with open source of any of the big software houses. As I wrote in Rebel Code, in early July 1998, an Oracle representative said "we're not seeing a big demand from our customer that we support it" - "it" being GNU/Linux. And yet just two weeks later, Oracle announced that it was porting Oracle8 to precisely that platform. This was one of the key milestones in the acceptance of free software by business: no less a person than Eric Raymond told me that "the Oracle port announcement...made the open source concept unkillable by mere PR" - PR from a certain company being a big threat in the early days of corporate adoption.

Open source has come on by leaps and bounds since then, and these moves by Oracle are not nearly so momentous - at least for free software. But I wonder whether the otherwise canny Larry Ellison really knows what he's getting into.

Until now, Oracle has mainly interacted with open source through GNU/Linux - that is, at arm's length. If it takes these three companies on board - especially if it acquires Zend - it will find itself thrown into the maelstrom of open source culture. Here's a hint for Mr Ellison: you don't get to assimilate that culture, whatever you might be thinking of doing with the companies. You either work with it, or it simply routes around you.

Yes, I'm talking about forks here: if Oracle misplays this, and tries to impose itself on the PHP or JBoss communities, I think it will be in for a rude surprise. To its credit, IBM really got this, which is why its embrace of open source has been so successful. Whether Oracle can follow in its footsteps, only time will tell.

But the rumoured acquisitions, if they go ahead, will have one other extremely significant effect. They will instantly add credibility, viability and desirability to a host of other second-generation open source companies that have grown up in the last few years. Free software will gain an immediate boost, and hackers will suddenly find themselves in great demand again.

Given the astonishing lift-off of Google's share price, and the palpable excitement surrounding Web 2.0 technologies (and the start-ups that are working on them), the hefty price-tags on open source companies being bandied around in the context of Oracle have a feeling of déjà-vu all over again: didn't we go through all this with Red Hat and VA Linux a few years back?

You don't have to be clairvoyant - or an oracle - to see that if these deals go through, the stage is well and truly set for Dotcom Delirium 2.0.

12 December 2005

Going to the Dogs

My heart leapt last week upon seeing the latest issue of Nature magazine. The front cover showed the iconic picture of Watson and Crick, with the latter pointing at their model of DNA's double helix. A rather striking addition was the boxer dog next to Crick, also gazing up at the DNA: inside the journal was a report on the first high-quality sequencing of the dog genome (a boxer, naturally).

This is big news. Think of the genome as a set of software modules that form a cell's operating system. Every change to a genome is a hack; like most hacks, most changes cause malfunctions, and the cell crashes (= dies/grows abnormally). Some, though, work, and produce slight variants of the original organism. Over time, these variations can build up to form an entirely new species. (In other words, one way of thinking about evolution is in terms of Nature's hacking).

Mostly, the changes produced by these hacks are small, or so slow as to be practically invisible. But not for dogs. Humans have been hacking the dog genome for longer than any other piece of code - about 100,000 years - and the result can be seen in the huge variety of dog breeds (some 400 0f them).

Getting hold of the dog genome means that scientists have access to this first Great Historical Hack, which will tell us much about how genomic variation translates to different physical traits (known as phenotypes). Even better - for us, though not for the dogs - is that all this hacking/interbreeding has produced dogs that suffer from many of the same diseases as humans. Because particular breeds are susceptible to particular diseases, we know that there must be a strong genetic element to these diseases for dogs, and so, presumably, for humans (since our genomes are so similar). The different breeds have effectively separated out the genes that produce a predisposition to a particular disease, making it far easier to track them down than in the human code.

That tracking down will take place by comparing the genomes for different breeds, and by comparing dog genomes against those of humans, mice, apes and so on. Those comparisons are only possible because all this code is in the public domain. Had the great battle over open genomics - open source genomes - been lost at the time of the Human Genome Project, progress towards locating these genes that predispose towards major diseases would have been slowed immeasurably. Now it's just a matter of a Perl script or two.

Given this open source tradition, and the importance of the dog genome, it's a pity that the Nature paper discussing it is not freely available. Alas, for all its wonderful traditions and historic papers, Nature is still the Microsoft of the science world. The battle for open access - like that for open source - has still to be won.