To be similarly pedantic: Ctrl+C is a hotkey that sends the corresponding ASCII code / codepoint to signal something, it is not an ASCII code itself.

You could have the same character be sent by using Ctrl+Q (if you were to remap it), and not break compatibility with other processes while doing so: the codepoint being sent would be the same. From a technological perspective there is nothing special about the key combination Ctrl+C specifically, but altering this behavior in a terminal absolutely wreak havoc on the muscle memory of terminal users, and altering it’s behavior in a text editor on everyone else’s.

The key issue is that the request is to change behavior in one place (browser) to match that of a rare case (terminal), causing a mismatch with the frequent case (office suites, mail programs, …). The terminal is the odd one out, not the browser, and ought be the one to change the default for the reason you provide.

In practice, a terminal is a special case and not just a text input window, and current convention is that Ctrl + C aborts / cancels.

(You could of course have a duplicate hotkey, but now you are inconsistent w.r.t. other browsers, and there will be someone else who will be annoyed by the difference)

Yep. LLMs are at their core text completion engines. We found out that when performing this completion, large enough models account for context enough to perform some tasks.

For example, “The following example shows how to detect whether a point is within a triangle:”, would likely be followed by code that does exactly that. The chatbot finetuning shifts this behavior to happen in a chat context, and makes this instruction following behavior more likely to trigger.

In the end, it is a core part of the text completion that it performs. While these properties are usually beneficial (after all, the translation is also text that should adhere to grammar rules) when you have text that is at odds with itself, or chatbot-finetuned model is used, the text completion deviates from a translation.

Privacy concerns are valid when an external server needs to be queried, like if you were to use DeepL or Google Translate for this stuff, or for any LLM related muck, but they have been accounting for this already by making things work locally. For example, translations performed fully on device, and are an example of a feature I wanted.

Like many here, the entire AI browser idea doesn’t appeal to me at all, but I also struggle to come up with ‘features their users want’ if I take myself as an example. I have previously used Vivaldi, and while it is much more full featured, it doesn’t add any features that I actually end up using frequently.