81–90 of 390 posts
That seems where most of the value is to me, like you can't just make a 10x car by attaching stickers to an existing one, eventually you are going to need to redesign the whole thing, the same is probably true for terminals too.
That means you contribute free ("open source") completions to them, but the scope and type of the completions is limited by their proprietary engine.
--- YC has pinned the founder comment and made it an impossible to reply to the top-level comment.
They say the most effective forms of advertising are the ones we don't realize are ads. Well, this is an ad.
Sign in with your work e-mail?
We ask people to sign in with their work email, so you can share private completions for scripts and internal CLI tools with teammates. (You can use your personal email, if you prefer!)
Disclaimer: I invested in Fig recently because I'm such a fan.[0]
Earlier quoted context omitted.
Glad you are liking it! VSCode terminal should be supported out of the box. Go to ◧ > Settings and make sure the VSCode Integration is ticked. (You may also have to restart VSCode.) re Fig's icon: haha yes we could definitely do with a new icon. Our previous icon was an emoji pear (yes a pear, not a Fig) so at least our current one is a step up from that! We take the feedback on board and will investigate some new lo…
Ah, you're right! I am on the "VSCode Exploration" build still from being an early M1 adopter. I guess that version doesn't work -- no idea. I swapped my builds and it's working perfectly, thank you and good luck to you and the team.
If it's different, want to create an issue for us and we'll get to it this week? https://github.com/withfig/fig
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…
Earlier quoted context omitted.
Thanks! We do need to put in place a proper privacy policy. But we wanted to be transparent with how Fig uses your data (hence what we have currently). You can run `fig settings app.disableTelemetry true` to disable all telemetry except for one daily ping. You also make a good point: in our onboarding we should move our privacy information to before granting accessibility! We will make this more clear
Telemetry being on by default on something like this is going to be hard to pull off. Homebrew has telemetry but it's only for Homebrew commands. This would potentially be for every single command one type in a terminal. It just takes one little bug in the app and who knows what can be sent, maybe passwords and so on.
It was also more than a little controversial.
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…
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.
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…