Re:Dealing with Out-of-Memory Conditions in Rust
by IshKebab on Saturday August 14, 2021 @12:20PM
(#28181843)
So now if your code gets into a broken state users have no way to fix it. Awesome.
Re:Dealing with Out-of-Memory Conditions in Rust
by lmilcin on Saturday August 14, 2021 @01:56PM
(#28182666)
Don't make it possible to get your system into broken state?
Why everybody assumes every developer doesn't know what they are doing just because most of them don't?
Re:Dealing with Out-of-Memory Conditions in Rust
by notriddle on Saturday August 14, 2021 @09:27PM
(#28185448)
Because most developers also think they’re one of the rare exceptions.
Re:Dealing with Out-of-Memory Conditions in Rust
by IshKebab on Sunday August 15, 2021 @01:06PM
(#28190380)
Why do so many developers assume that they are the perfect ones who never make mistakes? They think that their programs have no bugs despite the overwhelming evidence that all programs have bugs. But no. Not theirs. Literally all other programmers are idiots and only they write perfect code.
The application saved state to internal database, and even if you cycled power it would just come back to the same screen and same state it was before power cycle.
This wasn't to deal with memory problems (in fact, it had no dynamic memory allocation at all) but rather to deal with some crappy external devices and users that would frequently power cycle things if it didn't progress for more than couple of seconds.