Minor correction in one example:

use crossbeam_channel as channel;

// Create a non-buffered channel.
let (tx, rx) = channel::unbounded();

// Create a buffered channel with a capcity of one.
let (s, r) = channel::bounded(1);

[...]

The first comment should be Create a buffered channel of unlimited capacity.. As you explain above this point, it would have to block when you send if it were unbuffered.

I too had issues around syncing my own files using pass in the past and eventually settled on LastPass. In my opinion, it’s worth paying $24 a year for premium support which gives me 1GB of encrypted storage and more two-factor authentication options. Plus having the app seamlessly sync to my phone is great as I can just copy passwords to the clipboard for other apps on my phone. It’s been easy to use and I enjoy not having to worry about passwords anymore.

Edit: Sorry that this was seen as spam. I realized after the fact that it was a little zealous. I am by no means connected to or trying to endorse LastPass.

I have been toying around with the idea of writing a daemon that is similar to fail2ban. I use fail2ban on my small VPS now and have found it to be memory hungry. I plan on using Rust and exploring the problems that come with monitoring log files. There isn’t any code yet but I will get to prototyping soon.

I ended up writing a few middleware handlers following the pattern mentioned here so I could use alice to chain them. Combining this with popular community middleware made it easy to write robust servers.

Reading more about Rust as I prepare to start a job that will largely have me writing in it.

The new position puts me as the only engineer on a project initially and my usual languages are C and C++. I’m worried about safety of a system I’m writing by myself. Rust should provide sufficient safety and strictness to help mitigate a large portion of problems with writing low level code, especially since this will be completely green field development.

I’m also excited to be using a modern toolchain for development (e.g. cargo) :).

This was a refreshing post as the author didn’t go on about generics or how all of Go’s third-party package managers are horrible. The linked articles on writing effective Go and benchmarking were great to read again as well.

I haven’t used Perl for a few years now and reading this reminds how much I enjoyed it. I wonder what I have been missing and what has been added to the language and community since 2015. It’s great to hear that there is no slowing down for Perl.

I just moved into my new place this past weekend, so lots of unpacking and changing my address for banks and such. After getting done with all of those tedious things I plan on picking back up on some Rust work. I had written a nom parser for the Redis crate but haven’t attended to it since I started escrow.

I am in week three of my new job so I haven’t been able to settle in enough to where I want to program in my free time. Although the project I am trying to make progress on is a client for NSQ written in Rust. It’s been fun to learn more about binary protocols and the asynchronous world at the same time.

For those that are interested NSQ can be found at this page: http://nsq.io

The thing that bothers me the most is how some sites enforce a small maximum length. For example, my bank’s site doesn’t allow passwords over 14 characters. Since I use a password manager I would have liked to make one that is much longer.

I’m mostly toggling between Rosetta albums at the moment. Flies to Flame and The Anaesthete are some heavy albums that keep me focused while coding.

I realize this post is full of buzz words, but:

Since Tokio released version 0.1 last week, I have been writing a StatsD clone in Rust. I wanted to dive into asynchronous servers and this seemed like an achievable project.

Outside of work and programming, I am trying to get myself into the habit of exercising again. It’s hard to get motivated after work to go to the gym and especially hard to do it alone. I have also been thinking of getting into juicing. One of my coworkers has suggested an Omega brand model but I don’t know if I want to spend over $300 for my first juicer. It may be worthwhile though in the long run.

Long live the dispassionate programmers! They get the documentation written and the boring bugs ironed out, when the passionate programmers have finished 80% on their latest cool Proof-of-Concept and are moving on to their next one.

At home, some Rust operating system fun. Porting a microkernel I last worked on eight years ago; it’s so much nicer to use something-that’s-not-C.

At work, working on our new Markdown parser (… in C) and the transition of our existing user content from old-non-specified-Markdown to an actual spec.

I have been using a Model S keyboard for about a year now and I couldn’t imagine using anything else at this point. Mechanical keys really do have a distinct feel and I have noticed I have much more accuracy.

The Model S comes only in a wired option but it has two extra USB ports on the side that can be used. I can’t say I dislike anything about it other than the noise but that can be solved with having brown keys instead of the blue ones.

Between this and the Xi editor, I am impressed how Raph has shown Rust’s strengths for system software. I hope these projects continue gaining traction moving beyond a useable proof of concept.

I’m finally back to Rust coding and picked up my work on a CouchDB client again.

I’m in dire search for a catchy name.

Are passwords ‘broken’ in general? I don’t see the need to fix them.

This should probably include “(2008)” in the title, it’s old enough that “the old way” has been new and then old again, again.

Rust lets you borrow stuff, just remember to always use the & and you’ll be fine.

This is what I had the hardest time coming to terms with when trying to break my code down into functions when I was beginning to learn Rust. But instead of thinking of the ampersand as the “address of” operator, remembering that it is the “borrow” operator makes a lot more sense. You are just giving that data to something else for it’s execution and then it’s your (caller) data again.