Show HN: Warp, a Rust-based terminal
651–660 of 757 posts
Re: Show HN: Warp, a Rust-based terminal
#652At https://github.com/warpdotdev/Warp How did you achieve to have the folders /keysets and /themes to be linked to the other git repos https://github.com/warpdotdev/keysets and https://github.com/warpdotdev/themes I wanted to do this for a long time but all tutorials pointed to all alternatives one more difficult than the other.
Re: Show HN: Warp, a Rust-based terminal
#653I see a lot of cool tech here all around. It's inspiring! Thanks! At https://github.com/warpdotdev/Warp How did you achieve to have the folders /keysets and /themes to be linked to the other git repos https://github.com/warpdotdev/keysets and https://github.com/warpdotdev/themes I wanted to do this for a long time but all tutorials pointed to all alternatives one more difficult than the other.
Re: Show HN: Warp, a Rust-based terminal
#654Earlier quoted context omitted.
You may be conflating programs running in a terminal and the terminal itself. We've managed to get this far without the latter.
I am not conflating the two. If the terminal can run programs connected to the internet, then the terminal has internet connectivity. The host system would not be able to tell the difference. Warp could certainly promise not to include any phone-home functionality in their code, but unless it's open-source and everything is audited, it could easily call the host system's HTTP client and still phone home.
Is this true? This sounds wrong to me but I don't know the inner workings of terminals. The terminal just executes programs and handles pipes it seems. A terminal can be completely walled from the internet, and when you execute something from it, say, curl, then curl has it's own memory space and access layer outside the terminal, and just has it's stdio wired to the terminal.
Re: Show HN: Warp, a Rust-based terminal
#655Earlier quoted context omitted.
So programs/workflows written in Warp will be portable without much effort, in some way that an equivalent shell or python script isn't? Why do you think that?
It seems like you’re grouping a bunch of things together and saying I have opinions about them that I don’t. Let’s break them out: workflows I would assume to be portable, yes. It is an assumption. I generally expect program configuration to be mostly cross platform by default. I’m not sure what a program written for a particular terminal would be, so I’m not sure if I’d assume portability or not. Shells are not ubiq…
> You aren't the one porting Warp, but you are the one porting the shell script.
It sounds like your are saying somthing like "Warp scripts/workflows require almost no effort to port, compared to the shell scripts they replace". I was interested to learn how this can be the case. Perhaps my interpretation was wrong.
Re: Show HN: Warp, a Rust-based terminal
#656Re: Show HN: Warp, a Rust-based terminal
#657Re: Show HN: Warp, a Rust-based terminal
#658[1] https://twitter.com/anshublog/status/1511553856487845892?s=2...
Re: Show HN: Warp, a Rust-based terminal
#659Earlier quoted context omitted.
Agree, this is a pretty bad deal breaker for me. Big business people doing short-sighted big business things, salivating at cramming a product full of telemetry. All without transparency around it? In a terminal of all things?? Indescribably off-putting and catastrophically damages my trust in the product and the CEO. EDIT: To be fair there is some transparency in the original post. I was looking through the landing…
or they actually listen to our feedback, remove forced telemetry, remove sign-in in the next release, then i'd be more happy to give their product another chance although no guarantee they'll not turn evil at some point in the future...
Then why would anybody bother to invest in their next series?
Re: Show HN: Warp, a Rust-based terminal
#660- Downloaded it - Saw the github login - Uninstalled it