Unsurprisingly getting some dumb comments on the memory safety video, at the same time some of them are so dumb they might be on to something
=> More informations about this toot | More toots from BrodieOnLinux@mstdn.social
@BrodieOnLinux they complain about Rust fanboys but Rust haters are even more annoying
=> More informations about this toot | More toots from goosewastaken@mastodon.social
@BrodieOnLinux Yes, so this is a strategy. A program can just allocate everything they’re going to use up front and then thats it. No more allocations or frees for the life of the process. IIRC TigerBeetle does this.
=> More informations about this toot | More toots from keyboardg@mastodon.social
@BrodieOnLinux Depending on context, it is a valid strategy:
https://devblogs.microsoft.com/oldnewthing/20180228-00/?p=98125
"Of course it leaks". ... they had calculated the
amount of memory the application would leak in the total possible flight time for the missile and then doubled that number. They added this much additional memory to the hardware... Since the missile will explode when it hits its target or at the end of its flight, the ultimate in garbage collection is performed without programmer intervention.
=> More informations about this toot | More toots from michal@kottman.xyz
@BrodieOnLinux I remember reading an anecdote by someone who worked on missiles, he was told to never free, the missile has enough memory to last until it explodes
=> More informations about this toot | More toots from Geniusak@vivaldi.net
@BrodieOnLinux I think that might be a joke.
=> More informations about this toot | More toots from SteveHeist@mastodon.sdf.org
@SteveHeist It is
=> More informations about this toot | More toots from BrodieOnLinux@mstdn.social This content has been proxied by September (ba2dc).Proxy Information
text/gemini
