141–150 of 208 posts
I installed Fig just now and got "Something went wrong. Signups are currently disabled." when I tried to use it. Their servers have been overwhelmed by Hacker News traffic presumably.
There is a note: ``` Note: While we integrate with AWS, Fig is currently not accepting new sign ups ```
Earlier quoted context omitted.
There is a note: ``` Note: While we integrate with AWS, Fig is currently not accepting new sign ups ```
Yeah, now I see it. Banning signups just when they get an inrush like this seems a boneheaded move. You never know who you can upsell on AWS later. brew remove fig
> 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…
Idk though, this doesn't seem useful enough to me as an individual that I'd bother looking into it. Maybe for a team or company.
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…
I'm a super confused soul, and currently I use all of them:
- Emacs (for clojure / lisps / big projects).
- NeoVim (for when I want to work in the shell, smaller scripts/playground, ssh).
- VScode (js / ts / frontend / figma / etc).
I've made both my vim and emacs keybindings / features almost identical, so there is limited context switching there.
I feel very slow in VSCode, I don't even have one of my most common task optimised in VSCode yet: grepping something and quickly moving to that buffer.
Earlier quoted context omitted.
That wording implies an asset sale which is for anyone involved in or doing business with Fig a big difference. In that case existing ownership and obligations stay with the original entity (probably something like Fig Inc, Delaware corp), the whole team gets hired on at Amazon, Amazon buys the tech they want for some payment the Fig board signs off on, and then someone goes in to clean up and wind down Fig Inc. It's…
... and ther's a big difference in taxation.
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…
And this isn't coming from some FOSS ideology. I don't personally care about any of that, but the best tools are sometimes FOSS. I've got a Mac and can deal with Linux as needed.
Oh times have changed. In days past acquisitions of startups by big tech were met with congratulation and adulation. Today they are met with dread and despair.
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.
Fig has been a godsend for acting as glue for one-off bash scripts that are added to repos.