← Feed

Posts

• View post

  After writing this comment I noticed it became a bit ranty, sorry for that. Something about this article rubbed a bit in the wrong way. The relevant section seems to be this: > Browser engines and garbage-collected runtimes are classic examples of code that fights the borrow checker. You’re constantly juggling different memory regions: per-page arenas, shared caches, temporary buffers, objects with complex interdependencies. These patterns don’t map cleanly to Rust’s ownership model. You en...