I’ve been working on some classic Mac projects but I kept tripping over text encodings. My toolchain for the projects is Rust and assumed there’d be a solid, maintained crate for this, but I couldn’t find one. So I made one that follows Apple’s official Unicode maps.
\n", "date_published": "2026-08-16T18:10:55-05:00", "url": "https://b10g.xyz/2026/08/16/macencoding-on-cratesio-ive-been/", "tags": ["apple","development","mac","classic mac","rust"] }, { "id": "http://codybrom.micro.blog/2026/08/07/rustlangrust-is-adopting-an-llm/", "title": "rust-lang/rust is adopting an LLM policy", "content_html": "Jynn Nelson, writing for The “Inside Rust” Blog:
\n\n\nAt the time of writing, there are 1,281 open PRs to rust-lang/rust. This represents a staggering amount of time invested by both authors and reviewers. We have long had the problem that there are more people who want to write code than people willing to review it. With the advent of LLMs, this problem only gets worse.
\n
If you’re technically minded, the policy they agreed to adopt is an interesting read, but the overview has its own summary:
\n\n\n\n", "date_published": "2026-08-07T16:20:07-05:00", "url": "https://b10g.xyz/2026/08/07/rustlangrust-is-adopting-an-llm/", "tags": ["development","ai","rust"] } ] }It’s fine to use LLMs to answer questions, analyze, distill, refine, check, suggest, review. But not to create.
\n