Ehh, time to uninstall. Too bad, it worked great for me.
Amazon acquires Fig
191–200 of 208 posts
Re: Amazon acquires Fig
#192First time hearing of fig, other than when the name was used for a precursor to Docker Compose.
Is this effectively very similar to Atuin?
Re: Amazon acquires Fig
#193Earlier 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?
Do you know of any product that was acquihire and wasn't decimated?
I think there’s the definition of acquihire.
Re: Amazon acquires Fig
#194Earlier 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?
They want to move the customers to a new AWS service (that will be this product rebranded with AWS) and tie into AWS infrastructure instead of using a special system for sign in.
By preventing sign ups, they fix the number of accounts that will need to be migrated in future.
Re: Amazon acquires Fig
#195Earlier quoted context omitted.
Isn't Fig open source? Now'd be the time for people to fork it while there's still the opportunity to do so if they find genuine value in the project. My favorite 'acquihire' story is when Oracle bought out MySQL and the creator forked it and made MariaDB.
when Oracle bought out MySQL and the creator forked it and made MariaDB Not quite. Wiki tells me: https://en.wikipedia.org/wiki/MySQL#History Sun Microsystems acquired MySQL AB (the company) in 2008. Oracle acquired Sun Microsystems in 2010. The day Oracle announced the purchase of Sun, Michael "Monty" Widenius forked MySQL, launching MariaDB, and took a swath of MySQL developers with him.
Correct, I just kinda lumped it all together, apologies on the mix up. I rather miss when Sun was not owned by Oracle.
Re: Amazon acquires Fig
#196Earlier 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 was at Cloud9 which was acquired by Amazon. We took most of the existing frontend and tech and rebuilt the backend on AWS, then relaunched it as AWS Cloud9. In the meantime we sunset the existing service. I'd assume the same thing is going to happen here.
How was the exit on your end
Re: Amazon acquires Fig
#197Earlier 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…
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.
There are degrees of insecurity. Typing secrets into a terminal is not good. Typing secrets into a terminal with telemetry is worse.
Re: Amazon acquires Fig
#198Earlier quoted context omitted.
1. Wrong thread. 2. IMHO: Be in the wrong place at the wrong time. I've never heard a happy story about Amazon that didn't involve a metric ton of Kool-Aid.
Kool-aid was mostly leaders ending regurgitating leadership principles and gaming it (without internalizing the greatness of it)
I've seen some employees that drank it too much.
IMHO: Drinking the Kool-Aid is OK if you like the flavor. Just realize you are doing it.
Re: Amazon acquires Fig
#199> 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…
I would use this as the way for company's command line tools to be provisioned to me as a team member. This means my tools can be separated from work tools
Re: Amazon acquires Fig
#200Earlier 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.
The blog post doesn't mean anything. HN is full of congratulatory posts of acquihires. They're all the same. "Now that we're part of $BIGCO we'll be working to integrate our technology into $BIGCO." It never happens. If $BIGCO had any intent to keep the product along, you'd be reading the post on $BIGCO's blog, not $FAILEDSTARTUP's blog.
Acquirers typically add terms to deal preventing vanity announcements and defining shutdown timeline. They don’t want the overhead of maintaining, or the negative brand hit. Each case is different, but there’s always a plan. They probably have some reason to keep maintaining the current customers/product, we can just guess what it is.