I don't understand what Fig is actually for. Why would I want a "visual autocomplete" when I already get what I want out of bash-complete + fzf, a more technically complete and understood solution?
Do you get rounded corners and soft shadows with bash-complete :)
Fig now supports JetBrains IDEs
31–40 of 71 posts
Re: Fig now supports JetBrains IDEs
#32Fig is macOS-only, proprietary, requires e-mail and has telemetry Fig relies on free labour to add completions and does not support open-source completion formats Fig is VC-funded and at some point will have to generate revenue for it’s investors - at your cost don’t use Fig! if you have zsh you can use zsh-autocomplete, which is no worse than Fig https://github.com/marlonrichert/zsh-autocomplete edit: this comment w…
Re: Fig now supports JetBrains IDEs
#33Hey HN! Didn't expect to see Fig here this morning. We just released a new version of Fig that allows users to install a custom input method on macOS. This means we now work with over a dozen new terminals, including all JetBrain IDEs, Alacritty, Kitty, WezTerm and more. The engineering behind it was surprisingly tricky since these APIs are not as well documented as you'd hope. (Indeed, the best place to look is the…
> The idea is that you can configure your developer environment in Fig and then we'll sync it across all of your devices. What's Fig's target audience? Developers. Developers have been using a tried and tested way to keep configurations for decades -- dotfiles. We sync them across all our devices using git (or any of a thousand other ways). This is a solved problem and doesn't require email addresses or logins.
We are building our own version of this, that is more tailored to the use case than a generic git repo interface. :)
Re: Fig now supports JetBrains IDEs
#34Hey HN! Didn't expect to see Fig here this morning. We just released a new version of Fig that allows users to install a custom input method on macOS. This means we now work with over a dozen new terminals, including all JetBrain IDEs, Alacritty, Kitty, WezTerm and more. The engineering behind it was surprisingly tricky since these APIs are not as well documented as you'd hope. (Indeed, the best place to look is the…
> The idea is that you can configure your developer environment in Fig and then we'll sync it across all of your devices. What's Fig's target audience? Developers. Developers have been using a tried and tested way to keep configurations for decades -- dotfiles. We sync them across all our devices using git (or any of a thousand other ways). This is a solved problem and doesn't require email addresses or logins.
Which kinda sucks
Re: Fig now supports JetBrains IDEs
#35Earlier quoted context omitted.
> The idea is that you can configure your developer environment in Fig and then we'll sync it across all of your devices. What's Fig's target audience? Developers. Developers have been using a tried and tested way to keep configurations for decades -- dotfiles. We sync them across all our devices using git (or any of a thousand other ways). This is a solved problem and doesn't require email addresses or logins.
> Developers have been using a tried and tested way to keep configurations for decades -- dotfiles Which kinda sucks
Re: Fig now supports JetBrains IDEs
#36Earlier quoted context omitted.
> The idea is that you can configure your developer environment in Fig and then we'll sync it across all of your devices. What's Fig's target audience? Developers. Developers have been using a tried and tested way to keep configurations for decades -- dotfiles. We sync them across all our devices using git (or any of a thousand other ways). This is a solved problem and doesn't require email addresses or logins.
Currently, lots of developers use GitHub (which naturally requires a login) to sync their dotfiles across devices. We are building our own version of this, that is more tailored to the use case than a generic git repo interface. :)
you’re building a proprietary solution for something that isn’t a problem at all
Re: Fig now supports JetBrains IDEs
#37Earlier quoted context omitted.
It seems like Fig might not be solving a problem you have and that's totally okay. We believe that there is a lot of room to improve developer experience in the terminal. That's why we build the products that we build.
to be honest, i don’t know anyone who has a problem moving files from one computer to another there are even open-source tools like Syncthing that do this https://syncthing.net/ i guess i’m very thankful we don’t need Fig for this!
Re: Fig now supports JetBrains IDEs
#38Hey HN! Didn't expect to see Fig here this morning. We just released a new version of Fig that allows users to install a custom input method on macOS. This means we now work with over a dozen new terminals, including all JetBrain IDEs, Alacritty, Kitty, WezTerm and more. The engineering behind it was surprisingly tricky since these APIs are not as well documented as you'd hope. (Indeed, the best place to look is the…
Yeah yeah right and you just appeared out of nowhere with a 300-word explainer. "Just in case". Stop this shit-show already, everybody knows you're a YC-baked company
YC-baked companies get tips and notifications when they're about to get featured
people are critiquing you below and you're asking HN mods to downrank negative comments to keep up your PR-game
my harsh, but valid criticism of your product ended up at the bottom of page, although it has 20 points and should actually be higher than yours and any other comment, but life's easy when you can cheat a bit!
see yourself: https://imgur.com/a/Z5AZkik
how can a comment with 20+ points be the last one on the page?
Re: Fig now supports JetBrains IDEs
#39But I've dumped most of it in the last month for Fig. I like seeing command specific options, relevant to the current context, and in a long list which I can scan and scroll quickly.
I go to documentation MUCH less now and I'm faster with it. And that's most of what I care about.
Commence retaliations...
Re: Fig now supports JetBrains IDEs
#40Hey HN! Didn't expect to see Fig here this morning. We just released a new version of Fig that allows users to install a custom input method on macOS. This means we now work with over a dozen new terminals, including all JetBrain IDEs, Alacritty, Kitty, WezTerm and more. The engineering behind it was surprisingly tricky since these APIs are not as well documented as you'd hope. (Indeed, the best place to look is the…
> Didn't expect to see Fig here this morning. Yeah yeah right and you just appeared out of nowhere with a 300-word explainer. "Just in case". Stop this shit-show already, everybody knows you're a YC-baked company YC-baked companies get tips and notifications when they're about to get featured people are critiquing you below and you're asking HN mods to downrank negative comments to keep up your PR-game my harsh, but…
We don't.