Rainer Weikusat <rweikusat@talktalk.net> writes:
Mart van de Wege <mvdwege@gmail.com> writes:
Henry Law <news@lawshouse.org> writes:
On 12/10/2020 10:38, Mart van de Wege wrote:To you and all tone policers: fuck off. This is Reiner, who never holds
This is fucking horrible code. What is 'vals'? What is 'wk'? What is >>>>> 'cur'? Is it 'current' or 'currency'?
I'm not even pointing at your obvious pride in writing as compact as >>>>> possible by packing as many skis into one expression instead of using >>>>> subexpressions for clarity, just your variable naming alone shows you as >>>>> an absolute egotist incapable of writing code for others.
This post is an example of a growing trend: the completely unwarranted >>>> and vicious put-down of someone in public.
back either.
This is actually Rainer. And he is not responsible for any kind of
"enemy stereotype" you like to push onto him.
Playing 'gotcha' with typos is not helping your case.
Mart van de Wege <mvdwege@gmail.com> writes:
Henry Law <news@lawshouse.org> writes:
On 12/10/2020 10:38, Mart van de Wege wrote:To you and all tone policers: fuck off. This is Reiner, who never holds
This is fucking horrible code. What is 'vals'? What is 'wk'? What is
'cur'? Is it 'current' or 'currency'?
I'm not even pointing at your obvious pride in writing as compact as
possible by packing as many skis into one expression instead of using
subexpressions for clarity, just your variable naming alone shows you as >>>> an absolute egotist incapable of writing code for others.
This post is an example of a growing trend: the completely unwarranted
and vicious put-down of someone in public.
back either.
This is actually Rainer. And he is not responsible for any kind of
"enemy stereotype" you like to push onto him.
"Mart" == Mart van de Wege <mvdwege@gmail.com> writes:
Mart> Remember how this "be smarter than the rest of the sheep" led to Perl Mart> golf, and people making jokes about 'write-only' language? The community"Mart" == Mart van de Wege <mvdwege@gmail.com> writes:
Mart> spent years rectifying that and pushing best practices, so why the fuck Mart> would you accord any respect to a dinosaur from that time?
I'd say JAPHs (which predated Golf) deserve an equal or greater blame,
for which I have repeatedly apologized.
I don't think anything "deserves a blame" for this ill-conceived bundle
of fiction. People refer to Perl as "write-only language" because of the liberal and unconventional use of symbol characters in the syntax (a significant barrier to understanding for people who have "general
programming knowledge" but who are not very familiar with the Perl
syntax itself).
And then, because it used to be the language of choice for people whose
only mode of operation is "ingenuitively hack something together which sometimes works somehow" (I've seen examples of such code) as it was
easier to use than C. Nowadays, most of these people use Python and
their Python-code is just as "write-only" just in a differently looking
way.
On Thu, 15 Oct 2020 15:13:33 +0100, Rainer Weikusat wrote:
I don't think anything "deserves a blame" for this ill-conceived bundle
of fiction. People refer to Perl as "write-only language" because of the
liberal and unconventional use of symbol characters in the syntax (a
significant barrier to understanding for people who have "general
programming knowledge" but who are not very familiar with the Perl
syntax itself).
Perl is far from "write only". I have perl scripts from 2007 that I am
still maintaining because they're useful. I am an Oracle DBA, so I have
Perl scripts to dump tables to CSV or XML, draw ER diagrams of the given schema and summarize performance aspects of an Oracle database in a few
nice reports. I have been adjusting those scripts from Oracle v8. Before that, I was using Perl4 and "oraperl", Perl4 executable with Oracle
bindings linked into the executable itself. Whenever there is a new major version of Oracle, there is a need to modify my scripts. I've never had
any problems with them
And then, because it used to be the language of choice for people whose
only mode of operation is "ingenuitively hack something together which
sometimes works somehow" (I've seen examples of such code) as it was
easier to use than C. Nowadays, most of these people use Python and
their Python-code is just as "write-only" just in a differently looking
way.
Python is much more verbose. And the idea of the mandatory indentation
comes from COBOL, today a largely forgotten monstrosity. Python is a
truly OO language, as opposed to Perl, which is mostly procedural.
However, it is true that Python has won and it is practically the only scripting language in wide use today.
Python isn't that bad. You have to stop worrying and learn to love
Python. Any resemblance to the subtitle of "Dr. Strangelove" is purely accidental.
I don't support this claim ("write only language"). But the expression I originally posted,
@vals = @$kv{@{$$cur[KWDS]}}
is going to look pretty daunting to someone not familiar with Perl dereferencing syntax: stripping out the letters leaves one with
@${@{$$[]}}
and - to the best of my knowledge - constructs like this area really
unique to Perl. Something I'recently noticed while having to read through some code written in Rust: conventions for use of symbol characters one
isn't familiar with appear very bizarre when one encounters them.
Also, I think people simply don't like the feeling of looking at
something which obviously must have made sense to somebody despite they
don't have the slightest idea what it means. In order to get around
that, they fault the language for being unknown to them.
or using it because someone supposed to give order wants it to be used.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 285 |
Nodes: | 16 (2 / 14) |
Uptime: | 72:42:25 |
Calls: | 6,489 |
Calls today: | 2 |
Files: | 12,096 |
Messages: | 5,275,833 |