It’s shipping for Windows and Linux. Neither of these uses that kind of sandbox by default (or makes it at all easy to achieve). It could trash the user’s home directory, for example.
$ firejail ./bin
Even the very limited default profile hides things like ~/.ssh and makes the rest read-only (with the exception of ~/.cache and such).> or makes it at all easy to achieve
firejail makes this trivial. You won't be able to steal anything of interest. Making an easy to use sandbox for desktop applications is the main goal of the project. You could have tried it out before arguing against it in what feels like bad faith.
$ firejail bash
-- snip --
$ ls ~/.mozilla
ls: cannot open directory '/home/foo/.mozilla': Permission denied
$ ls ~/.ssh
ls: cannot open directory '/home/foo/.ssh': Permission denied
$ ls -lh passwords.kdbx
-r-------- 1 nobody nobody 0 May 29 14:53 passwords.kdbx
And so on. (The last one is my real password database and it definitely isn't 0 bytes in size.)