Comment by networked
8 days ago
> Replicating the experience of using something like Smalltalk transcript window.
As far as I know from Pharo, the Smalltalk transcript logs plain text and is less capable than xterm. So what you care about is not the capabilities of the terminal but having a long-lived interactive session/REPL or a REPL integrated with an editor?
> No need for SSH to talk with Windows Core/Nano, it can be done via Web GUI administration, or PowerShell remoting.
I was thinking of the administrator connecting to Windows from their Mac or Linux/BSD machine. I don't know if that's a good idea compared to them getting a Windows VM and using Windows-to-Windows PowerShell remoting as you suggest.
The concept of an XTerm it's far inferior to Emacs either as a REPL with a shell (eshell), the scratch buffer of the whole Elisp environment. Ditto with 9front with remote mounts and device binding. When you can use a remote component you can do NAT by importing /net in the spot from a remote machine. When you import /proc from another one you can suddenly debug processes of another machine.
Acme with shells are still far superior too. I can edit and script the editor's content and panes and run scripts on them. I can reuse Acme as a Mail, Usenet and maybe Irc client on the spot. I can cut, copy and paste with a mouse faster than a keyboard and yet maintain the Sam commands which are like the ex/ed ones but easier for some tasks (recursive searchs) without getting yourself mad with classic regexps. Heck, I can run filters a la vi under Acme but without being bound to a terminal and thus worried about the input/output on pipes.
How come a graphics powered REPL is less capable than a window that pretends to be a tty from the 1970's?
You can certainly use the same Web GUIs from macOS and GNU/Linux as well, as for Powershell remoting, no need for VM when Powershell nowadays is written in modern portable .NET.
> How come a graphics powered REPL is less capable than a window that pretends to be a tty from the 1970's?
I mean the Smalltalk transcript and its capabilities alone, not Smalltalk as a whole. The transcript apparently just logs plain text; xterm supports color and text formatting like bold and italic. I'm guessing that, per > as for Powershell remoting, no need for VM when Powershell nowadays is written in modern portable .NET.
It looks like multiplatform PowerShell remoting uses SSH:anthk
7 days ago
The transcript on Smalltalk is a bad point when the environment itself (the object browser) it what matters in the end. You already have a logical browser far superior to boldted pipes under XTerm. Even 9front has a ndb(1) tool (not just useful for network settings) which can be reused as a small text database a la GNU recutils.
With rio windows I get an actual text stream to copy and paste (and grep and wahtnot), not the text, terminal control codes for bold and colour and often DEC decorations such as the ones in Nethack for walls.