Top all-time · #14142
hobofan's lil' website
Personal blog · hobofan.com/blog · on HN as hobofanprogramming
hobofan's lil' website is a personal blog at hobofan.com about programming. Since 2021, 5 different Hacker News readers have linked it 6 times, most often “Rust’s async isn’t colored”. No feed was found, so read it on the site itself.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link this blog for posts on Rust interop with other languages (bindings, extending Python and others from Rust) and on whether Rust async is 'colored' (function colouring).
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
-
Most-linked posts?
- Rust’s async isn’t colored3 people · 3 mentions · first linked 2021-03-10
- /rust-interop/2 people · 3 mentions · first linked 2022-06-08
What Hacker News says?
Rust seems to excel in having an ecosystem that provides binding helper libraries like PyO3, Neon and napi-rs, Helix, etc. which both ensure "if it compiles, you're doing the C glue properly" and provide a layer for automatic type conversion. ...so requiring `use of "unsafe"` is often akin to forbidding Cargo/pip/NPM/etc. and then calling the language un-productive or faulting a procedural/imperative language for pe…
Comment linking /rust-interop/
on “Rust Is Hard, Or: The Misery of Mainstream Programming”Submitted Rust’s async isn’t colored as a story · 116 points
HN discussionFirst it was "Rust's async isn't f#@king colored!" ( https://www.hobofan.com/blog/2021-03-10-rust-async-colored/ ) Then "Rust async is colored, and that’s not a big deal" https://morestina.net/blog/1686/rust-async-is-colored And now it's a good thing. Honestly, this sounds like somebody struck Achilles' heel of Rust and it hurts. They're neatly covering 3 stages of grief over these 3 articles, and I wouldn't be surp…
Comment linking /blog/2021-03-10-rust-async-colored/
on “Red and blue functions are a good thing”Submitted Rust's async isn't F# king colored as a story · 7 points
HN discussionYou really want to be using C++ and Rust as little as possible - ideally only for high-performance code. The rest of your application should be developed using a RAD language like C# or Kotlin. Interoperability between C# and C++ right now is really great with first-party build tooling support from MS. Rust, as far as I know, doesn't have a great interoperability story with any other language except for, ironically,…
Comment linking /rust-interop/
on “Ask HN: Are there any good reasons to use C++ over Rust for new projects today?”That's actually one of my reasons for writing in Rust whenever possible. The Rust ecosystem has a broad collection of tooling for using Rust to extend other languages, so there's minimal chance something I wrote in Rust will have to be rewritten to use it in a project in another language. See https://www.hobofan.com/rust-interop/ and https://areweextendingyet.github.io/ In Python's case, there's also maturin, which…
Comment linking /rust-interop/
on “Rust vs. Go in 2023”