My take on it.
Visual Studio / SQL Server MGMT studio handles this nicely, at least as far as I've encountered it.
If you insert a closing brace (paren, quote, etc.), then I think the appropriate thing to do is to ignore / jump over the closing brace when it is typed by the user. When I type an open paren, go ahead and insert the close paren. But when I type in a close paren (which I do often), jump over that close paren. Don't make me go back and delete it, and don't make me take my hands off the home row to reach for anything (even the arrow keys). That's just wasteful.
SE knows enough about open & close items now to be able to highlight them when you close them, why not jump over them?
SE is the best text editor around, and when it comes to searches, file mods, and cool editing, it's the place to go. But I don't create much code in Slick simply because I get so frustrated typing, then removing, closing characters. I've been doing this too long to change now. Just like the two spaces I put between sentences - something drilled into me 25+ years ago on a manual typewriter. I'm not changing now, even when I try to. I have no hope of not typing a closing character. It's just ingrained by now. In that case, Visual Studio has slick beat hands down.
Jim.