Orhun Parmaksız
blog.orhun.dev · Personal blog · on HN since 2022
Orhun Parmaksız is a Rust developer and maintainer of Ratatui who writes about terminal tools, packaging, and open source funding.
What HN saysHN links it for the Ratty terminal announcement, which cites TempleOS as inspiration, and for posts on packaging Rust for npm and Ratatui funding.
29HN people shared it
8linked it in comments
45stories submitted
375story points
6 months agolast shared
2022people per year2026
Most-shared posts
- 1Taking Rust to the Cloud: Fast File Sharing4 people · 4 points · first shared 2023 · discussion on HN
- 2Packaging Rust Applications for the NPM Registry4 people · 2 points · first shared 2023 · discussion on HN
- 3Why is stdout faster than stderr?3 people · 44 points · first shared 2024 · 32 comments on HN
- 4Rust terminal projects in 3 years3 people · 3 points · first shared 2026 · discussion on HN
- 5Ratty: A terminal emulator with inline 3D graphics3 people · 1 points · first shared 2026 · discussion on HN
- 6Exploring Open Source Funding: Ratatui's Journey2 people · 10 points · first shared 2024 · discussion on HN
- 7Zig Bits 0x2: Using defer to defeat memory leaks2 people · 5 points · first shared 2023 · discussion on HN
- 8If you have one project and you keep bragging about it, just stop2 people · 4 points · first shared 2023 · discussion on HN
- 9From TUI-Rs to Ratatui: 6 Months of Cooking Up Rust TUIs2 people · 3 points · first shared 2023 · discussion on HN
- 10Kmon Let's manage the Linux kernel modules2 people · 3 points · first shared 2022 · discussion on HN
- 11Show HN: Zero-dependency random number generation in Rust2 people · 2 points · first shared 2023 · discussion on HN
- 12Automated Releases for Rust Projects2 people · 2 points · first shared 2023 · discussion on HN
- 13Building a guitar trainer with embedded Rust2 people · 2 points · first shared 2026 · discussion on HN
- 14Generating terminal user interfaces with Ratatui and ChatGPT2 people · 2 points · first shared 2023 · discussion on HN
- 15Rewriting Sysctl(8) in Rust: Systeroid1 people · 158 points · first shared 2022 · 77 comments on HN
What HN people wrote when they linked it
voidUpdate · 2026-05-11
I was going to comment how it reminded me of TempleOS and the author should look into that, but the accompanying blog post explains how it was inspired by it https://blog.orhun.dev/introducing-ratty/
Sharlin · 2026-05-11
The announcement blog post (https://blog.orhun.dev/introducing-ratty/), which would've been a better submission URL, unsurprisingly says that TempleOS was the direct inspiration of the project.
mtndew4brkfst · 2024-04-26
Seems like a vehicle to try to start another coin network, like Tea.xyz, and it's just burying the lede:
See Drips on https://docs.radworks.org/#projects
I'd first heard of Radicle from this post: https://blog.orhun.dev/open-source-funding-with-ratatui/
bin_bash · 2023-07-20
lol I see a lot of tools using npm to distribute binary CLIs written in compiled languages: https://blog.orhun.dev/packaging-rust-for-npm/
people are way more likely to be setup with npm than they are with cargo
JdeBP · 2023-06-02
It's really rather sad that people, even people advertising a TUI drawing library that draws boxes, don't get Unicode block graphic and line drawing characters to the extent that the box lines in the "title on bottom" example here don't join up.
This is, ironically, because https://blog.orhun.dev/site.css also sets a font-size and a line-height that make the explicit list of fonts that it selects not work. I take these out and go back to using the WWW browser's own pre-supplied monospace fonts and styles for <pre>, and the example appears correctly.
scns · 2022-04-19
Another interesting project by the same author: https://blog.orhun.dev/introducing-kmon/
sayanarijit · 2022-04-19
I find this interesting: https://blog.orhun.dev/introducing-gpg-tui
chatmasta · 2023-02-01
I'm really not a fan of the "download the prebuilt binary from github releases" workflow that's been proliferating along with the popularity of Rust. It seems like a step backward in terms of secure package management, and it's surprising to me that Rust doesn't offer a more out-of-box experience for this, instead encouraging users to build from source. I understand the arguments for this, and I even find some of them convincing - namely, that the inverse problem of opaque intermediate binaries and object files would be much worse as it would cause a cascade of brittle builds and barely any packages would work.
But the fact remains that end users want to download a binary, and the common approach to this is to simply publish them to GitHub actions. Surely Cargo could offer a better option than this, while retaining the ability to build all packages from source (maybe you can only publish binaries to Cargo _in addition_ to the source files... or maybe Cargo.toml could include a link to GitHub releases, and Cargo could include a command for downloading directly from there.)
In the meantime, I've been considering publishing Rust binaries to npm (in addition to GitHub releases). I got the idea from esbuild, which is written in Go but distributed via npm. What do people think of this approach? Here's a recent blog post [0] describing the setup.
[0] https://blog.orhun.dev/packaging-rust-for-npm/