Tramp works a lot more reliably if you customize where Emacs puts your backups and autosaves, such that they're stored locally instead of remotely. The Emacs wiki has details on how to do that: https://www.emacswiki.org/emacs/BackupDirectory

The biggest problem I have with Tramp performance is much deeper, the need to open a new connection for every request - it makes integrating other modes with Tramp much more difficult than I would hope for (e.g. I tried to make kubernetes-mode work over tramp, and it mostly did, but each refresh had to reconnect, which would freeze the whole Emacs GUI for a second or so; thankfully kubel-mode has a more complete implementation that handles this gracefully).

I've had this in my config for a long time. Seems to make tramp work a lot better:

    ; use ssh instead of scpx mode for tramp
    ; this should work a lot better with ssh connection sharing
    (setq tramp-default-method "ssh")

This was problematic even with SSH multiplexing?

You still have this problem even with a control master setup with ssh?

I can't and don't blame tramp, per se. My internet has regular hiccups of being completely disconnected. Pretty sure that is not fixable. :(

Not by Emacs, but locally storing backups and autosaves means it only matters when you're actively reading or writing a file via Tramp.

Absolutely. It just sucks, as my build are so much faster on the remote machine. :)

That is, a lot of my remote editing is not just idle edits, but edit, run build, burn down compile output of tests and other items I'm working.

If I really want hell, I'll try and run lsp remotely.

None of this would matter, if I hadn't built up so much muscle memory from when I did have good internet and it did just transparently work.

I work in the medical field, which requires me to view large xml files and multi patient csv files with years of patient history. The CSVs contain embedded pdf strings that are long strings of bytes in the file. Emacs struggles to copy and paste, and move around in the large CSVs.

For the large XML files, I have to switch to fundamental mode, because it struggles to highlight everything, and sometimes the xmls are pure ass and are basically all on one line. I've written a python script that will prettify the xml because emacs locks up when I try to do that. My colleagues just tell me to use sublime text.

Ah, yes. Long lines are known bad. I will be excited to see anyone give a way to fix that with minimal impact on the rest of the system.

I'm curious why other editors don't trip as badly on long lines.