Live data from Hacker News

Amazon acquires Fig

fig.io

101–110 of 208 posts

Re: Amazon acquires Fig

#101
I had completely forgot about Fig, I remember trying it out on my previous laptop, it didn't offer anything more than my zsh-autocomplete, which made me send in my feedback before uninstalling.

The telemetry part didn't bug me that much, but the product itself was cool, reminds me of warp.dev

Congratz on the acquisition.

Re: Amazon acquires Fig

#104

Seems like an acquihire!

I had never heard about them, but for the life of me, I cannot imagine sufficient paying customers: it's zsh/fish, basically. Sharing the settings is not really a $12/month productivity boost. Acquihire sounds likely.

Re: Amazon acquires Fig

#105
post #99

Seems like I dodged a bullet. When I interviewed there the founder asked very generic questions that may as well have come straight out of an Amazon leadership principles pamphlet. I bet Amazon will be a good fit for them. I feel bad for the employees who likely wanted to work for a startup, not Amazon. I’d be surprised if they got much from the acquihire either.

You join a startup in hopes of it getting acquired or going public some day. Fig was never going to go public so if I worked there I’d be happy about the acquisition assuming that I wasn’t stiffed on my stock options when joining.

Unless it's an acquihire where you get ~nothing for your stock and you have to interview to keep your job.

Re: Amazon acquires Fig

#106
post #98

> New users will not be able to sign up for Fig's products right now while we focus on optimizing them for existing customers and addressing some needs identified to integrate Fig with AWS. This sounds a lot like the product is dead, and may emerge again at some point as an AWS hosted, Amazon branded product... I'd never use a subscription + telemetry laden product like this in my core workflow, but sucks for the cur…

To me the whole post read like "we are aquihired, but we cannot admit we are are aquihired". The closing of registration driving it home. If AWS bought it for the product, what reason would there ever be to stop the current business model entirely rather than leaving it on its current trajectory for a few months, untill said "needs" are addressed?

Reminds me of Slapdash's and Command-E acquisitions. Both still living in a limbo last I checked...

Re: Amazon acquires Fig

#107
I love this product, have contributed several times to it, and I'm a little torn. One thing I am thinking about now, is that the completion specs are MIT-licensed, and it should be possible to use them to re-implement a basic open-source version of the autocompletion product... https://github.com/withfig/autocomplete

Re: Amazon acquires Fig

#108

Plugging a project of mine: I've been working on a similar idea for the era of LLMs: https://butterfi.sh . It's much more bare-bones than Fig but perhaps useful if you're looking for an alternative! Send me feedback!

Just curious, do you have any intent on adding local model support?

Re: Amazon acquires Fig

#109
post #98

Earlier quoted context omitted.

To me the whole post read like "we are aquihired, but we cannot admit we are are aquihired". The closing of registration driving it home. If AWS bought it for the product, what reason would there ever be to stop the current business model entirely rather than leaving it on its current trajectory for a few months, untill said "needs" are addressed?

Reminds me of Slapdash's and Command-E acquisitions. Both still living in a limbo last I checked...

Command-E is now Dropbox Dash and has been receiving fairly heavy promotion.

Re: Amazon acquires Fig

#110

Plugging a project of mine: I've been working on a similar idea for the era of LLMs: https://butterfi.sh . It's much more bare-bones than Fig but perhaps useful if you're looking for an alternative! Send me feedback!

Just curious, do you have any intent on adding local model support?

I've experimented with it, the reason I haven't yet added it is that I want deployment to be seamless, and it's not trivial to ship a binary that would (without extra fuss or configuration) efficiently support Metal and CUDA, plus download the models in a graceful way. This is of course possible, but still hard, and not clear if it's the right place to spend energy. I'm curious how you think about it - is your primary desire to work offline or avoid sending data to OpenAI? Or both?
Post reply on HN