But I agree that in normal input it is often annoying.
Maybe this is just an XKCD moment https://xkcd.com/1172/ ...
There's no need to break normal editing behavior.
I'm nowhere near a hiring position but if I was I'd add assessing that to the application procedure.
It feels like this is part of a set of growing issues, with millennials being the only generation in between gen X / boomers and gen Z that have computer skills and can do things like manage files or read a whole paragraph of text without a computer generated voice + RSVP [0] + Subway Surfers gameplay in the background.
But it was also millennials that identified their own quickly diminishing attention spans, during the rise of Twitter, Youtube, Netflix and the like [1].
I want to believe all of this is giving me some job security at least.
[0] https://en.wikipedia.org/wiki/Rapid_serial_visual_presentati...
[1] https://randsinrepose.com/archives/nadd/ (originally published 2003, updated over time to reference newer trends)
Quite literally laughed out loud at this. I still cannot believe this is a thing people actually do; I thought it was a joke "genre" at first.
Poor typists always slow down processes, and frequently become a bottleneck, local or global. If you can speed up a process by only ten seconds per Thing, by improving someone’s typing skills or by fixing bad UI and workflow, you only have to process 360 Things in a day (which is about one minute per Thing) to have saved an entire hour.
It can be very eye-opening to watch a skilled typist experienced with a software system that was designed for speed, working. In more extreme cases, it can be that one person can do the work of ten. In more human-facing things, it can still be at least a 50% boost, so that two skilled people can beneficially replace three mediocre.
We seem to value the actual craft less and less with each passing day. so everything slows down overall.
It's good enough, it gets the job done and does not cause enough friction for the person to feel the need to improve. Complacency.
If you have to use multiple keyboards, arrows, end, home etc tend to be at different position on the keyboard. Almost no better than using a mouse.
That's were old school vi / emacs shine. CTRL? Always same area, so ctrl-f to go forward? Same gesture whatever brand of a laptop I have to work on.
In my perceived experience, every time a delimiter is opened, it automatically closes, allowing you to move away from it without thinking.
Even in places where this is not available (Slack, comment boxes, etc.), I close the delimiter as soon as I open it
On a french keyboard, ~#{[|\\^@]} all require the "alt gr" modifier key which is usually just right of the space key. So totally outside the realm of shift, caps lock, ctrl or alt.
This feature is useful for me. So are LLMs. If someone doesn't want to use this or that, they are not obliged to. But don't tell me that features that I find useful "suck".
You can always insert the second " as a ghost(?) character to keep syntax highlighting working. But it's not like any modern language server really struggles with this anyways.
You can perhaps imagine an editor that only inserts the delimiter if you type the start-string symbol in the middle of a line.
Can't speak to other editors though.. I don't want to sound like I'm trolling, but they generally feel quite clunky, compared to Emacs (ducks, runs ;p )
It's just matching, and reflecting the way different humans think, and reason, that's all.
(yes, said in jest)
How is it ever wrong, though? If I insert a (, and then a {, and the editor appends so that it's ({}), that's always ?correct. Can it ever not be.
Maybe because on a Norwegian keyboard { is a bit awkward, but I like it. Then even if we're 5 levels deep with useEffect(() => {(({[{[ I can just press ctrl+shift+enter and it just magically finishes up everything and put my caret at the correct place, instead of me trying to write ]}]})) in the correct order.
Whenever you edit something existing that already has the ), ] or } further down and you end up with a ()), []] or {}}. Or when you select some text that you want to replace and start with a quote only to end up with "the text you wanted to replace" instead of the expected ".
I never notice when it works but get annoyed every time it doesn't, so I feel like it never works and always sucks.
I guess it's muscle memory and some people are used to it, but it feels fundamentally wrong to me to have the editor do different basic editing things based on which character is being pressed.
e.g.:
(a + b > c) -> ((a + b > c) -> (()a + b > c) -> no, I was aiming for ((a + b) > c)
(it sound like you're talking about a different feature/implementation, though, since in the annoying case there's no 'completion' shortcut, it just appears)
I think here you are talking about a different thing -- completion of already started parentheses/"/whatever with content in-between, not the pre-application of paired braces or quotation marks, as the author did, no?
I found one place where it makes sense, but it's kind of because of other design choices.
The Typst collaborative web editor automatically doubles "" and $$ and so on. It also breaks document preview/compilation if you have mismatched braces (of some kinds and not others) or mismatched $$. So the delimiter doubling actually helps you having a smooth valid document for a greater fraction of the time while live-editing, but it only really matters when you are collaborating with someone and both furiously typing at the same time.
(if the awesome Typst people are reading this: it's still wrong to not have an option to disable this. I'm deleting so many misfired "" insertions per day..)
Maybe it's like a pale imitation of structural editing? There are editing modes for some editors that more or less ensure the syntax is always valid as you edit, and they of course include this feature.
I have not yet figured out why anyone would choose this behaviour in a text editor. You have to press something to exit the delimited region anyway, whether that be an arrow key or the closing delimiter, so just… why did the first person even invent the idea, which just complicates things and also makes it harder to model the editor’s behaviour mentally? Were they a hunt-and-peck typist or something?
In theory, it helps keep your source valid syntax more of the time, which may help with syntax highlighting (especially of strings) and LSP/similar tooling. But it’s only more of the time: your source will still be invalid frequently, including when it gets things wrong and you have to relocate a delimiter. In practice, I don’t think it’s useful on that ground.