Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

fig.io

Post reply on HN
Print view View original

361–370 of 390 posts

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

#361

Post by yoz-y »

lasfter wrote: post #287

I detest that it has become normalized to grant tech companies access to personal data with only limp promises that it won't be misused. If you give Fig permissions to look at what you are typing into the terminal, you should be prepared for them to look at what you are typing into the terminal and use it how it best serves them . They're asking for more permissions than that of course. Imagine giving FedEx a copy of…

Wait. Does this mean that you are against the use of any tech product made by a company? From the description and the author comment it looks like they are not transmitting the keystrokes to their server (and it does not seem to have any need for it anyways). How is this different from using say, a compiler made by a company (they have access to all your code), or an image editor (they have access to all your photos).

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

#362

Post by heyoni »

tharkun__ wrote: post #327
Spivak wrote: post #316

Earlier quoted context omitted.

I mean they’re trying to be JetBrains but for Bash so it makes total sense to me why it would be a many many millions of dollars effort. I think people forget that IDEs (which is essentially what this is) are a stupid amount of work. Then you have to add the rest of the business: sales, leadership, support, hr, ops. I mean a 25 person company $200k average total comp is 5mil annual burned cash just on salary.

This is shell completion that you can already do by hitting tab twice (if a definition file exists for your tool). If not, write a definition file.

This is Kite all over again.

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

#363

Post by heyoni »

dheera wrote: post #238
sidlls wrote: post #202

Earlier quoted context omitted.

The correct balance is 0% of terminal activity is sent with telemetry, unless the user explicitly and specifically authorizes it.

Just add "0.0.0.0 fig.io" (or whatever it is, wireshark it to find out) to your /etc/hosts

Doesn’t it auto update? That’s a cat and mouse game I wouldn’t want to play.

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

#364

Post by ainiriand »

tyrex2017 wrote: post #345
lasfter wrote: post #287

I detest that it has become normalized to grant tech companies access to personal data with only limp promises that it won't be misused. If you give Fig permissions to look at what you are typing into the terminal, you should be prepared for them to look at what you are typing into the terminal and use it how it best serves them . They're asking for more permissions than that of course. Imagine giving FedEx a copy of…

Theoretically you are right. I wouldnt give Fig access. But the world moved on without us. Lets be honest: For 99.9% of users, no misuse ever happens which they care about.

I disagree in part, because this tool is not meant for the common user.

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

#367

Post by chrisjarvis »

djrogers wrote: post #105

This looks nice, but requiring an email during setup, with no explanation or discernible reason - and demanding a work email at that - seems very creepy. This decision alone removes my trust in your product and your company, sorry.

Ya I closed the app and removed the Accessibility permission at this step. I don't need this app to "connect with my coworkers"

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

#369

Post by cholojuanito »

12ian34 wrote: 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…

>5. Not available for Linux, and I get the feeling that Linux would forever be an afterthought since you released for Mac first (presumably, this was driven by financial reasons).

I am amazed that a CLI tool isn't made for Linux

Post reply on HN