Cranston's Life - Rust and More Rust

For some programmers, making an HTTP request is an EXTREMELY COMMON activity!

Such programmers find themselves wanting and needing a library to help them make HTTP requests EFFICIENTLY and SAFELY.

There is an article called Smoke-testing Rust HTTP clients and it is about putting some Rust HTTP client libraries TO THE TEST!

Some of the libraries tested include reqwest, ureq, isahc, http_req, attohttpc, minreq, and cabot.

The article tells quite a tale of HARDSHIP!

Network code is not always so easy to write well but I am very SURPRISED about how the article author described the Rust state of affairs!

The article's conclusion says "The place of the go-to Rust HTTP client is sadly vacant."

I have not yet done any HTTP clienting with Rust but I did not think that there would be so many potential problems with SO MANY Rust HTTP client libraries!

The lesson I have learned from the article is beware of BUGS and UNSAFE CODE deep in libraries and their dependencies!

I must STUDY the code of Rust HTTP client libraries that I might some day use, including their dependencies.

It is so easy to focus on the GOOD but sometimes we must also focus on the BAD!

Diego Pacheco has written an article called The dark side of Rust Language.

It gives insight into the BENEFITS of Rust but it also talks about the NEGATIVES of Rust.

One negative is the string situation, of which Diego identifies 6 string types and the DIFFICULTIES that so many string types can bring!

While SIX string types seems so UNNECESSARY there maybe is a good explanation for it.

Diego also writes of how some Rust libraries are immature and do not always have good documentation, but I do think that this is a problem that affects EVERY programming language to some degree!

The CHALLENGING nature of ownership is also described as a negative.

What this article reminds me is that Rust has TRADEOFFS.

Some parts of Rust are SO GOOD, but there are some parts of Rust that are BAD too.

With the GOOD comes the BAD!

I must not forget that Rust has TRADEOFFS.

I have read an article called Rust: First Impressions by Ruben Vermeersch and it is about first impressions with Rust.

What I learned from this article is that Rust is AMBITIOUS but Rust is also STRICT.

Understanding lifetimes can be HARD.

While there can be challenges there can also be BENEFITS from those challenges.

I am now hoping that Ruben will someday share SECOND IMPRESSIONS after using Rust some more!

Microservices are something that many programmers use and build DAILY.

Diego Pacheco shows us one way of using Rust to build a microservice in the Building a Microservice with Rust article.

I must study the CODE and ARCHITECTURE of this Rust microservice example!

Nick Fitzgerald has written an article called Synthesizing Loop-Free Programs with Rust and Z3.

I described it as an article but really I think it is more like an ACADEMIC PAPER!

Give yourself LOTS of time to read this work because it is DEEP and THOUGHT PROVOKING!

I must study this knowledge some more, because it is VERY INTERESTING to me!