Right, computers do have loads of RAM. So just spin up a chromium fork for the UI, and a handful of http servers for the different background tasks, pull in a bazillion of dependencies, and... it's gone. The RAM, that is.
No, spin up a worker that listens on a queue and thumbnails an image on request so in an event the thumbnailer crashes on a corrupted image the entire app does not die.
So the same for all other complicated tasks.
It is not that handling run time errors has demonstrated to be a trivial tasks for a main app.
Realistically you wouldn't want to run libparsealltheformats inside your main app anyway, because that's just obvious madness in case someone uses it on files from the Internet and not just files created by their non-evil camera. Of course, everyone does anyway.
I mean, if you're a bad programmer, sure. But we've had multi-core systems for decades at this point, one should know at least basic MT techniques, or, short of that, not to fuck with resources cross-thread unless you know what you're doing
Since we know the programs have bugs, photo formats evolve, some of the files are intentionally broken by "evil things" should not we write complex programs taking that into account rather than think that everyone else is an amateur and our code is so state of the art it will just handle bad conditions flawlessly?
