From b477015b087cb5884029830873b66d273c99dbc9 Mon Sep 17 00:00:00 2001
From: "Adam T. Carpenter" <atc@53hor.net>
Date: Fri, 19 Mar 2021 16:07:55 -0400
Subject: published certbot haproxy renewal, added/updated a bunch of drafts
 and CV

---
 drafts/it's not rust vs go.html | 49 +++++++++++++++++++++++++++++++++++++----
 1 file changed, 45 insertions(+), 4 deletions(-)

(limited to 'drafts/it's not rust vs go.html')

diff --git a/drafts/it's not rust vs go.html b/drafts/it's not rust vs go.html
index 8b3d6fc..6826d55 100644
--- a/drafts/it's not rust vs go.html	
+++ b/drafts/it's not rust vs go.html	
@@ -1,6 +1,6 @@
-<h1>It's Not Rust VS Go</h1>
-
-include coworker conversation tidbits draft notes:
+<h1>"Rust or Go?" is not the question</h1>
+<h1>Part 2: (But Rust is definitely the answer)</h1>
+-> part 2 include coworker conversation tidbits draft notes:
 <ul>
   <li>These are two very different languages</li>
   <li>These two languages are solving two very different problems</li>
@@ -43,7 +43,7 @@ include coworker conversation tidbits draft notes:
 </p>
 
 <p>
-  It's not Rust VS Go, it's when to use Rust and when to use Go. And the number
+  It's not Rust vs Go, it's when to use Rust and when to use Go. And the number
   one argument I get for why Go should be used is it's simpler and faster to
   learn and work with. There's the answer! The answer is use whichever one works
   best for you. There's no better or worse, or superiority. Redditors will say
@@ -61,3 +61,44 @@ include coworker conversation tidbits draft notes:
     >source</a
   >
 </p>
+<a
+  href="https://insights.dice.com/2020/08/27/rust-in-trouble-after-big-mozilla-layoffs/"
+  >Is Rust in Trouble After Big Mozilla Layoffs?</a
+>
+<a href="https://foundation.rust-lang.org/posts/2021-02-08-hello-world/"
+  >Hello World! (Rust Foundation)</a
+>
+
+<a href="https://killedbygoogle.com/"> Killed by Google</a>
+
+<p>quotables</p>
+
+<blockquote>
+  Take a look Go as well. I think you will find Go much faster to program in.
+  The other aspect is threading. They have very different threading models. Not
+  sure if you had the chance to research that yet or not
+</blockquote>
+<blockquote>
+  Yes, a big thing is threading. Unfortunately, Rust uses a similar model as
+  Java for threads :(. Go is based on Fibers approach which so much faster for
+  temporary, lightweight requests. Go is definitely superior for HTTP REST API
+  apps. Rust can be better for a single-thread app or general "systems"
+  programming.
+</blockquote>
+<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
+  collection] is not the issue people make it out to be. I started last month
+  porting [a chess] engine to Rust. I recently took a break from it because the
+  syntax and borrow checking were getting insane to deal with. Once I learned
+  about the threading issues in Rust, I have put it on the shelf for now. Rust
+  is still evolving which is good and bad. It needs better IDE and Debugging
+  support than current levels. Hopefully that will continue to improve. There
+  was a big Mozilla shakeup (Nov 2020) where they let go of the Rust developers
+  and cancelled the project. AWS hired them. So honestly, I am not sure which
+  direction the language is going in. Meaning, now that AWS owns the braintrust,
+  I don't know where they are headed. My guess is that AWS is using Rust for
+  some behind the scenes script-like stuff. Not sure. Will be important in the
+  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>
-- 
cgit v1.2.3