Live data from Hacker News

Launch HN: Fig (YC S20) – Autocomplete for the Terminal

fig.io

241–250 of 390 posts

Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal

#241

Earlier quoted context omitted.

Thanks so much! Yes - we would love to build our own terminal one day. I agree, a first party experience will make Fig much better. We think a good terminal needs to be fast, cross platform, customisable, and extendable (this is easier said than done). That said, one day we hope to build team-based tools too. Developers like to choose their tools - we would love to make Fig work, even if you weren't using a Fig termi…

This video was helpful to see. I do like the idea of being able to enter arguments in a form and get the full command, especially for complex scripts. An obvious extension would be pulling out argparse info e.g. from python scripts and letting the user enter arguments via a form

> An obvious extension would be pulling out argparse

Yes absolutely. A lot of possibility. We hope to create a whole new way of building terminal apps!

Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal

#242

Setup is very smooth. I'm impressed how well this integrates with my macOS. Also a bit suspicious, but unless/until there's real evidence, honestly I think it's just because of VS funding + how well the setup / integration went. Linux and especially smaller Unixes is where tools like this are really useful. My experience with Linux is that most stuff has to be installed on the command-line, or if there is a GUI it's…

Thanks! We currently work with the VSCode integrated terminal and will add support for Jetbrains IDEs, if possible!

Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal

#243
post #80

Nice website, but I wouldn't switch to this from Fish/Zsh on account of: 1. Cannot identify any killer features above what I already have with forever free tools with much larger support communities. 2. Less trust in you as a YC startup. What if you fail? What if you sell out? 3. Requirement of email. 4. Telemetry and privacy concerns raised by others. 5. Not available for Linux, and I get the feeling that Linux woul…

Can you suggest some tools which auto suggest like Fig and work with zsh? The built in auto complete in zsh works nicely, but how do I get the drop down of all options?

I really like Navi

Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal

#244
I think it's worth mentioning tldr as an effort towards more readable man pages: https://github.com/tldr-pages/tldr

Personally I like tealdeer for a tldr client b/c it's written in Rust and I think the name is fun, but the other tldr clients I've tried all seem fine as well: https://github.com/dbrgn/tealdeer

tldr doesn't do autocomplete, but between fish shell's autocomplete and tldr I feel I'm able to figure out most simple commands in the terminal.

Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal

#246
post #80

Nice website, but I wouldn't switch to this from Fish/Zsh on account of: 1. Cannot identify any killer features above what I already have with forever free tools with much larger support communities. 2. Less trust in you as a YC startup. What if you fail? What if you sell out? 3. Requirement of email. 4. Telemetry and privacy concerns raised by others. 5. Not available for Linux, and I get the feeling that Linux woul…

We started with macOS because I have a background in Swift development. Linux is definitely not an after thought to us! As for the telemetry concerns, I totally get that. We've tried to strike a balance and it seems like we've got it wrong. This will be fixed in the next update.

> I have a background in Swift development.

Then why on earth did you go out of the way to implement this in JavaScript instead?

Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal

#247
post #162

Earlier quoted context omitted.

> 2. Less trust in you as a YC startup. What if you fail? What if you sell out? > 3. Requirement of email. > 4. Telemetry and privacy concerns raised by others. Dovetailing on these... Like why is a CLI tool VC backed? Is the business model just selling our data? Is the VC backing for another product and the CLI tool is just a PR thing?

> Is the VC backing for another product and the CLI tool is just a PR thing? Autocomplete is our first product. The bigger vision that Fig can enable an ecosystem of terminal extensions. Here are some early prototypes we built [0] and here is the discussion from when we were posted on HN last summer [1]. > Is the business model just selling our data? We will never sell data. That just isn't the business we want to bu…

> We will never sell data. That just isn't the business we want to build

These are just words from strangers on the internet. You're offering a free and auto-updating app. You don't give me a contract guaranteeing anything. Most terms of use/privacy policies have a clause stating it can be updated without notice and when you do have actual policies on your site I'm sure they will be similar.

At any point you can decide that actually, you do want to share my data, or share access to it through one of your products. Maybe you won't call it "selling" (the same way Zuckerberg can tell Congress that Facebook doesn't sell anyone's data).

Maybe you don't decide to share my data, but Fig gets acquired and the new management decides to. Maybe an attacker gains access to the data and shares it. Maybe an attacker compromises an update, turning all Fig instances into keyloggers, and paired with the required email addresses uses it to compromise other data.

Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal

#249

Is Fig patenting this? How does the company prevent itself from being f.lux’d?

Autocomplete is just our first product. We've built an API that makes it possible to add visual extensions to any terminal.

We want to expand into stuff like runbooks, UIs for deployment, internal infra, etc..

Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal

#250
post #168
post #162

Earlier quoted context omitted.

> 2. Less trust in you as a YC startup. What if you fail? What if you sell out? > 3. Requirement of email. > 4. Telemetry and privacy concerns raised by others. Dovetailing on these... Like why is a CLI tool VC backed? Is the business model just selling our data? Is the VC backing for another product and the CLI tool is just a PR thing?

Just adding, from their website: > Investors: We've raised several million dollars from amazing VCs like General Catalyst and Kleiner Perkins, and angels like Jason Warner, Adam Gross, Olivier Pomel, Scott Belsky, Will Gaybrick and a handful of other impressive dev tool founders and executives. The fact that a CLI tool raised millions of dollars while also being basically powered by open-source contributions is also…

I mean, I agree, why is a cli tool YC backed, sure. But “several million dollars” is literally nothing in the VC space.
Post reply on HN