171–180 of 757 posts
This is certainly interesting, but I am struggling to sign up. I clicked "Sign up with GitHub", it took me to the website where I authorized it. It was seemingly working until I saw this: "Oops! We were unable to log you in."
Earlier quoted context omitted.
What would be the advantage over version controlled shell scripts?
(Not affiliated with Warp but care about this particular thing) Shell scripts implies, well, a particular shell. If everyone is on similar OSes, maybe that works for you, but as a Windows user, "pile of bash scripts" might as well be "doesn't work for you." I use a terminal for my daily work, but don't have bash installed on my machine. That said, I haven't tried Warp yet specifically because it's Mac-only right now.…
For mac linux, posix-compliant scripts mostly work in my experience but you have to account for different versions of gnu utils. For linux windows, if it's small you could just write a powershell script, or use something like python on both, no?
I fail to see how these features are nice enough to force people to use a proprietary terminal that, for now, is compatible with existing bash/zsh shells.
Earlier quoted context omitted.
I just ran a quick test using Casey Muratori's termbench ( https://github.com/cmuratori/termbench ) you are an order of magnitude slower than Alacritty, and also significantly slower than iTerm. Warp also locks up pretty severely and only shows a new frame once every few seconds during most of the run. Alacritty CPU: Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz VT support: no ManyLine: 1.5670s (0.0399gb/s) LongLine: 1.12…
Yeah, this is a known issue, unfortunately--but it's definitely something we want to fix as we improve Warp. See more information here where we chat with Casey about it: https://twitter.com/zachlloydtweets/status/14175482714432348...
> evidence that it’s not
> Yeah, this is a known issue
I don’t want to be critical, but which is it? If you know you are not anywhere near the performance, why say you are?
A company receiving receiving $23 million usd to build a terminal is about the dumbest thing I've seen this month. I would've figured it to be a April Fools joke if posted a few days earlier. Why is a company building a terminal? How are they going to earn money at all when there are other fast, performant terminals that are open source, community run, and don't have interests at-odds with user freedom and privacy? I…
> Warp is a fully native, GPU-accelerated, Rust-based terminal. No Electron or web-tech. I understand that this probably appeals to most readers there, but I don't like the negativity. I like Rust and Web tech, sometimes together, and I don't want my tools to shit on what I like. We can also discuss the full nativeness. To me, the menus don't even try to look native. Is it native because it doesn't use a virtual mach…
Hi, Warp engineer here! Nothing against electron. We write this in the headline because people who see features like blocks or input editor automatically think "slow". So it's a succinct way to communicate that we have a snappy app. For benchmarks, we have some preliminary info in this tech blog https://www.warp.dev/blog/how-warp-works .
A company receiving receiving $23 million usd to build a terminal is about the dumbest thing I've seen this month. I would've figured it to be a April Fools joke if posted a few days earlier. Why is a company building a terminal? How are they going to earn money at all when there are other fast, performant terminals that are open source, community run, and don't have interests at-odds with user freedom and privacy? I…
they’ll have a business offering which lets people collaborate
Congrats on your launch, though it seems you are getting slammed here and it may not be the reception you anticipated. I'm genuinely curious if you talked to your target demographic prior to this or only postulated that this would be a viable product with the proposed revenue model? The HN crowd is brutally candid and honest. Hopefully the criticism you are currently receiving can be structured into a revision of the…
Earlier quoted context omitted.
Yeah it might seem like a crazy amount. Building a terminal is hard. We have to build feature parity, maintain a stable terminal-shell interface, on top of modernizing the product experience. The money allows us to hire engineers to work on this project full-time and create a great product experience.
I don’t doubt any of that. The amount seems crazy not because of the potential costs, or ability to invest in the product, but rather due to TAM. But nobody would lead a round of that size without a decent monetization strategy. I suspect enterprise focus around security / IAM integrations (hence all the telemetry).
Actually the telemetry has nothing to do with our monetization.
Enterprise is right. We are monetizing through team and enterprise features. We are planning to build among others:
- Sharing hard-to-remember workflows within your team
- Wikis and READMEs that run directly in the terminal
- Session sharing for joint debugging