Live data from Hacker News

Warp: Fast, Rust-based terminal (waiting list)

warp.dev

141–150 of 181 posts

Re: Warp: Fast, Rust-based terminal (waiting list)

#141
post #50

Earlier quoted context omitted.

Just tried it: 2021-07-14T17:05:56.423Z WARN window::os::windows::window > EGL init failed with_egl_lib failed: with_egl_lib(libEGL.dll) failed: no compatible EGL configuration was found, atioglxx.dll: LoadLibraryExW failed, fall back to WGL 2021-07-14T17:05:56.500Z ERROR wezterm_gui::frontend > Failed to create window: The OpenGL implementation is too old to work with glium I feel sad when terminals need OpenGL ...…

On the flip side, if you do have OpenGL, why not utilise it for unparalleled terminal performance? I've used Kitty for years for that reason, it's incredibly responsive and smooth, a pleasure to use.

What does a responsive terminal look like compared to something else? What are you doing with your terminal that demands responsiveness?

Genuinely curious. I've never ran into a situation where the standard terminals felt "sluggish"... barring a slow internet connection sshing.

Re: Warp: Fast, Rust-based terminal (waiting list)

#142
Co-founder of Fig (https://fig.io) here.

I'm pleased that there is more innovation in the terminal emulator space. For a tool used by just about every developer, not a ton has changed since the launch of the VT100 [1] in the 70s.

Fig adds autocomplete [2] to your existing terminal. Soon, we're launching the ability for you to build your own visual apps and shortcuts (like these: https://fig.io/videos/old-sizzle-reel.mp4) and share them with your team or the community.

Rather than building our own terminal, we integrate with the terminals you already use (even the one embedded in your IDE). This means everyone on a team can collaborate but keep using their existing terminal and shell setup.

We are excited to integrate Fig with Warp.

[1] https://en.wikipedia.org/wiki/VT100

[2] https://github.com/withfig/autocomplete

Re: Warp: Fast, Rust-based terminal (waiting list)

#143
post #134
post #131

Earlier quoted context omitted.

If this was a better, generic, screen sharing solution, it might be awesome. But forcing people to use a specific terminal to work with others feels like it'll be a non-starter for most people. Not least given how rarely I've ever had a need to show anyone my terminal (despite having had solutions for it for literally decades via e.g. sharing screen or screen sharing all the way back to VNC and similar).

Our strategy here is to share sessions to the web, so collaborators don't need to download the app. It's fascinating how far utilities like screen will get you in functionality, but I agree it's really hard to get people on there.

My point in mentioning screen was rather that despite having had solutions that work for decades, that everyone I collaborate with knows how to use, I can literally count the number of times I've felt a need to share just a terminal window with someone, rather than e.g. a full screen, on two hands over the course of 25 years.

It's rare enough for me to have a need for sharing a screen, but sharing a single type of window would cover just a tiny proportion of those rare cases.

My tech stack is atypical enough in many respects that maybe others will find it more useful, but to me this seems like a couple of useful but easily copied features (the auto-complete), and some stuff I'd never use.

Re: Warp: Fast, Rust-based terminal (waiting list)

#144

Some of the features make it sound dubious. "Real-time collaboration". Why would you bake that in your terminal?

Why wouldn't real-time collaboration be useful?

What are you doing in a terminal that you need real-time collaboration? Here's what I do in my terminal:

* log in to AWS * push commits (though that's mostly in Emacs now) * tail logs from remote services * use ssh * random grepping/cat/awk/sed one-off stuff

I don't see any of those benefiting from real-time collaboration. The use-cases presented on the landing page don't make sense to me either - when my entire team is debugging production, we usually fan out and all look at different things rather than needing to fan-in and all do/look at the same thing. And if I want to chat I'll have Slack open next to the terminal.

Re: Warp: Fast, Rust-based terminal (waiting list)

#145

The text editing features (multiline, multiple cursors) are something I've really wanted from a terminal for a long time. Editing long/complicated commands in most terminals is not a great experience, so the point that I normally copy and paste from my text editor. A little wary of this if it's not open source, but looking forward to being to try it out.

man bash, and search for, 'edit-and-execute-command', to launch a configurable editor for long commands.

zsh has a similar facility.

Re: Warp: Fast, Rust-based terminal (waiting list)

#146
What's the business model?

How will that impact the quality of the product in comparison to, say, iTerm2?

I see the team [1] has some strong credentials, which honestly looks overpowered for "just" a terminal app. Unfortunately, that makes me suspicious of their goals for "just" a terminal app, which has a relatively well-established expected feature-set.

[1] https://www.warp.dev/about-us

Re: Warp: Fast, Rust-based terminal (waiting list)

#147
post #27

Who cares that it's Rust if it's closed source? Also: "All cloud features are opt-in. Data is encrypted at rest." The fact that this even needs to be stated makes it a hard no, especially for a terminal emulator.

> Who cares that it's Rust if it's closed source? People who care about security.

>People who care about security.

Those people tend to care more for their term being opensource than it being in Rust. Dont trust those who claim otherwise.

Re: Warp: Fast, Rust-based terminal (waiting list)

#148

Earlier quoted context omitted.

Why wouldn't real-time collaboration be useful?

What? You'll suddenly need 5 people to chat about that multiline command you're about to type?

What if you open an editor inside this terminal and collaborate in there?

Re: Warp: Fast, Rust-based terminal (waiting list)

#149
post #144

Earlier quoted context omitted.

Why wouldn't real-time collaboration be useful?

What are you doing in a terminal that you need real-time collaboration? Here's what I do in my terminal: * log in to AWS * push commits (though that's mostly in Emacs now) * tail logs from remote services * use ssh * random grepping/cat/awk/sed one-off stuff I don't see any of those benefiting from real-time collaboration. The use-cases presented on the landing page don't make sense to me either - when my entire team…

How’d you learn how to do all those things?

This is where the real-time collaboration comes in. Easy to teach novices how to use powerful shell commands to make things easy.

Post reply on HN