Live data from Hacker News

HyperTerm – JS/HTML/CSS Terminal

hyperterm.org

41–50 of 267 posts

Re: HyperTerm – JS/HTML/CSS Terminal

#41

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.

How many lines is the JDK? or .NET, or libcpp?

LLVM: 1.5 million (I assume libc++ is less than 500k)

OpenJDK: 6.8 million

.NET: 10.5 million

Source: https://www.openhub.net/

Re: HyperTerm – JS/HTML/CSS Terminal

#42

Earlier quoted context omitted.

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

If you have the RAM for it and the software works well, who cares? Plus, it seems potential improvements are coming in this area. https://github.com/electron/electron/issues/673

On the one hand side people complain that Turbo Pascal and WordPerfect (or even UNIX for that matter) worked extremely fast on an 386SX with 4MB RAM and that modern software eats hundreds of megabytes of memory and seems slower, without providing much new functionality.

This attitude (replacing a lean and fast terminal, by one rendered using a web browser engine) is exactly why modern machines that are 1000x faster and with 1000x the memory still seem to be slow for basic tasks.

Of course, it's a free choice. You can waste resources by replacing small programs by browsers ;). But it's reasonable that many people find it a waste.

Re: HyperTerm – JS/HTML/CSS Terminal

#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.

Re: HyperTerm – JS/HTML/CSS Terminal

#46

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.

https://www.openhub.net/p/putty

Perhaps not as feature comlpete, and not my daily use terminal emulator, but it's only 110k lines of code. And it's not just a terminal emulator, that's just one thing it does in that 110k lines of code.

EDIT: I was going to look up others but I'm distracted by other obligations. My point being: Terminal Emulators aren't actually that complex.

Re: HyperTerm – JS/HTML/CSS Terminal

#48
post #29

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 agree, but I'd take it a step further - the 15+ million Lo(memory-unsafe!)C for the unix kernel other (all?) trivial apps sits on is also not a good thing.

I agree with your larger point (I think) but for what it's worth: Most of those 15+ million lines are drivers you don't use.

Re: HyperTerm – JS/HTML/CSS Terminal

#49
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?

One?

Re: HyperTerm – JS/HTML/CSS Terminal

#50
post #16

Earlier quoted context omitted.

I believe it has to do with the amount of performance lost in the overhead with the electron stack versus a native implementation. Please correct me if I'm wrong.

For the majority of applications, I'd imagine there's a negligible performance difference. Besides, any app built on Electron will run infinitely faster than one which wasn't built at all since the developer didn't want to learn another language. I'm not saying Electron is suitable for everything, but I think it has its place.

I still question Electron for "commercial quality" apps. The Electron runtime by itself is about 100mb. I've built an internal Electron app for work and for that it's absolutely fantastic.
Post reply on HN