Rust is infamous for having a steep learning curve. The borrow checker is the first boss you must defeat, but with a good mental model of how memory works, how objects move, and the rules that the borrow checker enforces, it becomes second nature rather quickly. These rules may sound complicated, but really, they are about understanding the fundamentals of how a computer works.
Source: Rust is hard, yes, but does it matter?, an article by Julio Merino.
Let's see how a modern compiler and type system helps prevent many bugs and thus helps increase the security for everyone and reduces the costs of software production and maintenance.
Source: Bugs that the Rust compiler catches for you, an article by Sylvain Kerkour.
There are basically two types of client applications on the internet:
- Clients that use the request-response model. One request will generally result in one response. Some examples would be web browsers and many API clients.
- Clients that receive a continuous stream of data from a server and may or may not send data back at any time. Examples of this type would include chatbots, automated trading applications and multiplayer video games.
In this article, I will describe a fairly general way to use Haskell for constructing a specific kind of clients of the second type: clients that listen to a single network socket and send replies to that same socket, possibly while maintaining state. This article assumes basic proficiency with Haskell and networking.
Source: Making type-safe internet bots with Haskell, an article by Wander Hillen.
On a post-apocalyptic Earth, a robot, built to protect the life of his creator's beloved dog learns about life, love, friendship and what it means to be human.
In the evening we watched Finch. I liked the movie and give it a 7 out of 10.