Hacker News: throwlifeaway

New comment by throwlifeaway in "Memory safety absolutists"

throwlifeaway — Sun, 26 Jul 2026 21:43:31 +0000

Repeatedly calling Rust "memory unsafe" and then shoving your fingers in your ears when people refute you is not "discussing the limits of Rust's memory safety". Stating that your detractors have "Fil Derangement Syndrome" is not engaging in rational discussion.

> I think the limits of Rust’s memory safety are interesting to discuss, as are the limits of Fil-C’s perf and practicality.

Notably absent from what you claim to be willing to discuss are the limits of Fil-C's memory safety, or the possibility that it could be less safe than Rust.

What you're doing is well explained here:

https://katamari64.se/posts/2026/odin-wikipedia/

New comment by throwlifeaway in "Memory safety absolutists"

throwlifeaway — Sat, 25 Jul 2026 21:10:27 +0000

Pizlo is not a memory safety absolutist. His rhetoric towards rust is a tactic specifically designed to draw more attention to him and his project. It is amplified by people who already had a bone to pick with rust and take joy in giving rust folk "a taste of their own medicine," so to speak. Articles like this are taking the bait.

New comment by throwlifeaway in "Prefer strict tables in SQLite"

throwlifeaway — Sun, 12 Jul 2026 14:59:50 +0000

> This inspired me to add a feature to my sqlite-utils Python library

"me" == "ChatGPT", apparently:

> Can the .transform() internal Python method turn a non-strict table into a strict table?

> No. Table.transform() preserves the table’s existing strictness; it cannot change it. Its signature has no strict= parameter

> add an optional strict= boolean parameter to the transform() method - if it is None (the default) then the strict is not changed, otherwise True means change to strict and False means change to non strict. Implement with red/green TDD and uv run pytest -k

https://gist.github.com/simonw/ab8256b81646ad967a601975e206d...

I appreciate the transparency, at least.