5 ms·
I'm skeptical of the value of electron-ified applications when fully native alternatives suffice. However, ignoring that, there are a few (pretty severe) proble
by woodruffw 10y ago
I'm skeptical of the value of electron-ified applications when fully native alternatives suffice. However, ignoring that, there are a few (pretty severe) problems with this release:
* The .deb package seems to install everything in /opt. This seems to be pretty common practice for electron apps and isn't a huge deal, except for the fact that a wrapper executable/link isn't installed anywhere else on the system. As a result, I had to go looking for the install directory and invoke hyper as a fully-qualified path (i.e., /opt/Hyper/hyper).
* Hyper tries to run `npm prune && npm install --production` on every startup, which (naturally) fails when the user doesn't have node (much less npm) installed globally.
* Most control modifiers don't work on Linux at all, making it impossible to work inside of programs like nano, alpine, etc.
* Throughput seems to be an issue. Running `cat /dev/zero` locked the entire application up.
These problems are understandable considering the (often unappreciated) complexity of terminals, but they're also surprising in a 1.0.0 release.
- paulddraper 10y ago> The .deb package seems to install everything in /opt Hm, just like another commonly installed package... $ ls /opt/google/ chrome chrome-beta chrome-unstable Though it installs executables $ ls -l /usr/bin/google-* /usr/bin/google-chrome -> /etc/alternatives/google-chrome /usr/bin/google-chrome-beta -> /opt/google/chrome-beta/google-chrome-beta /usr/bin/google-chrome-stable -> /opt/google/chrome/google-chrome /usr/bin/google-chrome-unstable -> /opt/google/chrome/google-chrome-unstable
- nilved 10y agoWhich is exactly what GP mentioned. Although using `/opt` to begin with is an anti-pattern in all cases including Chrome.
- paulddraper 10y agoWhich is exactly what I mentioned. Are we looking for a disagreement?
- nilved 10y agoMaybe, sorry if I misread your comments!
- calpaterson 10y agoSeems reasonable to me if it's a third party package that doesn't want to clobber whatever the distro installs. Where else? /srv?
- woodruffw 10y ago/usr/local, traditionally. Since it only exposes one executable anyways, I'd say the chance of clobbering is fairly small (and reversible, since it's a deb).
- mst 10y agoAugh! No no no no no no. Sorry, this is a pet peeve of mine. /usr/local belongs to the sysadmin (I grit my teeth at FreeBSD's interpretation of this, much though I love the OS otherwise, and prefer NetBSD's addition of a /usr/pkg hierarchy to avoid jamming packages in /usr instead, which is only a bit less aggravating). /opt exists basically for vendors to have somewhere to put things that they know won't trample on my /usr/local hierarchy. (I still think they should've installed something in $PATH, mind, but /opt is not at all the wrong answer to my mind.)
- deleted 10y ago[deleted]
- IshKebab 10y ago> I'm skeptical of the value of electron-ified applications when fully native alternatives suffice. Me too, although in the case of terminal apps, they really haven't moved on since the 70s. How many support images? Completion popups? Browsable history? Current directory widget? Collapsible output? Honestly if it takes some insane over-engineering to get some actual innovation in terminal apps I'm all for it! And when I say "innovation" I mean "obvious features that should have been there decades ago".
- Klathmon 10y agoI really don't think it's all that much "over engineering". I mean, if you want images, history, tabs, to support every language under the sun, and support for most platforms, I'd say a browser is a fantastic way to get most of that "for free".
- woodruffw 10y agoUnfortunately, "support for most platforms" tends to result in the kind of user experience that I described above. There's something comedic about millions of lines of compiled Chromium failing to handle the Control modifier on Linux. I can't really blame them (Linux, like every nix, does something unique at the tty level that breaks reasonable assumptions), and I'm sure it'll get a lot worse once they try to run their JS bindings over the pty/tty subsystem of something like Solaris.
- Volt 10y agoI'd say a browser introduces a non-negligable cost.
- drvdevd 10y agoAgreed, though this is a situation that should be improved if the industry wants everyone using browsers for everything.
- woodruffw 10y agoI agree, and I'm sure that the stagnancy of the plain old terminal is behind this and other modern takes on terminal emulation. I personally prefer that the terminal delegate just about everything besides I/O to plugins or extensions, so Hyper is probably out of the picture for me. That being said, my current terminal of choice (urxvt) doesn't do much on that front either. I hope that other terminal emulator projects pay attention to the development here and adopt the best innovations.
- baldfat 10y agoI am using the appimage and I don't have these issues. Ranger.py runs very smooth and vim is fine. I am kind of shocked that there was no delay and I am on a 8 year old dell.
- kolme 10y ago> Hyper tries to run `npm prune && npm install --production` on every startup. Wait, what, really? Wouldn't that leave you without dependencies if you don't have internet connection at the time? Seems a very dangerous thing to do for many, many reasons.
- madeofpalk 10y agoDepends whether you already have the dependencies or not I guess - I'm not sure if it ships with a node_modules or not. FWIW `npm prune` only removes modules from node_modules that aren't specified in package.json. It won't actually remove and declared dependencies.