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

Fig now supports JetBrains IDEs

fig.io

Post reply on HN
Print view View original

21–30 of 71 posts

Re: Fig now supports JetBrains IDEs

#21

Post by shric »

mschrage wrote: post #4

Hey 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.

Re: Fig now supports JetBrains IDEs

#22

Post by mschrage »

ushakov wrote: post #19
mschrage wrote: post #17

Earlier quoted context omitted.

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

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.

Re: Fig now supports JetBrains IDEs

#23

Post by ASalazarMX »

ushakov wrote: post #19
mschrage wrote: post #17

Earlier quoted context omitted.

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

Whatever good points you are making are obscured by the overly aggressive tone of your comment.

Re: Fig now supports JetBrains IDEs

#24

Post by ushakov »

mschrage wrote: post #18
ushakov wrote: post #15

Earlier quoted context omitted.

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

where does terminal lack user-experience in your opinion?

you really think your proprietary, VC-baked, telemetry-enabled product would improve developer experience?

a terminal is accessible as it gets and doesn’t need a web interface

this is just a pervert version of Electron

Re: Fig now supports JetBrains IDEs

#25

Post by ushakov »

mschrage wrote: post #22
ushakov wrote: post #19

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

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

#26

Post by sanjayio »

ushakov wrote: 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…

Not to mention the possible security vulnerabilities associated with having telemetry on keyboard events.

Re: Fig now supports JetBrains IDEs

#27

Post by ushakov »

mschrage wrote: post #6
DiabloD3 wrote: 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?

I think there are two main areas where we improve the default experience. 1. Zero configuration needed to get started. With Fig, the experience just works out of the box. A lot of developers - especially people less comfortable with the terminal - don't feel confident installing a bunch of 3rd party zsh completions or creating a custom setup. 2. Extensibility. We've worked really hard to make the experience of writin…

> especially people less comfortable with the terminal - don't feel confident installing a bunch of 3rd party zsh completions or creating a custom setup

are you telling us that your proprietary blackbox that asks my e-mail and sends telemetry data is better than open-source well-documented, widely-used, established tools?

> Lots of teams are using Fig to make internal scripts and CLI tools more ergonomic and discoverable.

can these completions be used outside of Fig?

i guess not, because this doesn’t make you any money?

> In my experience, writing custom shell completion scripts is not very much fun

yep, because nobody usually writes them, they’re autogenerated by whatever CLI framework you’re using

with Fig you write them and yes, writing autocompletions for Fig manually is better than writing Compdef manually

but again, nobody usually writes them…

Re: Fig now supports JetBrains IDEs

#28

Post by number6 »

ushakov wrote: post #25
mschrage wrote: post #22

Earlier 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!

Or just use git. It also has versioning in case you want to revert a change.

There are like 100 blog posts on how to manage your dotfiles...

Re: Fig now supports JetBrains IDEs

#29

Post by mschrage »

ushakov wrote: post #24
mschrage wrote: post #18

Earlier quoted context omitted.

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

where does terminal lack user-experience in your opinion? you really think your proprietary, VC-baked, telemetry-enabled product would improve developer experience? a terminal is accessible as it gets and doesn’t need a web interface this is just a pervert version of Electron

Tens of thousands of developers use Fig everyday and seem to really enjoy the autocomplete affordances that we've added.

That said, if you already are very comfortable in the terminal, some of the pain points that we're tackling might be less acute for you.

Re: Fig now supports JetBrains IDEs

#30

Post by number6 »

ushakov wrote: post #27
mschrage wrote: post #6

Earlier quoted context omitted.

I think there are two main areas where we improve the default experience. 1. Zero configuration needed to get started. With Fig, the experience just works out of the box. A lot of developers - especially people less comfortable with the terminal - don't feel confident installing a bunch of 3rd party zsh completions or creating a custom setup. 2. Extensibility. We've worked really hard to make the experience of writin…

> especially people less comfortable with the terminal - don't feel confident installing a bunch of 3rd party zsh completions or creating a custom setup are you telling us that your proprietary blackbox that asks my e-mail and sends telemetry data is better than open-source well-documented, widely-used, established tools? > Lots of teams are using Fig to make internal scripts and CLI tools more ergonomic and discover…

If zsh is to complicated just use fish...
Post reply on HN