The pervert's guide to computer programming languages (2017) [video] • Hacker News Board

Re: The pervert's guide to computer programming languages (2017) [video]

#131

Post by jdoege » Tue, Apr 21, 2020, 3:55 PM UTC

WesternStar wrote: post #122

vesche wrote: post #12

From the video... Psychopath Languages: Javascript, PHP, VBA, and SQL Masochist Languages: C, Assembly, Ada, Brainfuck, and Factor Sadist Languages: Perl, Clojure, Erlang, and Regex Fetishistic Languages: Erlang, Smalltalk, Elixir, and Factor Obsessional Languages: Java, C++, Haskell, Scala, Go Hysterical Languages: Python, Ruby, C#, Prolog, Elixir, and Matlib Depression Languages: COBOL Melancholy Languages: Lisp, S…

Its interesting to me to reclassify language schisms slash internal wars in this context. The C programmers(masochists) vs the C++99 programmers(Obsessives) vs C++11 programmers(Obssessives who want to move to Hysterical). The Raku vs Perl split as a move toward sociopathic behavior. The resistance in go to generics as an aversion of the masochistic to the hysterical. Its super fun.

I view the Raku vs. Perl split as schizophrenic conflict resolution.

Re: The pervert's guide to computer programming languages (2017) [video]

#132

Post by WesternStar » Tue, Apr 21, 2020, 4:21 PM UTC

jdoege wrote: post #131

WesternStar wrote: post #122

Earlier quoted context omitted.

Its interesting to me to reclassify language schisms slash internal wars in this context. The C programmers(masochists) vs the C++99 programmers(Obsessives) vs C++11 programmers(Obssessives who want to move to Hysterical). The Raku vs Perl split as a move toward sociopathic behavior. The resistance in go to generics as an aversion of the masochistic to the hysterical. Its super fun.

I view the Raku vs. Perl split as schizophrenic conflict resolution.

Private equity has been making millions selling the parts of a company for more money than the whole. I don't see how that split is any different.

Re: The pervert's guide to computer programming languages (2017) [video]

#133

Post by b2gills » Wed, Apr 22, 2020, 10:48 PM UTC

DonHopkins wrote: post #105

wwatson wrote: post #102

Earlier quoted context omitted.

The sadist (causing anxiety to the other in order to get the other to announce the rules) wants the other to admit their impotence (in the way that the other develops software). The erlang community wants the other to admit that they can't develop software that has nine nines of availability.

Isn't it sadistic the way Perl and Bash are so ideal for developers gaining control over their employers and ensuring job security by making themselves indispensable (forcing their employers to admit their impotence of firing them) by writing obscure unmaintainable code that only they can understand and modify? You can do that in any language, of course, but Perl and Bash are are optimized for it. While the other han…

I've heard about a merger between two companies.

One use Java, the other used Perl.

At some point both teams were told that they had to add a particular feature.

The Perl team was done well before the Java team.

This was a story from one of the Perl trainers. I don't remember enough about the rest of the video in order to find it online.

Re: The pervert's guide to computer programming languages (2017) [video]

#134

Post by lizmat » Mon, Apr 27, 2020, 2:22 PM UTC

b2gills wrote: post #133

DonHopkins wrote: post #105

Earlier quoted context omitted.

Isn't it sadistic the way Perl and Bash are so ideal for developers gaining control over their employers and ensuring job security by making themselves indispensable (forcing their employers to admit their impotence of firing them) by writing obscure unmaintainable code that only they can understand and modify? You can do that in any language, of course, but Perl and Bash are are optimized for it. While the other han…

I've heard about a merger between two companies. One use Java, the other used Perl. At some point both teams were told that they had to add a particular feature. The Perl team was done well before the Java team. This was a story from one of the Perl trainers. I don't remember enough about the rest of the video in order to find it online.

If we're talking about the same thing: this was about merging their databases, so that either could sell the other company's inventory. Both had an XML-interface for affiliates. It took the Perl team about 3 weeks to be able sell the other company's inventory using the XML-interface. The other company at that point hadn't agreed on a date for a initial design meeting yet.

By this, the company of the Perl team almost doubled its turn-over in 3 weeks. The other company ceased to exist a few years later, with most of its staff integrated in the company with the Perl team.