Skip to content

Evan Ovadia personal blog

Memory safety without borrow checking, reference counting, or garbage collection

verdagon.dev

Single ownership is one of those concepts that's both easier and more powerful than we realize.

Read on verdagon.dev → Discuss on HN (93) Archived copy

Points: 111
HN comments: 93
Submissions: 1
Cited by: 0 commenters

Software Engineering Programming Languages 2023

On Hacker News

Submitted	Title on HN	Points	Comments
Jun 16, 2023	Memory safety without borrow checking, reference counting, or garbage collection by modernerd	111	93

More from Evan Ovadia

All 12 posts →

Vale's first prototype for immutable region borrowing

2023395 points139 comments Programming Languages details

Accidentally making a language, for an engine, for a game

2022356 points221 comments Software Engineering details

Making C++ safe without borrow checking, reference counting, or tracing GC

2023275 points214 comments Software Engineering details

How to Survive Your Project's First 100k Lines

2023214 points81 comments Software Engineering details

Borrow Checking, RC, GC, and the Eleven () Other Memory Safety Approaches

2024189 points208 comments Software Engineering details

Valen's Memory Safety: A New Kind of Borrow Checking

2026184 points100 comments Programming Languages details

Related posts from the same era

Reverse engineering Ticketmaster's rotating barcodes

conduition20242,305 points714 comments details

Building a Virtual Machine Inside ChatGPT

Jonas Degrave20222,029 points908 commentscited by 16 details

Anyone can access deleted and private repository data on GitHub

Truffle Security Blog20241,983 points374 commentscited by 8 details

ChatGPT Plugins

OpenAI Blog20231,875 points1,106 commentscited by 14 details

Cognitive load is what matters

minds.md20241,769 points721 comments details

Everything that uses configuration files should report where they're located

Chris Siebenmann20231,744 points472 comments details