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

Amazon acquires Fig

fig.io

Post reply on HN
Print view View original

151–160 of 208 posts

Re: Amazon acquires Fig

#151

Post by dwaltrip »

scosman wrote: post #121
berkes wrote: 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?

I read it as “hosted AWS version coming soon, we will email you when it’s time to migrate”. If it was just acquihire there probably wouldn’t have a big blog post tying it to AWS. Just negative publicity for acquirer when they could shut down quietly.

> If it was just acquihire there probably wouldn’t have a big blog post tying it to AWS. Just negative publicity for acquirer when they could shut down quietly.

That’s a good point.

But what reason is there to disable new registrations?

Re: Amazon acquires Fig

#152

Post by nojito »

politelemon wrote: post #140
api wrote: post #114

Earlier quoted context omitted.

I would never use a cloud-syncing cloud-connected terminal for simple security and privacy reasons alone, not to mention the fact that if it goes down I become basically disabled as a developer or admin. Several companies have tried to SaaSify the terminal and failed, so I suspect I am not alone here. "We've noticed that there's a component of the computing infrastructure that isn't sending everything you do to the c…

Yes I'm genuinely shocked at the other comments here saying they use this happily; it should be a cause for concern. That it's now landing in Amazon's lap, doubly so.

> All cloud features are opt-in and your data is encrypted at rest. For autocomplete, all of your keystrokes are processed locally and never leave your device.

Fig is a great product.

Re: Amazon acquires Fig

#153

Post by fragmede »

dwaltrip wrote: post #151
scosman wrote: post #121

Earlier quoted context omitted.

I read it as “hosted AWS version coming soon, we will email you when it’s time to migrate”. If it was just acquihire there probably wouldn’t have a big blog post tying it to AWS. Just negative publicity for acquirer when they could shut down quietly.

> If it was just acquihire there probably wouldn’t have a big blog post tying it to AWS. Just negative publicity for acquirer when they could shut down quietly. That’s a good point. But what reason is there to disable new registrations?

Terms of the acquisition, most likely. Existing customers are worth $x/yr. New customers with the new product are worth $y/yr. Finance doesn't want $x competing with $y. Something something financial models making the deal worth what they paid, so closing registration is simply part of the deal that was signed.

Re: Amazon acquires Fig

#154

Post by fragmede »

api wrote: post #114
the_duke wrote: post #72

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

I would never use a cloud-syncing cloud-connected terminal for simple security and privacy reasons alone, not to mention the fact that if it goes down I become basically disabled as a developer or admin. Several companies have tried to SaaSify the terminal and failed, so I suspect I am not alone here. "We've noticed that there's a component of the computing infrastructure that isn't sending everything you do to the c…

As a side note, if your security relies on you typing things into your terminal, you're doing it wrong. AWS even makes you check a box when generating creds that basically says "I understand the way I'm doing this is insecure" when generating creds that will be used that way.

Re: Amazon acquires Fig

#155

Post by chrysoprace »

masto wrote: post #55

These features are nice, but I've never liked the idea of having to use a whole new terminal application to get them. I may be becoming a dinosaur, but it's not that I'm not willing to try new things. On the contrary, after many years of being rigid about having one true development environment, I've moved away from Emacs to VS Code, and work from more heterogeneous environments instead of being 100% Mac. So these pl…

It's not a different terminal application, but an overlay that gives you autocomplete-style suggestions in your existing terminal emulator. I don't know all the terminal emulators it works with since it's MacOS only, but it works in both iTerm2 and the VSCode terminal, granted that you're not using a terminal multiplexer like tmux (which makes it useless for my workflow).

Re: Amazon acquires Fig

#158

Post by derefr »

berkes wrote: post #98
the_duke wrote: post #72

> 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?

> 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?

That’s an easy one: if it’s burning money like crazy on its current hosting, but only because of rents extracted by one of their competitors, not for any inherent OpEx-intensity; and that therefore Amazon expects it to be profitable when moved to live rent-free on their hosting.

Re: Amazon acquires Fig

#159

Post by dangoodmanUT »

the_duke wrote: post #72

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

The telemetry was the exact reason I never tried it. It looked amazing, but wasn't keen on fig getting every one of my inputs

Re: Amazon acquires Fig

#160

Post by keyle »

berkes wrote: post #98
the_duke wrote: post #72

> 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?

Do you know of any product that was acquihire and wasn't decimated?
Post reply on HN