Hypertile: A zero dependency runtime tiling engine for Ratatui inspired by Hyprland 🦀

#rust #rustlang #ratatui

Malus: Clean room re-implementations as a service: https://malus.sh/

So real.

Want to transcribe speech locally from your terminal? 👀

🎙️ **scriptor** — Real-time speech-to-text CLI & TUI

💯 Speak into your mic and get instant transcription. Fully local, no cloud!

🦀 Written in Rust & built with @ratatui_rs

⭐ GitHub: https://github.com/giacomopiccinini/scriptor

#rustlang #ratatui #tui #speech #terminal #transcription #devtools

Do we need yet another person crashing out about Apple’s design decisions? Am I doing it only because it’s fashionable to be on Apple Design Hate Train these days? I’ll be honest: I don’t know. But I have been bothered by Apple’s approach to some of its keyboard design for a while.

Even if you don’t care about any of this, it might be a fun visual history of the most tricky of modern modifier keys: the [Fn] key. Hope you like it!

https://aresluna.org/fn

RE: https://typo.social/@fontra/116183016588316849

The blog post is a very interesting write-up, I suggest everyone interested in the font making to read it.

The technical part at the end is the most interesting to me. I’m particular proud of the very neat trick that allows #Fontra to emulate glyph positioning while maintaining interaction between it and manually written feature code.

For context. Font editors will generate positioning features from kerning and anchor data in the font.

Sometimes one wants to add some other feature code before or after the generated ones (e.g. move a dot contextual after being positioned by the default anchor to avoid a clash that happens only in a certain context). The order of the generated and manual code is important, since one might depend on the output of the other.