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.
- Moscow Metro
01 December 2003
- Mr. Picassohead
03 December 2003
- Related by category:
- How much faster is Redis at storing a blob of JSON compared to PostgreSQL?
28 September 2019
- Best practice with retries with requests
19 April 2017
- Fastest way to find out if a file exists in S3 (with boto3)
16 June 2017
- Interesting float/int casting in Python
25 April 2006
- Fastest way to unzip a zip file in Python
31 January 2018
- Related by keyword:
- Integer division in programming languages
04 August 2004
- Django vs. Java
25 October 2008
- Vista voice recognition and Perl
09 February 2007
- PSP - Python Server Pages
09 March 2004
- Zope compared to PHP
22 June 2005