You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
116 lines
4.7 KiB
116 lines
4.7 KiB
11 months ago
|
<!DOCTYPE html>
|
||
|
<html lang="en">
|
||
|
<head>
|
||
|
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
||
|
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||
|
|
||
|
<!-- Enable responsiveness on mobile devices-->
|
||
|
<!-- viewport-fit=cover is to support iPhone X rounded corners and notch in landscape-->
|
||
|
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1, viewport-fit=cover">
|
||
|
|
||
|
<title>Julio Biason .Me 4.3</title>
|
||
|
|
||
|
<!-- CSS -->
|
||
|
<link rel="stylesheet" href="https://blog.juliobiason.me/print.css" media="print">
|
||
|
<link rel="stylesheet" href="https://blog.juliobiason.me/poole.css">
|
||
|
<link rel="stylesheet" href="https://blog.juliobiason.me/hyde.css">
|
||
|
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=PT+Sans:400,400italic,700|Abril+Fatface">
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
</head>
|
||
|
|
||
|
<body class=" ">
|
||
|
|
||
|
<div class="sidebar">
|
||
|
<div class="container sidebar-sticky">
|
||
|
<div class="sidebar-about">
|
||
|
|
||
|
<a href="https://blog.juliobiason.me"><h1>Julio Biason .Me 4.3</h1></a>
|
||
|
|
||
|
<p class="lead">Old school dev living in a 2.0 dev world</p>
|
||
|
|
||
|
|
||
|
</div>
|
||
|
|
||
|
<ul class="sidebar-nav">
|
||
|
|
||
|
|
||
|
<li class="sidebar-nav-item"><a href="/">English</a></li>
|
||
|
|
||
|
<li class="sidebar-nav-item"><a href="/pt">Português</a></li>
|
||
|
|
||
|
<li class="sidebar-nav-item"><a href="/tags">Tags (EN)</a></li>
|
||
|
|
||
|
<li class="sidebar-nav-item"><a href="/pt/tags">Tags (PT)</a></li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
</div>
|
||
|
</div>
|
||
|
|
||
|
|
||
|
<div class="content container">
|
||
|
|
||
|
<div class="post">
|
||
|
<h1 class="post-title">Programming Rust: Fast, Safe Systems Development - Jim Blandy</h1>
|
||
|
<span class="post-date">
|
||
|
2018-05-22
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/books/">#books</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/jim-blandy/">#jim blandy</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/reviews/">#reviews</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/it/">#it</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/rust/">#rust</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/stars-4/">#stars:4</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/published-2017/">#published:2017</a>
|
||
|
|
||
|
</span>
|
||
|
<p><a href="https://www.goodreads.com/book/show/25550614-programming-rust">GoodReads Summary</a>:
|
||
|
Rust is a new systems programming language that combines the performance and
|
||
|
low-level control of C and C++ with memory safety and thread safety. Rust's
|
||
|
modern, flexible types ensure your program is free of null pointer
|
||
|
dereferences, double frees, dangling pointers, and similar bugs, all at
|
||
|
compile time, without runtime overhead. In multi-threaded code, Rust catches
|
||
|
data races at compile time, making concurrency much easier to use.</p>
|
||
|
<span id="continue-reading"></span><div>
|
||
|
★★★★☆
|
||
|
</div>
|
||
|
<p>First off, this is not a book for <em>learning</em> Rust: This is a Reference Book. A
|
||
|
good one at it, but not for learning.</p>
|
||
|
<p>My inclination to learn Rust is how it deals with errors (it's <code>Result</code> enum),
|
||
|
something that most languages seem to drop out of context or accept some
|
||
|
"catch all" which let developers ignore such errors. Rust doesn't; you
|
||
|
<b>have</b> to deal with errors.</p>
|
||
|
<p>And, in such small thing, which I thought it was very simple and
|
||
|
straightforward... is not. The <code>Err</code> part can be very complex, specially if
|
||
|
you want to keep in line with the rest of the system. Which is good.</p>
|
||
|
<p>Although a good book, it's not great. The explanation for generics is very
|
||
|
convoluted and complex and doesn't help grasping the whole context -- maybe
|
||
|
it's easier if you're already working with a language that has generics. And
|
||
|
then, when you are almost getting how they work, they throw lifetimes in it
|
||
|
and the confusion grows. </p>
|
||
|
<p>Several topics are started and then become "beyond the scope of this book". So
|
||
|
it just brushes some pointers at it and then completely forget about it. I,
|
||
|
personally, would drop some of those -- it could mention that they exist --
|
||
|
and expanding for not being "beyond the scope of this book".</p>
|
||
|
|
||
|
</div>
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
</div>
|
||
|
|
||
|
</body>
|
||
|
|
||
|
</html>
|