Top all-time · #7661
Simonas Kazlauskas
Personal blog · kazlauskas.me · on HN as nagisasystemsprogramming
Simonas Kazlauskas's personal blog at kazlauskas.me covers systems and programming. Since 2013, 10 different Hacker News readers have linked it 11 times. It is still writing: the last post was on 2026-09-09, and you can follow it by feed.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
HN readers link Simonas Kazlauskas's Rust error-handling post, which adds context to errors, and a post about running Tailscale on a robot vacuum or similar device, titled 'Tailscale doesn't quite suck'.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
I am Simonas Kazlauskas, a software engineer based in Vilnius, Lithuania. This is my blog.
Most-linked posts?
- /entries/errors.html3 people · 3 mentions · first linked 2021-04-25
What Hacker News says?
I sill don’t understand is how to write idiomatic code which deals with multiple different error types. I am not sure if it is idiomatic but I have been following the guidelines int this article for general error handling: https://nick.groenen.me/posts/rust-error-handling/ And this article for having context: https://kazlauskas.me/entries/errors.html
Comment linking /entries/errors.html
on “Rust Language Cheat Sheet”Submitted A x64 OS #1: UEFI as a story · 224 points
HN discussionYou can root certain models of robot vacuums and then ssh into them. Most run some variant of linux. Then just install tailscale. There are a few blogs out there of people who have done it[0][1]. It's taking a cloud-based product, de-clouding it, and then connecting it to your own private 'cloud'. Pretty cool all things told. [0] https://kazlauskas.me/entries/tailscale-doesnt-quite-suck [1] https://tailscale.com/blo…
Comment linking /entries/tailscale-doesnt-quite-suck
on “Let's put Tailscale on a jailbroken Kindle”Submitted Should you Rust in embedded yet? as a story · 164 points
HN discussionAh, I see. In short, I consider `From::from` implementations for errors to be an anti-pattern. It is super easy to become lax about adding context with these implementations in place. Especially as code is modified in the future. I describe the approach that I use for errors in a detail in an article ( https://kazlauskas.me/entries/errors.html ) that has already been linked elsewhere in the thread. It is, as far as…
Comment linking /entries/errors.html
on “Rust: Enums to Wrap Multiple Errors”Submitted I reverse engineered a motherboard as a story · 107 points
HN discussionHeh, I opened the comment section to link https://kazlauskas.me/entries/errors.html and https://sled.rs/errors.html :-)
Comment linking /entries/errors.html
on “Rust: Enums to Wrap Multiple Errors”Submitted Fast Page Maps for JIT as a story · 3 points
HN discussionSubmitted Context-preserving error handling in Rust as a story · 2 points
HN discussionSubmitted Due to limitations in the borrow checker, this implies a 'static lifetime as a story · 2 points
HN discussionSubmitted You have no right as a story · 1 points
HN discussion