Top all-time · #1738
llogiq
Personal blog · llogiq.github.ioprogramming
llogiq writes Llogiq on stuff, a personal blog at llogiq.github.io about programming. Since 2015, 44 different Hacker News readers have linked it 71 times, most often “Rust Performance Pitfalls”. It is still writing: the last post was on 2026-03-20, and you can follow it by feed.
Most-linked posts?
- Rust Performance Pitfalls6 people · 6 mentions · first linked 2017-06-01
- Comparing Rust and Java4 people · 4 mentions · first linked 2016-02-28
- Rust Faster3 people · 4 mentions · first linked 2015-10-03
- Benchmarks vs. The World3 people · 3 mentions · first linked 2016-12-08
- Rust as a High Level Language3 people · 3 mentions · first linked 2020-05-30
- Easy Mode Rust2 people · 2 mentions · first linked 2024-03-29
- Blog: Rust Faster – SIMD Edition2 people · 2 mentions · first linked 2018-09-06
- Rust, a Game Review (2019)2 people · 2 mentions · first linked 2024-01-30
- Out of the Box Dynamic Dispatch2 people · 2 mentions · first linked 2020-03-15
- Rust a Decade Later2 people · 2 mentions · first linked 2025-05-18
What Hacker News says?
> Rust programmers tend to do all kinds of little hacks here and there to make the borrow checker happy. It can add up. The borrow checker is perfectly happy when you copy everything. Do you mind sharing an example? If you're talking about using to_owned or clone without reason, then it's fully on the developer. Some more pitfalls to avodi: https://llogiq.github.io/2017/06/01/perf-pitfalls.html What you say definite…
Comment linking /2017/06/01/perf-pitfalls.html
on “Why asynchronous Rust doesn't work”Submitted Rust Performance Pitfalls as a story · 424 points
HN discussion> You could use LLVM to compile any language to LLVM IR, and then to machine code using a backend. Does that mean every language has the same properties as Rust? Nope, it's largely depend on the language design. > If Node/Java/Go use GC (or VMs), then aren't they more safe than Rust? Yes and No, memory allocation is one of the issue in GC. Go is generally more safe on networking but not security where Rust can manag…
Comment linking /2016/02/28/java-rust.html
on “Rust 1.17”Submitted Comparing Rust and Java as a story · 268 points
HN discussionYou might like https://llogiq.github.io/2016/02/28/java-rust.html
Comment linking /2016/02/28/java-rust.html
on “Announcing Rust 1.7”Submitted Something Secret This Way Comes as a story · 163 points
HN discussionI think you're referring to: https://llogiq.github.io/2019/11/05/fear.html ETA, and here's the discussion thread on the original post: https://www.reddit.com/r/rust/comments/dpakxq/rust_2020_more...
Comment linking /2019/11/05/fear.html
on “The Haskell Elephant in the Room”Submitted Yes, I am still learning Rust as a story · 135 points
HN discussionhttps://llogiq.github.io/2017/06/01/perf-pitfalls.html https://doc.rust-lang.org/1.30.0/book/second-edition/ch13-04...
Comment linking /2017/06/01/perf-pitfalls.html
on “Why is Rust slightly slower than C?”Submitted Rust Faster as a story · 114 points
HN discussion>>Perhaps one should notice that this is one of the few hacks that people aren't doing.<< You told us -- "Since I'm lazy, I'll point out that most of the stuff is indirectly mentioned in this write-up: https://llogiq.github.io/2015/10/03/fast.html" Here's what people will read if they look there -- "However, since the generator only produces 139968 separate numbers, the Haskell code just caches them all in an array.…
Comment linking /2015/10/03/fast.html%22
on “Rust-Doom: A Doom renderer in Rust, with no unsafe code”Submitted Rust Sucks If I Fail to Write X as a story · 72 points
HN discussionSince I'm lazy, I'll point out that most of the stuff is indirectly mentioned in this write-up: https://llogiq.github.io/2015/10/03/fast.html This reminds me I haven't written up stuff for chameneos-redux, which is probably the most fun and over-engineered of them all. The fasta/Haskell thing I was mentioning are the parts at "The Haskell code does a quite clever alternative" and "the Haskell code just caches them a…
Comment linking /2015/10/03/fast.html
on “Rust-Doom: A Doom renderer in Rust, with no unsafe code”Submitted Rust, a Game Review (2019) as a story · 69 points
HN discussionSomebody wrote a macro for the simple cases: https://llogiq.github.io/2019/05/18/momo.html
Comment linking /2019/05/18/momo.html
on “How to speed up the Rust compiler in 2020”Submitted Easy Mode Rust as a story · 68 points
HN discussionDon't discount multiple years of "odd optimizer improvements". They add up. That said, yes, re-writes are probably a bigger thing here. Especially lately: https://llogiq.github.io/2018/09/06/fast.html
Comment linking /2018/09/06/fast.html
on “Using Rust for Game Development [video]”Submitted Rust Mutation Testing as a story · 52 points
HN discussionllogiq wrote a post about this: https://llogiq.github.io/2016/12/08/hash.html
Comment linking /2016/12/08/hash.html
on “Rust vs C Pitfalls”Submitted Corner Cutting vs. Productivity as a story · 16 points
HN discussionI blogged about that some time ago: https://llogiq.github.io/2015/07/09/cow.html
Comment linking /2015/07/09/cow.html
on “String types in Rust”Submitted Comparing Rust and Java (2016) as a story · 11 points
HN discussion> I've been watching Rust on that Benchmarks Game site for a while — it's been interesting to see it go from worse than Java a year or so ago to competitive with C++ To be clear, Rust-the-language has not sped up significantly in the past year. It's just that a few dedicated people decided to try to win the benchmarks game strictly for PR purposes [0]. Chances are, for very algo-heavy (i.e. unrealistic) workloads, t…
Comment linking /2015/10/03/fast.html
on “Path to Rust – A practical introduction”Submitted Rust Performance Pitfalls (2017) as a story · 8 points
HN discussion> there's even a book teaching how to implement doubly linked lists in Rust [1] Doubly-linked lists are an awkward example because the "safety" of a doubly-linked list as a data structure involves fairly complex invariants that Rust can't even keep track of at this point, much less check independently. These things are exactly why the unsafe{} escape-hatch exists and is actively supported. But just looking at the am…
Comment linking /2020/01/10/rustvsgc.html
on “Null References: The Billion Dollar Mistake”Submitted Blog: cargo install clippy as a story · 8 points
HN discussionI'm doing all my development on a HP Chromebook 13 G1. While the CPU is low-powered, and I since ditched the ChromeOS for a custom Linux, it's a fairly capable machine, and very cheap for what it offers. My recent 1-year review is on https://llogiq.github.io/2018/03/02/chromebook.html
Comment linking /2018/03/02/chromebook.html
on “Ask HN: Are Chromebooks ready for serious development?”Submitted Matching Puzzle Pieces and Disappointing Benchmarks as a story · 6 points
HN discussionI have no idea either, maybe "Rust Evangelism Strike Force"? https://llogiq.github.io/2017/09/13/resf.html
Comment linking /2017/09/13/resf.html
on “ReScript aims to be a strictly typed JS, simpler and faster than TS”Submitted Easy Mode Rust as a story · 6 points
HN discussion
