added a bunch and published bad animated page titles

4 files changed, 109 insertions, 80 deletions

diff --git a/drafts/html-for-docs-2020.html b/drafts/html-for-docs-2020.html
index a33bb51..8b5462e 100644
--- a/drafts/html-for-docs-2020.html
+++ b/drafts/html-for-docs-2020.html
@@ -1,20 +1,72 @@
-<h1>Document Writing: MD? LaTeX? WINWORD.EXE? Nope, just HTML</h1>
+<h1>Writing Documents: Markdown? LaTeX? WINWORD.EXE? Nope, just HTML</h1>
 
 <p>
   <img src="https://nextcloud.53hor.net/index.php/s/XaZRfgK3G7ZzWbs/preview" />
 </p>
 
-<p>The year is 2020 and I write the majority of my documents in HTML.</p>
+<p class="description">
+  I've been without MS Word for quite a few years since I switched away from
+  Windows and honestly I haven't needed it. I took notes and wrote documents in
+  Markdown for a while. That was alright because the syntax is easy and any text
+  editor can read a Markdown file. Sometimes I need shareable formatting, so
+  recently I started using HTML for all documents I intend to share, upload, or
+  print.
+</p>
+
+<p>
+  The year is 2021 and I write all my formatted documents in HTML. It sounds
+  needless but if you think about it it makes a lot of sense. HTML after all was
+  designed to be the streaming document of choice when the web was introduced to
+  the world. So it's tailor-made for shareable, digital documents.
+  <a href="https://www.w3.org/TR/html52/"
+    >Over the years the specification has gotten larger</a
+  >, and most of the syntax required by a typical user is present.
+</p>
+
+<p>
+  But why bother? What are the "benefits"? Well, HTML is ubiquitous. And by that
+  I mean literally <em>everyone</em> can read an HTML document because literally
+  everyone has a web browser installed. Friends don't have Word? Use Google
+  Docs? Use Apple Pages? Forget it. I bet you all of those folks have a web
+  browser that was made after 1999. That means they can all read your document,
+  either by visiting it on your site or receiving it in an email.
+</p>
+
+<p>
+  What's easier than reading HTML is writing it. Anyone with a text editor can
+  do it. Heck, even those folks with Word installed can save their documents as
+  [reasonable] HTML. And the tags aren't that hard to learn. I don't think that
+  Markdown is an easier syntax to learn and understand. HTML's tags are only
+  slightly more verbose and the structure is a pro, not a con. It's certainly
+  easier than writing a document in LaTeX. I would even argue in some ways it's
+  easier than working with a WYSIWYG editor. At least the formatting you're
+  looking for isn't getting shuffled from menu to sub-menu.
+</p>
 
-- Literally everyone can read an HTML document because literally everyone has a
-web browser installed - Anyone can print out an HTML document - Anyone can edit
-an HTML document - Writing a document in HTML is easier than writing one in Word
-or Latex
+<p>
+  Sometimes folks want a PDF instead. Okay, fine. For whatever reason PDFs are
+  the reigning document of the land. That doesn't mean you need Adobe Acrobat or
+  some custom setup involving
+  <code>wkhtmltopdf</code>. Or even worse, some strange LaTeX middleware via
+  <code>pandoc</code>. You don't need any of that! The best PDF reader in the
+  world, MuPDF, also comes with <code>mutool</code>.
+  <code>mutool convert [options] file [pages]</code> will convert a variety of
+  formats to or from a PDF. And the results look terrific going from an HTML to
+  a PDF. If you want, you can customize the results by writing CSS into
+  <code>@media print</code> queries. Automate the creation with a script when
+  you safe the underlying document. Sky's the limit!
+</p>
 
 <p>
