Rather than just repeat the first Google result I'll link it[1] as it gives a far more thorough answer than I would. While I welcome innovation I would not wan

Rather than just repeat the first Google result I'll link it[1] as it gives a far more thorough answer than I would. While I welcome innovation I would not want my terminal to be in charge of much more than rendering text and inserting keypresses. Yes there are some helpful things your terminal emulator can do like multiplexing, repeating input across instances, scrolling, text resizing/flowing but these are strictly UI features at no point is the terminal in charge of interacting with the underlying system, that's what the shell is for. The example of typing a URL and having it be rendered by the terminal blurs this line, it is intercepting a command you've typed into your shell (what is essentially a system command) and being executed in the terminal, not the shell. If they want to blur that boundary then they can crack on, it will lead to pain and anguish down the line for the users especially when they find themselves out of their comfort zone without their toys. 1. http://superuser.com/a/144668 http://superuser.com/a/144668