This blog post is
14 years old! Most likely, its content is outdated.
Especially if it's technical.
This is an article about a group of developers who had a task to do but hadn't chosen what programming language to use. The alternatives they had to choose from were C, PHP, Perl, Java and Python; and the requirements where these:
- We planned to prototype on a remote device and anticipated numerous changes. We needed a language that was designed with change in mind.
- We wanted to avoid the added step of code compilation in order to minimize the overhead associated with a change. An interpreted language seemed pragmatic.
- We wanted a language with good introspection capability.
- We needed to do a lot of string manipulation and file I/O. Whatever language we chose had to excel in both of these areas.
It's so suited for Python that it almost sounds as if they wrote the requirements after the choice. But that's just how Python is.
- Previous:
- Moscow Metro
01 December 2003
- Next:
- Mr. Picassohead
03 December 2003
- Related:
- Django vs. Java
25 October 2008
- Vista voice recognition and Perl
09 February 2007
- Zope compared to PHP
22 June 2005
- Integer division in programming languages
04 August 2004
- He must really hate C
17 March 2004
- PSP - Python Server Pages
09 March 2004
- Why Sun should Open up on Java
18 February 2004
- Crontab wizard
13 January 2004
- Zolera SOAP Infrastructure 1.4
14 November 2003
- Python for .NET
06 November 2003