-  I've been without Word for a few years since I switched away from Windows and
-  honestly I haven't needed it. I took notes and wrote documents in Markdown for
-  a while. That was alright because the syntax is easy and any text editor can
-  read a Markdown file. Recently however, I've started using HTML for writing
-  documents that I intend to upload, print, or send to other users. Here's why.
+  But what about presentations or slideshows? Surely, the "minimal" solution is
+  to use something like Suckless' <code>sent</code> right? Well, you can also do
+  slideshows in HTML! Just a little CSS and some <code>section</code> and
+  <code>a</code> tags and you've got a click-able, full-browser slideshow with
+  images, links, titles, icons, flowcharts, embedded videos, and a printable
+  slide deck. And the best part is that you can instantly share online by
+  dropping it into a public web root. You don't have to use Google Slides or
+  some other third-party slide creator online that none of your friends use.
+  Heck, Suckless <code>sent</code> is just that: yet another slideshow tool that
+  does one thing and nobody but you has it installed. Your HTML slides are
+  <em>just as plain text</em> as a <code>sent</code> deck.
 </p>
diff --git a/drafts/it's not rust vs go.html b/drafts/it's not rust vs go.html
index 6826d55..c9273ff 100644
--- a/drafts/it's not rust vs go.html
+++ b/drafts/it's not rust vs go.html
@@ -1,5 +1,6 @@
 <h1>"Rust or Go?" is not the question</h1>
 <h1>Part 2: (But Rust is definitely the answer)</h1>
+<h1>Part 3: Rust is definitely production ready</h1>
 -> part 2 include coworker conversation tidbits draft notes:
 <ul>
   <li>These are two very different languages</li>
@@ -71,6 +72,32 @@
 
 <a href="https://killedbygoogle.com/"> Killed by Google</a>
 
+<a href="https://dart.dev/overview">The Dart Programming Language</a>
+
+<a
+  href="https://blog.discord.com/why-discord-is-switching-from-go-to-rust-a190bbca2b1f?gi=c8caad873419"
+  >Discord swapped Go for Rust</a
+>
+
+<blockquote>
+  Both Microsoft and Amazon have just recently announced and released their new
+  officially supported Rust libraries for interacting with Windows and AWS.
+  Official first party support for these massive APIs helps make Rust people's
+  first choice when deciding what to use for their project.
+</blockquote>
+<a href="https://blog.rust-lang.org/2021/05/15/six-years-of-rust.html"
+  >Source</a
+>
+
+<a href="https://hub.packtpub.com/is-dart-programming-dead-already/"
+  >Dart -- apples to oranges? I'm not trying to say that go is going the way of
+  dart, I'm trying to say that industry-leading companies aren't always stewards
+  of their creations. take FreeBSD. It's a thriving, excellent operating system
+  capable of "industry-leading company" usage. See the usuals (Netflix, Sony,
+  etc). Look at the FreeBSD foundation. Now look at RedHat and IBM. Again,
+  apples to oranges? No, just a bad argument to make in the first place.</a
+>
+
 <p>quotables</p>
 
 <blockquote>
@@ -85,6 +112,19 @@
   apps. Rust can be better for a single-thread app or general "systems"
   programming.
 </blockquote>
