Skip to content
This repository has been archived by the owner on Jan 1, 2025. It is now read-only.

Commit

Permalink
fix perl grammer thing
Browse files Browse the repository at this point in the history
rwxrob committed Dec 19, 2024
1 parent 3f38f91 commit 8c86e81
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion adoc/shut-the-faq-up/why-perl-rocks.adoc
Original file line number Diff line number Diff line change
@@ -128,7 +128,7 @@ The idea that Perl is a "boomer language" is a complete misunderstanding of its

[IMPORTANT]
====
The reason Perl because the defacto language for _all_ backend web development—when there was no JavaScript and no frontend at all—is because the only alternatives were C and POSIX shell, which, as anyone who knows what they are talking about will tell you, is ridiculously insecure and easy to shell-inject. Perl even comes with taint checking (`-T`) and forces the develop to explicitly match any data the originated outside of the script in any way. Python never fucking did that. JavaScript sure didn't. Perl was never intended to do what it because the standard for, it was just that fucking good. Today there are tons of other options for backend web development that are all far superior for that, but _all_ of those language suck ass when it comes to text processing from the command line.
The reason Perl because the defacto language for _all_ backend web development—when there was no JavaScript and no frontend at all—is because the only alternatives were C and POSIX shell, which, as anyone who knows what they are talking about will tell you, is ridiculously insecure and easy to shell-inject. Perl even comes with taint checking (`-T`) and forces the develop to explicitly match any data the originated outside of the script in any way. Python never fucking did that. JavaScript sure didn't. Perl was never intended to do all the web backend processing it was forced to do, it was just that fucking good. Today there are tons of other options for backend web development that are all far superior for that, but _all_ of those language suck ass when it comes to text processing from the command line.
====

== Why Perl still matters
2 changes: 1 addition & 1 deletion docs/shut-the-faq-up/index.html
Original file line number Diff line number Diff line change
@@ -1590,7 +1590,7 @@ <h3 id="_the_boomer_language_myth"><a class="link" href="#_the_boomer_language_m
</td>
<td class="content">
<div class="paragraph">
<p>The reason Perl because the defacto language for <em>all</em> backend web development—when there was no JavaScript and no frontend at all—is because the only alternatives were C and POSIX shell, which, as anyone who knows what they are talking about will tell you, is ridiculously insecure and easy to shell-inject. Perl even comes with taint checking (<code>-T</code>) and forces the develop to explicitly match any data the originated outside of the script in any way. Python never fucking did that. JavaScript sure didn&#8217;t. Perl was never intended to do what it because the standard for, it was just that fucking good. Today there are tons of other options for backend web development that are all far superior for that, but <em>all</em> of those language suck ass when it comes to text processing from the command line.</p>
<p>The reason Perl because the defacto language for <em>all</em> backend web development—when there was no JavaScript and no frontend at all—is because the only alternatives were C and POSIX shell, which, as anyone who knows what they are talking about will tell you, is ridiculously insecure and easy to shell-inject. Perl even comes with taint checking (<code>-T</code>) and forces the develop to explicitly match any data the originated outside of the script in any way. Python never fucking did that. JavaScript sure didn&#8217;t. Perl was never intended to do all the web backend processing it was forced to do, it was just that fucking good. Today there are tons of other options for backend web development that are all far superior for that, but <em>all</em> of those language suck ass when it comes to text processing from the command line.</p>
</div>
</td>
</tr>

0 comments on commit 8c86e81

Please sign in to comment.