Running nvim as child of terminal process, not interactive shell

I just started playing around with running nvim as a direct child process of my terminal emulator, e.g.

alacritty -e nvim

as opposed to running an interactive shell, e.g.

alacritty -e bash

and invoking nvim from the shell.

So far, the only behavior difference I’ve observed is that suspending (<C-z>) drops you into a blank, unusable terminal, which you mush terminate with Ctrl-C.

Has anyone else played around with this? Are there any other differences in behavior?

I’m considering trying this out for a while (and mapping <C-z> to Nop), since I can always run a shell inside a neovim :term window. I suppose I could also map <C-z> to open a :term window.