To be fair neither node nor python are where they are today because of their performance.
I wish we could leave them behind as a fun phase of mass adoption of programming and fully switch to strongly typed languages alone. One can dream.
I wish we could leave them behind as a fun phase of mass adoption of programming and fully switch to strongly typed languages alone. One can dream.
The other options built into your UNIX (maybe Linux) machine were:
- C
- C++
- tcsh/ksh/bash
- awk
- TCL
What would you have chosen?
golang/rust/c doesn't fit well the kind of tasks you would use Perl to do. There is simply too much verbosity and at some point in time you will bail out of the sisyphean nature of the task. Kotlin etc are more for mobile apps.
To me, back end work is-
1. Any serious application, that needs to run for years with performance - Java.
2. Glue work- Python/Perl.
This is why a lot of us still use vi/emacs; it's just what's available where we have to fix the problems.
I'll give you an example. I used to contract with booking.com, where they gave us a crippled little windows "amazon workspace" over vnc which we had to use to talk to their systems. They're transitioning from a perl shop into a java one, so naturally they use an IDE. Unfortunately, they have configured this little workspace such that SSH mounting your dev VM into an IDE isn't possible (due to it not having a workable ssh agent), and you can't install anything not pre-approved (so x11 forwarding a locally installed IDE is right out).
Minor changes could have been made to these workspaces to address this; requests for which went ignored for years.
The only thing I could rely on was what I am used to writing perl in. An SSH console session with vim and tmux.
I was quite glad to have java experience from before the days when java IDEs were any good. I'd have been screwed if I didn't know how to use the debugger and javac directly.
We've all had to work with our hands tied behind our backs often enough we just "skip to the end" and use the tools we know for a fact will always be available.
It's probably that same reason that perl persists to the level of popularity it has. Like vi, I know it's going to be there on basically any server I have to work on, and the client probably doesn't care/want or even know how to provision me something less primitive.