paritybit.ca

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit d848f06a489787741e1a451d68d219528740dc08
parent 2ac076bf6af7662b39192fe9b41ebcd303a35724
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Fri,  8 May 2020 23:28:10 -0400

Publish new blog post

Diffstat:
Mpages/blog.md | 1+
Apages/blog/cat-v-considered-harmful.md | 68++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mpages/home.md | 4++--
Mpublic/feeds/sitewide-feed.xml | 68++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mpublic/sitemap.xml | 1+
5 files changed, 140 insertions(+), 2 deletions(-)

diff --git a/pages/blog.md b/pages/blog.md @@ -20,6 +20,7 @@ href="https://social.paritybit.ca/@jbauer">Mastodon</a>. ### 2020 <ul> + <li>2020-05-08 <a href="blog/cat-v-considered-harmful">Cat -v Considered Harmful</a></li> <li>2020-05-07 <a href="blog/unsure-what-to-write">Unsure What To Write</a></li> <li>2020-05-07 <a href="blog/the-joys-of-old-tech">The Joys of Old Tech</a></li> <li>2020-05-05 <a href="blog/refining-my-neomutt-config">Refining My NeoMutt Configuration</a></li> diff --git a/pages/blog/cat-v-considered-harmful.md b/pages/blog/cat-v-considered-harmful.md @@ -0,0 +1,68 @@ +## Cat -v Considered Harmful + +[//]: # "My thoughts after spending a long time looking through harmful.cat-v.org/software." + +[//]: # "main.min.css" + +[//]: # + +<div class="byline"> +<b>Written By:</b> Jake Bauer | + <b>Posted:</b> 2020-05-08 | + <b>Last Updated:</b> 2020-05-08 +</div> + +I spent a long while today going through many of the articles on +[cat-v.org](http://harmful.cat-v.org/). Particularly, I spent a lot of time +going through each entry under _[All software +sucks](http://harmful.cat-v.org/software/)_. On that page is a table listing +software considered harmful alongside non-harmful alternatives. + +After having a cursory look through the table, I went on to read each page +discussing why each bit of harmful software is considered harmful and, for the +most part, there are valid criticisms and explanations given. In most of the +mentioned software categories, in fact, it's easy to see why these programs +would be considered harmful. For example, as much as GCC is a really popular +compiler, there is a ton of complexity behind its code. It is not at all a +simple piece of software. Though, frankly, I'm not experienced enough to know +how much complexity in a compiler is too much nor would I know what could be +changed in GCC to make it more simple. + +Despite most of the examples given making intuitive sense or being backed up +with some quotes by experienced programmers (Rob Pike, Theo de Raadt, and the +like), many of the "things considered harmful" seem to be entirely +opinion-based. Take the license section as an example: "GPL, LGPL, Apache +Software License, MPL, CC", is considered harmful where "ISC, MIT/X, BSD, CC0, +public domain" is not. This is clearly just the authors' opinion and preference +for permissive licenses which tend to be smaller and easier to read and +understand simply because they hardly impose any conditions. Yes, those larger +licenses are relatively harder for a layperson to understand, but hardly +impossible assuming one takes the time to read them. Not to mention the benefits +that copyleft licenses provide for preserving end-user freedom. + +Furthermore, for some of the pages specific to a piece of software, the only +discussion provided is a humorous chat log such as for the [GRUB +page](http://harmful.cat-v.org/software/GNU/GRUB/) or a simple "Q&A" such as for +[GNU Auto*hell](http://harmful.cat-v.org/software/GNU/auto-hell). For someone +such as myself, unfamiliar with the particular complexities underlying some of +this software, these pages aren't exactly helpful and don't do much to show how +the software is harmful. They do explicitly say: + +<blockquote><b>Note</b>: At the moment a detailed rationale is not provided for +most of this, so figuring out why some things are considered more or less +harmful than others is left as an exercise for the reader. Here is a hint: +complexity is the bane of all software, simplicity is the most important +quality,</blockquote> + +though, so I wasn't expecting everything to be plainly spelled out for me with +highly cogent arguments. + +On the whole, I agree with a lot of what is laid out in the explanations. In +general: complexity bad; simple good. It's the viewpoint that I had going in and +the examples definitely strengthened that opinion (I still don't particularly +like Go though). + +_This is my fourteenth post for the +[#100DaysToOffload](https://social.paritybit.ca/tags/100DaysToOffload) +challenge. You can learn more about this challenge over at +[https://100daystooffload.com](https://100daystooffload.com)._ diff --git a/pages/home.md b/pages/home.md @@ -17,6 +17,8 @@ rel="me" href="https://social.paritybit.ca/@jbauer">on Mastodon</a>. src="/img/feed-icon.png" width="15" height="15" alt="Click for RSS Feed"/> </a> </div> +2020-05-08 <a class="feed-item" href="blog/cat-v-considered-harmful">Cat -v Considered Harmful</a> + 2020-05-07 <a class="feed-item" href="blog/unsure-what-to-write">Unsure What To Write</a> 2020-05-07 <a class="feed-item" href="blog/the-joys-of-old-tech">The Joys of Old Tech</a> @@ -35,8 +37,6 @@ rel="me" href="https://social.paritybit.ca/@jbauer">on Mastodon</a>. 2020-04-29 <a class="feed-item" href="blog/interesting-things-for-today">Some Interesting Things For Today</a> -2020-04-28 <a class="feed-item" href="blog/how-far-translation-tools-have-come">How Far Translation Tools Have Come</a> - ### What is a Parity Bit? It is a bit (in the 1's and 0's sense) used in checking for errors in digital diff --git a/public/feeds/sitewide-feed.xml b/public/feeds/sitewide-feed.xml @@ -7,6 +7,74 @@ <description>The feed that covers all notable additions, updates, announcements, and other changes for the entire paritybit.ca website.</description> <item> + <title>Cat -v Considered Harmful</title> + <link>https://www.paritybit.ca/blog/cat-v-considered-harmful</link> + <guid>https://www.paritybit.ca/blog/cat-v-considered-harmful</guid> + <pubDate>Fri, 08 May 2020 23:17:39 -0400</pubDate> +<description><![CDATA[<h2>Cat -v Considered Harmful</h2> + +<div class="byline"> +<b>Written By:</b> Jake Bauer | + <b>Posted:</b> 2020-05-08 | + <b>Last Updated:</b> 2020-05-08 +</div> + +<p>I spent a long while today going through many of the articles on +<a href="http://harmful.cat-v.org/">cat-v.org</a>. Particularly, I spent a lot of time +going through each entry under <em><a href="http://harmful.cat-v.org/software/">All software +sucks</a></em>. On that page is a table listing +software considered harmful alongside non-harmful alternatives.</p> + +<p>After having a cursory look through the table, I went on to read each page +discussing why each bit of harmful software is considered harmful and, for the +most part, there are valid criticisms and explanations given. In most of the +mentioned software categories, in fact, it's easy to see why these programs +would be considered harmful. For example, as much as GCC is a really popular +compiler, there is a ton of complexity behind its code. It is not at all a +simple piece of software. Though, frankly, I'm not experienced enough to know +how much complexity in a compiler is too much nor would I know what could be +changed in GCC to make it more simple.</p> + +<p>Despite most of the examples given making intuitive sense or being backed up +with some quotes by experienced programmers (Rob Pike, Theo de Raadt, and the +like), many of the "things considered harmful" seem to be entirely +opinion-based. Take the license section as an example: "GPL, LGPL, Apache +Software License, MPL, CC", is considered harmful where "ISC, MIT/X, BSD, CC0, +public domain" is not. This is clearly just the authors' opinion and preference +for permissive licenses which tend to be smaller and easier to read and +understand simply because they hardly impose any conditions. Yes, those larger +licenses are relatively harder for a layperson to understand, but hardly +impossible assuming one takes the time to read them. Not to mention the benefits +that copyleft licenses provide for preserving end-user freedom.</p> + +<p>Furthermore, for some of the pages specific to a piece of software, the only +discussion provided is a humorous chat log such as for the <a href="http://harmful.cat-v.org/software/GNU/GRUB/">GRUB +page</a> or a simple "Q&amp;A" such as for +<a href="http://harmful.cat-v.org/software/GNU/auto-hell">GNU Auto*hell</a>. For someone +such as myself, unfamiliar with the particular complexities underlying some of +this software, these pages aren't exactly helpful and don't do much to show how +the software is harmful. They do explicitly say:</p> + +<blockquote><b>Note</b>: At the moment a detailed rationale is not provided for +most of this, so figuring out why some things are considered more or less +harmful than others is left as an exercise for the reader. Here is a hint: +complexity is the bane of all software, simplicity is the most important +quality,</blockquote> + +<p>though, so I wasn't expecting everything to be plainly spelled out for me with +highly cogent arguments.</p> + +<p>On the whole, I agree with a lot of what is laid out in the explanations. In +general: complexity bad; simple good. It's the viewpoint that I had going in and +the examples definitely strengthened that opinion (I still don't particularly +like Go though).</p> + +<p><em>This is my fourteenth post for the +<a href="https://social.paritybit.ca/tags/100DaysToOffload">#100DaysToOffload</a> +challenge. You can learn more about this challenge over at +<a href="https://100daystooffload.com">https://100daystooffload.com</a>.</em></p>]]></description> +</item> +<item> <title>Unsure What To Write</title> <link>https://www.paritybit.ca/blog/unsure-what-to-write</link> <guid>https://www.paritybit.ca/blog/unsure-what-to-write</guid> diff --git a/public/sitemap.xml b/public/sitemap.xml @@ -3,6 +3,7 @@ <url><loc>https://www.paritybit.ca</loc></url> <url><loc>https://www.paritybit.ca/home</loc></url> <url><loc>https://www.paritybit.ca/blog</loc></url> + <url><loc>https://www.paritybit.ca/blog/cat-v-considered-harmful</loc></url> <url><loc>https://www.paritybit.ca/blog/unsure-what-to-write</loc></url> <url><loc>https://www.paritybit.ca/blog/the-joys-of-old-tech</loc></url> <url><loc>https://www.paritybit.ca/blog/refining-my-neomutt-config</loc></url>