-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fig is joining AWS! 🚀 #2706
Comments
Could have sworn there were comments here earlier... ? |
And the worst thing is that you disabled new signups ... [Update] |
Linux port seemingly abandoned? No activity for 1.5years now... |
@brendanfalk could we at least get a rough estimate for when signups will be allowed again? I only learned about fig because there's a lot of buzz created about it from it being acquired by AWS, as I'm sure a lot of others have. I'm looking forward to using it, but that being said it's definitely not a good look for potential new users to be greeted with an ASCII text response in the web browser saying "new signups are currently disabled" without any further context. |
This software is currently unusable... |
Abandonware? |
I doubt this project will ever enable SignUps again. AWS doesn't acquire orgs to keep them or their projects alive. It acquires them so that it can add take their USP and add it exclusively to AWS, and eventually monetize it. I would be very, very surprised if Fig accepts signups ever again. The next I am expecting to see of fig is inside AWS, potentially integrated into AWS-CLI or something similar. |
@CrazyByDefault if that's true then they should close up shop with their current website, etc, because what's here currently is misleading at best. |
|
@CrazyByDefault don't worry,since this project is open source, we can fork it |
@jzuhone I laughed so hard. Ugh 1 day of deleting peoples comments and then 2 weeks of silence for users... I already recreated all the useful parts of fig in my own setup repo. People can't afford downtime like this. |
@miclgael Did you create a fork of fig? or grab the functions you were using from fig and put them in your new macbook setup repo? Did you find an alternative for the fig cli dropdown autocomplete? |
Heya @WybeBosch 👋 Yep, I moved everything of most value to https://github.com/miclgael/setup/tree/main/dotfiles I did fork the main fig repo, but decided not to do anything with that. I am no longer using fig's autocomplete, instead using the tried and true |
With Fig being highlighted today in Medium's newsletter, I'm very disappointed that I can't sign up today. Your announcement also said that a new signup link will be available in the coming weeks, so where is that new link? |
@brendanfalk I'd love to delete my account. Any updates on accounts? |
I hope to receive registration support soon |
November 17 still not work. |
I have already uninstalled this app. |
Took the cash and ran |
According to #2577 (comment) we aren't going to get support. There's two separate issues where fig eats all CPU and all Memory which won't get fixed because you're only back-porting security issues. It's effectively unusable on my computer. I think you need to put in a disclaimer in the repo that this project is not really supported anymore because it's confusing. Additionally for those of us that have a paid subscription, I can't select the free plan, am I going to get billed again when the billing cycle comes around? |
This is extremely disappointing. I've been watching this thread and it hasn't progressed. At this point I can assume Fig is abandonware. Perhaps it's time to fork it and have a community maintain it. |
@miclgael Their privacy policy says you have to email hello@fig.io to revoke permission and request deletion. Privacy Policy |
....and now Fig is buckling, as many open-source or startup companies do when they get acquired or backed by the giants. Seriously disappointed with you guys, especially as a former worker for a partner to Fig. |
cash grab for sure, time to move on. |
I've recently reverted from codewhisperer to fig due to ongoing issues that codewhisperer has not patched since release. This includes aliases not beign recognized and most recently that there are dozens of long lived zsh sessions that get orphaned running on my machine. Not only that bug fig is consistently faster than codewhisperer. If these issues still persist after Sep 1, I'll just have to go back to a figless life because codewhisperer is not production ready. |
I guess my terminal is going to suck a lot more going forward then. |
you can try warp.dev |
Hi, I don't know the Fig product at all, however I'm wondering what's going to happen to manual pages ? Thanks |
Ever since it changed to Amazon Q i've been having issue after issue, before it just worked. Anyone know if there is any alternative aside from warp? I would like to have it integrate with the vscode terminal, and i remember that not being possible with warp. |
This is the worst thing ever & we are not even allowed to keep using an older version. |
I am thrilled to announce that the Fig team will be joining Amazon Web Services (AWS) and Amazon has acquired Fig.io’s technology. See the announcement here
Fig and AWS share a passion for improved developer tools and services. By combining Fig’s expertise with AWS’ long-term orientation and track record of delivering customer-centric products, we see an opportunity to enhance the developer experience.
Existing users will continue to be able to use Fig and will receive ongoing support. In fact, we are now making all the paid Fig Team features completely free. New users will not be able to sign up for Fig.io’s products right now while we focus on optimizing them for existing customers and addressing some needs identified to integrate Fig with AWS.
As always, we are incredibly thankful to our community for its continued support. With hundreds of thousands of users, 22k GitHub stars, 13k Discord members, 400 open source contributors, and 5 core products, we could not be more proud of what you have helped us accomplish over the last 3 years.
We can’t wait to continue to innovate with you.
The text was updated successfully, but these errors were encountered: