201–208 of 208 posts
How does one join AWS?
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.
Earlier quoted context omitted.
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.
Fig is only two, three years old at most.
Earlier quoted context omitted.
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.
I've been a personal paying customer going on 2 years now. The biggest benefit I get from fig is their "build a script / cli" functionality. With it you can define UI elements like "list all branches" and you have a nice UI sector and then you can string together code snippets using the outputs of the UI elements. So I have some fig scripts that prompt me for half a dozen inputs and then execute bash and python based…
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…
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
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 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.
I worked at AWS from 2010 to 2014 after also getting acqui-hired (AWS SDK for PHP, fka CloudFusion).
Earlier quoted context omitted.
> Existing users will continue to be able to use Fig and will receive ongoing support. What's more, we are now making all the paid Fig Team features completely free. This sounds like a win for users.
Except people just hearing about Fig now can't sign up.
Earlier quoted context omitted.
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
What’s wrong with a company git repo for that?