Live data from Hacker News

HyperTerm – JS/HTML/CSS Terminal

hyperterm.org

51–60 of 267 posts

Re: HyperTerm – JS/HTML/CSS Terminal

#51
post #37

Earlier quoted context omitted.

How about the fact that your computer now has three enormous copies of chromium on it for no good reason?

How many copies of unix (partitions, vms, containers) do you have on your computer?

TinyCore Linux is 12 MB. A fully functional Unix(-like) system, including an X server.

So, for one Javascript-written terminal app, you can install a full Linux system with X and a window manager 10 times (Hyperterm.app is 122 MB).

Re: HyperTerm – JS/HTML/CSS Terminal

#52
post #19

The folks who make HyperTerm might have something to say about your product naming... http://www.hilgraeve.com/hyperterminal/ Edit: I'm surprised more people in the HN crowd aren't familiar with HyperTerm (Yes that is the name and what everyone called it for many many years) It was bundled with Windows up to 7, and is still used heavily in industrial control areas.

Perhaps a rename to "HyperTermiML" is in order.

Re: HyperTerm – JS/HTML/CSS Terminal

#53

Earlier quoted context omitted.

Trivial apps depending on 14+ million lines of code is not a good thing. Edit: @michaelmior I think you know what I mean.

I think a good terminal emulator is far from trivial. Edit: I'm not sure I do know what you mean. I agree that building trivial apps in Electron probably doesn't make sense. But my terminal emulator is something I spend most of my day using. If building that on top of 14 million lines of C++ gives me a better piece of software, I'm all for it.

Does it though? iTerm2 is the most feature-rich terminal I've ever used, and even then it's several orders of magnitude smaller then Electron (cloc says it's around 111K lines of Objective-C, with around 38K more lines split across Python and C++).

Re: HyperTerm – JS/HTML/CSS Terminal

#54
post #40

Earlier quoted context omitted.

How about the fact that your computer now has three enormous copies of chromium on it for no good reason?

My Visual Studio Code app is 138MB. On the grand scale of things, I'm not that worried about multiple copies of Chromium.

Electron by itself weighs in around 100mb. iTerm2 is a packed to the gills with features terminal that is 13mb.

Re: HyperTerm – JS/HTML/CSS Terminal

#55
post #35

Earlier quoted context omitted.

How about the fact that your computer now has three enormous copies of chromium on it for no good reason?

> no good reason. Well thats subjective. I might not be as cool as you but I get my work done using these tools.

I think he's saying you only need one version of Chromium on your machine to run all these tools.

Re: HyperTerm – JS/HTML/CSS Terminal

#58
post #43

This makes me want to re-implemented "commando" from AUX/MPW (I've never understood why this idea didn't take off). If you don't know, when you typed an ellipsis after a command in AUX or MPW a dialog box would be displayed showing the most popular toggles and options for the command (and allowing graphical file-picking). When you clicked "ok" it would type the command for you, so it made the command line both easier…

What did you lose enthusiasm for? commando or HyperTerm? I've been toying with the idea of a "teaching terminal" for learning the command line as well, and building off of HyperTerm seems like a good approach.

A teaching shell might be more important. Something like what Reason does for OCaml, but done for the the unix command line.

Use the model of something like is common with a lot of MUD clients, all text input occurs in a field at the bottom (look at tinyfugue).

Below that have a set of autocomplete hints. This would be filled in based off of common usage, and knowledge of binaries avialable in the path, knowledge of the command line arguments of common tools (git-prompt.sh is really nice for getting my new-to-git coworkers started, for instance).

This could be wrapped up in the terminal, but needs to be aware of the environment in which it's being executed which moves beyond the purview of most terminal emulators and into the area of the shell itself.

EDIT: Rough ascii art illustration:

  +----------------------------------------------------+
  | > cat foo.txt                                      |
  | Hello, world!                                      |
  |                                                    |
   ////////////////////////////////////////////////////
  |                                                    |
  +----------------------------------------------------+
  | > ca                                               |
  +----------------------------------------------------+
  |cat | cac... | cal...| can...  | can... | cap...    |
  +----------------------------------------------------+
`cat` first because of frequency of use (in general) and recent use. Others are showing other matches of the currently typed value + one letter, ... indicating more than one option.

You'd want usage statistics on common commands, and you'd need to assemble a database of command line options. Might be able to grab these from man/info pages, but formatting is likely inconsistent. Could at least get started that way. And you'd want to collect the users history to customize it. This'd be equivalent to the hints on many mobile OS keyboards.

I could see this being pulled into the terminal, rather than the shell itself. But it'd still need information about the underlying environment (easy if local, hard if remote).

How do terminal emulators on tablets handle keyboard input? Do any of them offer guided hints?

Re: HyperTerm – JS/HTML/CSS Terminal

#59
post #9

Earlier quoted context omitted.

I use two tools daily that are built on Electron and they are great. Not only that, but it's never obvious they run on Electron. I'm curious, what do you hate so much about it?

How about the fact that your computer now has three enormous copies of chromium on it for no good reason?

On my system, a long running Slack process uses about as much memory as a Finder window.
Post reply on HN