Windows support is really appreciated! I just switched from a MacBook to a Surface Book, and the biggest pain point has been finding a good terminal to replace iTerm2. I'll definitely try this when I get home!
Hyper 1.0.0
41–50 of 214 posts
Re: Hyper 1.0.0
#42I'm incredibly confused about why I should switch from iTerm. If you've been using Hyper, can you tell me why you switched and what was better?
- looks nicer - easier to customize (at least for me) - runs super smooth (not that iTerm was slow or anything) - I'd have to confirm, but a lot syntax highlighting and things that I just want to "work" out of the box seemed more applicable to Hyper than iTerm - extensions (not sure if iTerms extension community could rival npm)
Re: Hyper 1.0.0
#43This Terminal Emulator: brew cask install hyper
Docker Hosting: brew install hyper
Re: Hyper 1.0.0
#44Posted link has virtually no description of what the project is.
Going to the root of the github repo has release notes and with the most detailed description as "HTML/CSS/JS Terminal" but burned into a PNG file.
Best description of the product is on "hyper.is" in an animated GIF form.
People working on project like this need to understand that without a reasonable textual description of their product, outlining basic features and benefits over other existing systems, that the uptake is going to be very, very low.
Re: Hyper 1.0.0
#45Earlier quoted context omitted.
It makes sense because JavaScript has, through several bizarre turns of events, become the language du jour , which means all sort of clueless people are falling over themselves to abuse it in increasingly convoluted ways, so that the clueless people in corporate HR who've been told "We need someone who is a JavaScript rockstar!" can be wowed by the description of some nightmarish contraption that "really takes insan…
You know what's tiring? People getting out of their way to gratuitously criticize the collective effort of a coordinated group of passionate people who just want to have fun reinventing the wheel.
Re: Hyper 1.0.0
#46Earlier quoted context omitted.
Try `ps -afx` in Hyper. Then in iTerm 2. Though I love the ideas behind Hyper, I'm going to stick with iTerm 2 as my daily terminal for now.
Also try `yes` in Hyper, see what happens.
Re: Hyper 1.0.0
#47(I literally have not tried a single other thing. I made a typo on the very first command I wanted to try. I tried ctrl+c to start over, and it did not recognize it.)
EDIT
I gave it another chance. If I start a bash shell, it recognizes ctrl+c, but it does not recognize the up arrow key. Not impressed. Don't get the hype. Sorry.
EDIT2
Is this being brigaded? It's the first result on HN without clear reason, and I'm being downvoted immediately for posting this feedback. What's going on?
https://github.com/zeit/hyper/issues/1127
https://github.com/zeit/hyper/issues/1126
https://github.com/zeit/hyper/issues/1121
https://github.com/zeit/hyper/issues/1129
EDIT3
OK, seriously, what's with the downvote brigade? I'm at -3 now.
Re: Hyper 1.0.0
#48Erm... What is it? I've clicked through several pages and still don't know, aside from the fact that apparently it extends the command line in some way. But I might just be missing something.
Re: Hyper 1.0.0
#49Earlier quoted context omitted.
Typesafe HTTP implementation? Meh. I go back and forth on stringly typed vs strong typing. Just this weekend I wrote an app in Objective-C instead of Swift, and it's already close enough to 1.0 that I can start using it myself. I originally tried to do it in Swift but the IDE support is just way too lacking and buggy (still!) compared to ObjC. Point being, string-typing and dynamic typing aren't really all that terri…
> But I've given up at aiming at perfectionism in programming. Optional typing is the sweet spot.
```
const whatIsFoo = match (foo) {
case : nil : "nothing, really"
case : string : "it's a string"
case : number | boolean : "it's bool or number"
case [ head, ...tail ] : string[] : `it's array of strings with head ${head} and tail ${tail.join(', ')}`
case { value } : { type: 'NodeFoo' } : `it's Node Foo with value ${value}`
default: "well, something else."
}```