3 ms·
But yours is not a criticism that Philip can really use. He's clearly decided on an approach: adding capability to a terminal. It's as if someone posted a Ruby
by javajosh 13y ago
But yours is not a criticism that Philip can really use. He's clearly decided on an approach: adding capability to a terminal. It's as if someone posted a Ruby framework and you criticized them for the fact that they should be using Python, because it's just better for web stuff. Or someone posts a Vim plugin and you criticize them for not using Emacs, etc. Or someone writing an IDE plugin and you say they should run it from the command line anyway. Etc.
It seems unlikely that the author of finalterm, Philip, didn't consider doing this as a shell addition. But, if he pops in here and says, "Gosh, I never thought of that! You're right I should scrap this project and do it in the shell!" then I will humbly apologize. But, I don't think that's going to happen.
- jlgreco 13y agoI don't know what Philip did or did not think of. I think you are misunderstanding the nature of my complaint however. This isn't an issue of somebody using a tool that I don't prefer.. use Vim, or use Emacs, or use Nano for all I care. You want to use gnome-terminal? I can't stand it, but be my guest. This is me saying that Philip has a good idea but has implemented it in a way that does not play nicely with existing tools. He knows this obviously, since he (or maybe other Finalterm authors, I haven't really been paying attention to that) have pointed that out himself. What I am pointing out that this incompatibility is unnecessary and unfortunate. The crux of my complaint is that he has ideas that I would like to use, but solely because he has implemented them in an unorthodox way, there is simply no way that I can incorporate this into my workflow. I'm not going to not say this simply because he may have also thought of this and disagrees with me. HN should not be an echo chamber of praise.