Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail From: John Ames Newsgroups: comp.os.linux.misc Subject: Re: Memory Safety (Re: Python: A Little Trick For Every Need) Date: Mon, 9 Feb 2026 10:04:49 -0800 Organization: A place where nothing fits quite right Lines: 21 Message-ID: <20260209100449.0000348a@gmail.com> References: <10kl2sr$8rkl$3@dont-email.me> <31stmk1pd8a7q0ekv0is4bd1l5aorcgo95@4ax.com> <9hlumk1lodkjlm9a6egbo2fa79f85v6mad@4ax.com> <10lqdk2$n03u$1@dont-email.me> <10lrt1t$16vf1$1@dont-email.me> <-EOdnRUZmNTqQx_0nZ2dnZfqn_qdnZ2d@giganews.com> <10m28je$38cir$3@dont-email.me> <10m2bqs$39oes$1@dont-email.me> <10m2qvk$3g6mr$1@dont-email.me> <10m4go5$2gva$3@dont-email.me> <10m7b6c$10ebk$7@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Date: Mon, 09 Feb 2026 18:04:53 +0000 (UTC) Injection-Info: dont-email.me; posting-host="57abf9a716b2e559a6fd4174d86160e9"; logging-data="3149193"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/OvF2UaOl1ySFhx+1F0y44dEkRbhkWQUM=" Cancel-Lock: sha1:bSB2vbp31iAmBqPk5J81nO4+U+A= X-Newsreader: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Xref: csiph.com comp.os.linux.misc:81883 On Sat, 7 Feb 2026 16:31:24 -0500 c186282 wrote: > This prompted me to try ferroelectric memory, which is much much > faster. Built a dozen field-project boards using that. Could save a > bunch of relevant vars and values into that mem more often without > slowing down the rest of the app. Been meaning to poke around with that for ages. Obviously the intended application is as an alternative to flash memory for persistent storage of firmware and/or settings, but it's interesting to consider a small homebrew system where it's used as main memory, directly analogous to core - free and indefinite-ish "suspend" with no battery drain! (Volatility of main memory is such a baked-in assumption to every form of computing post-mini era...of course mobile devices have had suspend/ resume for ages, but our OSes are still designed around the assumption that the computer starts with a blank slate and every process starts by getting loaded from disk. It'd be interesting to seriously re-examine that way of thinking...)