Le 21.10.2014 23:37, Steve Litt a écrit :
On Tue, 21 Oct 2014 00:58:27 +0200
lee <l...@yagibdah.de> wrote:
berenger.mo...@neutralite.org writes:
> But my opinion is that, it's the accumulation of tools using
> different slow languages, which will kill the computer's resources
> (shell, python2, python3, php, perl, basic, whatever).
Perl isn't exactly slow, considering what it does.
In any case, pick the right tool for the job --- and I'm finding
perl
really amazing in some regards.
For an interpreter (you know what I mean), when I used Perl it was
fast
as hell. You'd need to go to Lua or Luajit to get a faster
"interpreter".
I do not know if perl or python or dash or ruby or php are fast or not.
I am just wondering, what's the result of having every single single
interpretor, with various programs depending on one or another, on the
same computer.
You know, I think it is something like having a mix between softwares
written for Qt, Gtk, WxWidgets, etc all on the same computer. Alone,
they're all fast, and with other softwares sharing the technology, speed
increases (since you load in memory the dynamic libraries only once,
future uses are accelerated. Theoretically.). But now, when your system
need to load all of those, what's the result? I have the same worries
about interpretors, especially about python, I must admit it.
For dash scripting, it's ok, I know it's not about a fashion
technology. For perl, the same, and it might be actually faster than
dash (which needs external binaries and processes started frequently to
do common things, like using regexes). I know (or I think I do) what it
was made for. And it was not to create a new language better than
everything which exists with new hype technos and with forced coding
style (I have read that perl was written to avoid the collisions of
awk's, grep's, sed's, shells' bugs and to have a more consistent
syntax).
But I am afraid by the use of such languages when then can break
backward compatibility with too much ease. For example, lsof, a tool
which is regularly useful, depends on either perl < 5.12 or
libperl4-corelibs-perl.
But maybe I'm too paranoid about backward compatibility and avoiding
having a different technology for each program installed on my system.
One of the first things I do when writing software is figure what the
bottleneck is. If the bottleneck is the user's molassas slow 140 word
per minute typing, I'll use an interpreter every time so I'm not the
guy doing allocation and garbage collection and bounds checking.
SteveT
Steve Litt * http://www.troubleshooters.com/
Troubleshooting Training * Human Performance
I do not know if perl or python or dash or ruby or php are fast or not.
I am just wondering, what's the result of having every single single
interpretor, with various programs depending on one or another, on the
same computer. Are interpretors that light, that accumulating them does
not cause overhead?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/afac4d6a0f0a36e28ae89aeb877f7...@neutralite.org
