Live data from Hacker News

Fig now supports JetBrains IDEs

fig.io

11–20 of 71 posts

Re: Fig now supports JetBrains IDEs

#11
post #7

I don't understand why you need my e-mail during setup.

I mentioned this in another comment [0].

> Autocomplete is just our first product, and it's part of a suite of tools focused on improving developer experience in the terminal. The idea is that you can configure your developer environment in Fig and then we'll sync it across all of your devices.

[0] https://news.ycombinator.com/item?id=31113668

Re: Fig now supports JetBrains IDEs

#12

Is anyone else getting this warning? I am using macOS 12.3.1, iTerm2 3.4.15 and bash 3.2.57(1) bash: trap: __bp_install: invalid signal specification

Update your iTerm shell integration and the issue should be resolved!

Please run `fig issue` and I'll investigate.

Re: Fig now supports JetBrains IDEs

#13

Is anyone else getting this warning? I am using macOS 12.3.1, iTerm2 3.4.15 and bash 3.2.57(1) bash: trap: __bp_install: invalid signal specification

Update your iTerm shell integration and the issue should be resolved! Please run `fig issue` and I'll investigate.

Thanks that is working now!

Re: Fig now supports JetBrains IDEs

#15
post #2

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?

from what i know the end goal of Fig is to to build a proprietary platform for webapps that run as overlay on top of your terminal

this sounds ridiculous because it is

they can’t drop this shitty idea now, because they took tons of cash from venture capitalists to make it happen

Re: Fig now supports JetBrains IDEs

#16
post #2

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 :)

Re: Fig now supports JetBrains IDEs

#17
post #8

Fig 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…

`zsh-autocomplete` is a great tool as well! Some of this is just a matter of personal preference.

I've answered a few of your concerns in a different comment[0].

tl;dr

Autocomplete is just our first product, and it's part of a suite of tools focused on improving developer experience in the terminal. The idea is that you can configure your developer environment in Fig and then we'll sync it across all of your devices.

Fig will always be free for individuals. Teams pay for Fig for collaboration and discovery of internal scripts and for managing dev environment setup and onboarding.

A Linux/Windows version is coming soon. [1] [2]

[0] https://news.ycombinator.com/item?id=31113668.

[1] https://github.com/withfig/fig/issues/34

[2] https://github.com/withfig/fig/issues/35

Re: Fig now supports JetBrains IDEs

#18
post #15
post #2

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?

from what i know the end goal of Fig is to to build a proprietary platform for webapps that run as overlay on top of your terminal this sounds ridiculous because it is they can’t drop this shitty idea now, because they took tons of cash from venture capitalists to make it happen

Our mission is to improve the developer experience in the terminal.

We think that layer on new interfaces can help make the commandline even more powerful... as well as making it more accessible. Check out kui[0] to get an idea of what we're imagining.

[0] https://github.com/kubernetes-sigs/kui

Re: Fig now supports JetBrains IDEs

#19
post #8

Fig 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…

`zsh-autocomplete` is a great tool as well! Some of this is just a matter of personal preference. I've answered a few of your concerns in a different comment[0]. tl;dr Autocomplete is just our first product, and it's part of a suite of tools focused on improving developer experience in the terminal. The idea is that you can configure your developer environment in Fig and then we'll sync it across all of your devices.…

> The idea is that you can configure your developer environment in Fig and then we'll sync it across all of your devices

don’t make it look like you’re solving a complicated problem

i don’t have 10000 computers at home that i want to sync my configs to

neither do i change my zsh config every day

you do understand that this is a non-issue?

> Fig will always be free for individuals. Teams pay for Fig for collaboration and discovery of internal scripts and for managing dev environment setup and onboarding.

what? people pay for it? you must be kidding, right?

there’s one reason you’re being ridiculed here: you have no moat, no unique value proposition, but you can’t just take your ball and go home, because you have investors whom you promised that this shit is big and will make you guys rich

luckily HN-community understands that and won’t eat your worthless crap

Re: Fig now supports JetBrains IDEs

#20
post #14

Hacking IME and/or accessibility features to provide shell autocompletion is certainly ... creative solution.

One of our core principles is backwards compatibility. We want Fig to be a seamless addition to your existing tools and workflows!

It's taken some creativity on the engineering side, but has been super fun to see what we've been able to build when working with these constraints.

Post reply on HN