So I love to talk about Ceph and MicroCeph, and the awesome nerds from the Grazer Linuxtage in a weak moment agreed to have me, so I gave a talk!
If you want to chat about MicroCeph find us on Matrix: https://matrix.to/#/#ubuntu-ceph:matrix.org …
So I love to talk about Ceph and MicroCeph, and the awesome nerds from the Grazer Linuxtage in a weak moment agreed to have me, so I gave a talk!
If you want to chat about MicroCeph find us on Matrix: https://matrix.to/#/#ubuntu-ceph:matrix.org …
For my first time ever I travelled to FOSDEM in Brussels!
FOSDEM apparently is famous for it's crowds, and I'm not a fan of those, but I have to say it was an awesome experience nevertheless. So many great talks, so many awesome nerdy people :-)
I had the opportunity to …
This post is a summary of chapter 23 in the Rust book, "Foreign Functions", the final chapter in the book.
Apparently there's lots of code out there that's not written in Rust. Rust's foreign function interface (FFI) allows calling C and C++ functions from Rust, providing access to low-level …
For this post I'm summarizing chapter 22 of the book, "Unsafe Code"
Unsafe code is for bypassing Rusts safety mechanisms. You're telling the compiler "this'll work out, trust me". Not all safety mechanisms are bypassed – but you can now call unsafe funcs, use unsafe pointers, and call functions in …
For this post I'm summarizing chapter 21, "Macros" of the book.
Macros are the more dynamic part of Rust, aka metaprogramming; e.g. defining traits, generating boilerplate and such.
We saw the assert_eq!
already. One of
the things macros do that can't be done with functions is refer to …
For this post I'm summarizing chapter 20, "Asynchronous Programming".
In the previous chapter we've been talking about concurrency via threads. Threads are, of course, expensive. Some systems do their own scheduling of lightweights threads/processes (e.g. Erlang) to come around this. Rust doesn't have a VM / runtime built-in …
This post summarizes chapter 19, "Concurrency". The concurrency chapter introduces has this nice bit at the beginning: "Experience inculcates a healthy skepticism, if not outright cynicism, toward all multithreaded code". Yes, yes it does.
All the safety features Rust brings with it should come to good use here.
This post summarizes chapter 18, "Input and Output"
Rust I/O is organized around three basic traits: Read, BufRead, and Write. Read does byte-oriented input, BufRead buffered reads (lines of text and similar), Write does output.
Example Read types are Stdin, File, TcpStream; BufRead: Cursor and StdinLock. Examples for …
All about bytes, chars, unicode, formatting and regexes. Covers chapter 17, "Strings and Text"
The book starts off with an overview of Unicode which I will skip here, except to say that Rusts String and str represent text as utf8
Rust chars are 32bit Unicode code points …
Page 1 / 3 »