Why interpreted languages make superior scripting languages

By Niraj Zade  |  2023 Jan 03  |  1m read  |  tags:

Table Of Contents

None

Ever thought why python, bash, ruby are so dominant in the scripting scene?

It is not their syntax or their standard libraries that make them so good for scripting. The actual reason is the convenience/workflow.

Take a compiled language. For eg: C.

If you want to write a quick script, you'll write a script.c

But you cannot use it yet. You'll have to:

  1. Write the script in a C file
  2. Compile it for your architecture.
  3. Copy-paste the object file to your $PATH
  4. Execute the compiled file, and check if the script works
  5. If the script doesn't work, you are back to step 1

A similar process will be for other compiled languages like C++, rust, C#, java, scala etc

~

Now take an interpreted language. For eg: python

You write the script.py in your $PATH directory, and you can immediately execute it by running the script.py. No more steps.

If the script doesn't work, edit it on the spot and re-run it. Simple.

It is the same for other interpreted languages like python, bash, ruby etc.

~

With interpreted languages you can write scripts stupid fast. Because, the file you write is exactly the file that is run. There are no other steps, no frictions. Just write, and it is already executable.

Another point is, the python script that you wrote for your computer can be run on any device that has python installed. The C script that you wrote for your computer will have to be re-compiled to match the architecture of the other device.

The difference is in being able to do something immediately, versus having to do extra steps to get the thing done.

Friction is a big factor.


Other Articles

(Most of these are ever evolving pieces)


sqlserver

SqlServer reference - All date & time formatters
2025 Jul 10 | 2m (519 words)


spark

Spark Microbook
2025 Oct 16 | 26m (4,801 words)

Delta Lake - performance optimization and maintenance
2026 Jan 03 | 12m (2,262 words)

Spark performance optimization compendium
2025 Oct 11 | 4m (887 words)

Spark join strategies
2024 Jan 22 | 13m (2,450 words)


python

Unicode string normalization schemes in Python
2024 May 06 | 7m (1,303 words)

Python gotchas compilation
2023 Sep 17 | 5m (1,058 words)


linux

SSH notes
2024 Sep 22 | 2m (417 words)


career

Lecture - You and your research by Dr. Richard Hamming
2024 Oct 14 | 1hr18m (14,441 words)

Why charge more as an engineer
2025 Oct 13 | 6m (1,253 words)


personal computing

Keyboard shortcuts
2024 May 06 | 0m (137 words)


resources

Catalyzing research within India
2025 Aug 25 | 1m (239 words)

Links collection
2025 Jun 15 | 3m (586 words)

Papers, books, talks etc
2025 Jun 02 | 3m (715 words)


webtech

JWT - a quick overview of its working and encryption algorithms
2024 Apr 02 | 12m (2,321 words)

© Niraj Zade 2025 - Website, Linkedin
Website was autogenerated on 2026-01-11
Whoever owns storage, owns computing