+
+<p>
+  Rust is not a "systems programming" language. Systems programming is not a
+  genre of languages. It's not like saying Italian is a "Romantic language".
+  Systems programming is a specific, targeted programming *application*. It's
+  the destination, the use-case that a language is being applied to. Rust is a
+  general-purpose programming language. I have used it to write a variety of
+  tools, low- and high-level, server-side and client-side, graphical and CLI.
+  Yes, I used it for some systems programming. Also used it to make a very
+  simple and robust web service digested by a variety of other developers at our
+  company.
+</p>
+
 <blockquote>
   The only way is to learn and try both. That's what I did. Most of the info
   from both sides is biased...Go is definitely very fast and [garbage
@@ -102,3 +142,9 @@
   next year or two on which direction things end up going. For Rust to benefit
   long-term, it needs the support of a corporate backer
 </blockquote>
+
+<p>Rust is absolutely ready for production use.</p>
+<p>
+  Anti-Rust zealotry is just as strong as pro-Rust zealotry. The hype goes both
+  ways. No, your talking points shouldn't come from Reddit.
+</p>
diff --git a/drafts/what happens when you remove js from your site.html b/drafts/what happens when you remove js from your site.html
deleted file mode 100644
index e69de29..0000000
--- a/drafts/what happens when you remove js from your site.html
+++ /dev/null
diff --git a/drafts/why does everyone insist on using adobe acrobat?.html b/drafts/why does everyone insist on using adobe acrobat?.html
deleted file mode 100644
index c2a5504..0000000
--- a/drafts/why does everyone insist on using adobe acrobat?.html
+++ /dev/null
@@ -1,69 +0,0 @@
-<h1>Why Does Everyone Use Adobe Acrobat [Reader]?</h1>
-
-<p>
-  This is something that I've never been able to figure out. All through high
-  school I had to use PDFs. And if you wanted to open a PDF, everyone understood
-  that you needed Adobe Acrobat Reader. Even web sites where you downloaded PDFs
-  insisted that in order to open them, you were going to have to follow a
-  download link to make sure you have Acrobat on your PC.
-</p>
-
-<p>
-  Fast-forward a few years into college and I'm using PDFs more than ever. Every
-  professor ever is scanning and uploading course material, so out comes Acrobat
-  Reader for literally every teacher and student. At this point I was actually
-  used to using Firefox (PDF.js) to view PDFs for a couple of reasons. First of
-  all, Firefox usually opened PDFs faster than Acrobat Reader did. Reader was
-  getting bigger with every release, and eventually had a monstrous UI to load
-  up every time I wanted to open a tiny PDF file. Second, Firefox had smooth
-  scrolling for page-width documents. Reader was getting slower and laggier with
-  each release, to the point where scrolling through a PDF was no longer buttery
-  smooth but jittery and stuttery. It also seemed like Reader purposefully
-  wouldn't slide the page when you used a mouse wheel. It would jump down a few
-  lines at a time like it was simulating the down arrow.
-</p>
-
-<p>
-  By my senior year I had switched from Windows to Linux full-time and it was
-  then I found out about <a href="https://mupdf.com/">MuPDF</a> and from then on
-  things were never the same. It's literally the best PDF reader I've ever used,
-  and I tried out quite a few. There are desktop and mobile apps. It opens
-  almost instantly. It lets you easily resize the page with excellent keyboard
-  shortcuts. There are no giant menu bars on either side of the page to squish
-  the document down to an unreadable size. Having a dozen of them open at once
-  doesn't bog down my PC. It's also available for all of the relevant operating
-  systems I've used (Windows, Mac OS, Linux, FreeBSD)! Oh and password-protected
-  PDFs are supported as well.
-</p>
-
-<p>
-  It's a fantastic piece of software And the best part is it comes with a
-  variety of tools to edit and manipulate PDFs as well. If the folks I went to
-  school with thought you needed the free Acrobat Reader to view a PDF, they
-  sure as heck thought you needed to buy Acrobat Pro to edit one. Some of them
-  refused to pay for it and used a variety of online services to upload, split
-  or merge, and download PDFs. I honestly for the life of me can't understand
-  why. MuPDF comes with <code>mutool</code>, which does all of the things I
-  would ever need to do with a PDF. It can attempt to convert a PDF to other
-  formats, like HTML. It can split and combine documents. It can even create
-  them from scratch and sign them.
-</p>
-
-<p>
-  It's also free and open source. Can you imagine that? PDF viewing and editing
-  being free and open source? It's AGPL (in addition to being commercially)
-  licensed by the creators. The only slight drawback is the desktop version
-  apparently does not yet let you fill out forms. Not sure why but this isn't
-  something I use very frequently.
-</p>
-
-<p>
-  It's not the hottest piece of tech out there, but it just plain works and
-  works really well. Maybe the only reason more people I know don't use it is
-  because Adobe is synonymous with the PDF format. It doesn't seem like that big
-  of a deal, but I feel like Acrobat has always been a piece of software that
-  has frustrated new or infrequent users in computing. And that's just not good.
-  Maybe the barrier to using MuPDF is the lack of GUI and abundance of
-  keybindings, but for me that's no sweat. I'd say to anyone to just try it out
-  and see if they like it. It is free, after all.
-</p>