[HN Gopher] Amazon acquires Fig
___________________________________________________________________
Amazon acquires Fig
Author : fatfox
Score : 270 points
Date : 2023-08-28 16:13 UTC (6 hours ago)
(HTM) web link (fig.io)
(TXT) w3m dump (fig.io)
| rexreed wrote:
| 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.
| [deleted]
| cush wrote:
| Fig is awesome. Congrats to the team!
| w0mbat wrote:
| 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.
| high_priest wrote:
| There is a note: ``` Note: While we integrate with AWS, Fig is
| currently not accepting new sign ups ```
| w0mbat wrote:
| 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
| hot_gril wrote:
| Really makes me think they don't intend to keep it around
| for long.
| [deleted]
| masto wrote:
| 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 platform-
| specific thick client apps no longer feel like the way to go.
| askew wrote:
| You may be thinking of Warp (https://www.warp.dev/)
| veg wrote:
| There's no need for a new terminal. Their homepage literally
| says "IDE-style autocomplete for your existing terminal".
| hot_gril wrote:
| I also thought the wrong thing at first since the big front
| and center title on the homepage says "The next-generation
| command line."
| rollcat wrote:
| To be honest I do think it's time we move on from emulating
| teletypes, but I also believe that whatever comes next has to
| be an open standard, with competing implementations.
|
| There's a whole graveyard out there of "next-gen" terminal
| projects, and none of those still alive seems to be gaining
| dominance. I don't think writing down a spec would help this,
| but it would be great if whatever emerged victorious had one.
| hot_gril wrote:
| Sticking to Vim and other very well-established CLIs is
| partially what enabled flexibility for me. As long as I have
| access to a *nix machine locally or over SSH, I have a capable
| dev setup that I'm well-versed in. Same thing for the past 8
| jobs I've bounced around in, whether in-office or remote, with
| whatever security restrictions, with or without a desk, maybe
| with just a 13" laptop. It's the lowest common denominator.
| Meanwhile my teammates at my current job are constantly trying
| to protect their workstation setups so they can use their IDEs
| locally, and they've also been forced to switch IDEs twice in
| the past couple of years.
|
| 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.
| [deleted]
| oxalorg wrote:
| Curious to learn more about your switch from Emacs to VSCode?
|
| 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.
| Alifatisk wrote:
| I had completely forgot about Fig, I remember trying it out on my
| previous laptop, it didn't offer anything more than my zsh-
| autocomplete, which made me send in my feedback before
| uninstalling.
|
| The telemetry part didn't bug me that much, but the product
| itself was cool, reminds me of warp.dev
|
| Congratz on the acquisition.
| ibdf wrote:
| Congratulations! I've been using it for about a year or so.
| Hopefully their product will continue to exist... that's what
| their blog says now, but that's pretty much what everyone says at
| first.
| sdesol wrote:
| > Hopefully their product will continue to exist
|
| They seem to have built a decent community, so I can see it
| continuing, provided the core/all code for Fig is open source.
| In the last 6 weeks, 57 new contributors took the time to
| create 62 issues and 111 new contributors took the time to
| comment. These are very heathy community metrics, but there
| hasn't been a lot of code activity, which would make sense if
| they were focused on the sale to AWS.
|
| Source for my insights from
| https://devboard.gitsense.com/withfig
|
| Full Disclosure: This is my tool
| acka wrote:
| AFAICT the core of Fig isn't open source. (Why else would
| there be a waiting list for Linux users if they could just
| grab the code for Fig and build it themselves?)
|
| What you are looking at seems to be a repository of
| autocompletion specs and some server to publish them.
| scarface_74 wrote:
| > There aren't any updates to share at this time on future plans,
|
| Wait for the "Our amazing journey" post where Amazon is just
| going to shut their product down
| appel wrote:
| Yep. Unfortunately great for the founders and (hopefully) for
| the team, but my first thought is always "another one bites the
| dust". Here's hoping we're both wrong.
| scarface_74 wrote:
| Well, not that I have any particular insight on how
| acquisitions work at AWS. But as a recent former employee in
| Professional Services, I do know how AWS operates as far as
| go to market strategies since we officially came under sales.
| Even though I was a billable consultant.
|
| It would make no sense for AWS to treat this as ongoing
| concern. They are probably going to integrate it with their
| other products - Cloud 9 , the AWS CLI, CloudShell etc.
| [deleted]
| nikolay wrote:
| Seems like an acquihire!
| tgv wrote:
| 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.
| mteigers wrote:
| 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 on the outputs.
|
| Fig has been a godsend for acting as glue for one-off bash
| scripts that are added to repos.
| blondin wrote:
| i never thought fig or warp would ever work. requiring an account
| and a subscription to use CLI tools sounds ludicrous. but they
| seem to have found a silver bullet with AWS since having an
| account is a requirement anyway.
|
| good luck to them on what comes next.
| rvz wrote:
| Another so called 'incredible journey' which the VCs (including
| YC) accelerated an exit.
| swyx wrote:
| nobody's forcing amazon to do anything they dont want to do lol
|
| but it is true that this is a rare devtools startup acquisition
| by amazon. i cant think of many here (cloud9 was the last one i
| know, and that was 2016) but that could be due to my ignorance.
| [deleted]
| jackblemming wrote:
| Seems like I dodged a bullet. When I interviewed there the
| founder asked very generic questions that may as well have come
| straight out of an Amazon leadership principles pamphlet. I bet
| Amazon will be a good fit for them. I feel bad for the employees
| who likely wanted to work for a startup, not Amazon. I'd be
| surprised if they got much from the acquihire either.
| w0mbat wrote:
| Acquihires generally get a better comp deal than hires, they
| just don't tend to make much off the acquisition deal unless
| they are high up. If their comp includes accelerated vesting
| rather than the terrible Amazon slowcoach vesting it could be
| decent.
| [deleted]
| ams92 wrote:
| You join a startup in hopes of it getting acquired or going
| public some day. Fig was never going to go public so if I
| worked there I'd be happy about the acquisition assuming that I
| wasn't stiffed on my stock options when joining.
| shrimpx wrote:
| Unless it's an acquihire where you get ~nothing for your
| stock and you have to interview to keep your job.
| the_duke wrote:
| > 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 current users I guess.
| api wrote:
| 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
| cloud and charging monthly rent..."
| politelemon wrote:
| 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.
| nojito wrote:
| > 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.
| hot_gril wrote:
| If Fig goes down, you fall back to the regular shell that
| doesn't have autocomplete etc. If Fig gets hacked, that's
| scary, then again GitHub and others are similarly big
| targets.
|
| 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.
| gpvos wrote:
| They give a timeline of a few weeks, so presumably we'll see
| soon enough.
| berkes wrote:
| 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?
| scosman wrote:
| 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.
| dwaltrip wrote:
| > 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?
| theolivenbaum wrote:
| Reminds me of Slapdash's and Command-E acquisitions. Both
| still living in a limbo last I checked...
| jtreminio wrote:
| Command-E is now Dropbox Dash and has been receiving fairly
| heavy promotion.
| ryneandal wrote:
| Yeah, that is my expectation about its future as well. I really
| enjoyed using Fig for clear CLI introspection for many of my
| common workflows.
|
| I am fully expecting that I'll have to go back to zsh-
| autosuggestions once the current iteration is fully wound down.
| Brajeshwar wrote:
| That was fast. Fig's HackerNews launch (May 25, 2021)
| https://news.ycombinator.com/item?id=27277819
|
| Have seen Brendan talk a lot about it on Twitter.
| nerdjon wrote:
| Will be interesting to see what happens to this long term, but
| hopefully means good things. I use the tool personally but really
| for largely basic things.
|
| The dropdown for autocomplete is far from necessary but a nice
| addition. Helping with completing commands that I don't use often
| but know the basics of like "aws s3 cp" is nice. But because of
| that I could just never justify spending money on it.
|
| Hopefully it isn't abandoned, but maybe this will also mean they
| don't have to try to find artificial reasons (or bloat) to
| convince people to pay and can just focus on the core offering.
| diebillionaires wrote:
| I can't help but not want to use a CLI I have to log into.
| [deleted]
| pbbakkum wrote:
| Plugging a project of mine: I've been working on a similar idea
| for the era of LLMs: https://butterfi.sh.
|
| It's much more bare-bones than Fig but perhaps useful if you're
| looking for an alternative! Send me feedback!
| Hamuko wrote:
| Is this in any way related to the fish shell or is this just a
| very unfortunate name?
| politelemon wrote:
| > Within Butterfish Shell you can send a ChatGPT prompt by just
| starting a command with a capital letter, for example:
|
| This is a dangerous assumption. Not all commands are lowercase.
| Interaction with an external service should be a deliberate,
| discrete action on the user's part.
| subw00f wrote:
| I like that a lot! It would be awesome if the client running on
| goal mode had capabilities to request some search engine API +
| do some crawling. Imagine getting the info out of up to date
| github issues or directly from AWS docs.
| xcdzvyn wrote:
| Just curious, do you have any intent on adding local model
| support?
| pbbakkum wrote:
| I've experimented with it, the reason I haven't yet added it
| is that I want deployment to be seamless, and it's not
| trivial to ship a binary that would (without extra fuss or
| configuration) efficiently support Metal and CUDA, plus
| download the models in a graceful way. This is of course
| possible, but still hard, and not clear if it's the right
| place to spend energy. I'm curious how you think about it -
| is your primary desire to work offline or avoid sending data
| to OpenAI? Or both?
| desireco42 wrote:
| This is very damaging for other startups. You create something,
| then you ask people to believe you and invest their time and
| sometimes money with you.
|
| Then you, in act of desperation, sell out and sell your users...
|
| The issue is, people are already super skeptical when these
| startups start asking for things, this just makes them even
| harder to get users to trust you as a emerging company or product
| with data and usage.
| hot_gril wrote:
| Startups don't have big reputations to protect unless they're
| tied to someone famous, and also they need a path towards
| acquisition for early investors to care. There isn't really a
| way around that.
| mullingitover wrote:
| Seems like tough competition in this space. Warp has what's
| essentially Github Copilot in the CLI, and it's the same price.
|
| Beyond that, actual GH Copilot does a damn good job of crafting
| any CLI command that you can describe.
| mirekrusin wrote:
| Where is open source alternative?
| mavamaarten wrote:
| Fig works in any terminal though, and its free tier gives me
| useful enough recommendations and docs. It's very useful to be
| able to use IDE-like autocomplete inside my IDE, which is the
| terminal I use 99% of the time. As far as I'm aware, Warp is
| really a standalone gig.
| Takennickname wrote:
| Isn't it mac only?
| jarek83 wrote:
| Interesting - I tried Fig for few days few months ago, it gave me
| more headaches than relief so uninstalled it. Surprised that it
| made into a viable product and shocked it actually got acquired.
| myth_drannon wrote:
| I checked Fig when it was announced but preferred Warp for some
| reason. I think it looked nicer and was snappier.
| acmecorps wrote:
| Tried to check it out, but I got "Signups are currently disabled"
| :(
| gurchik wrote:
| > 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.
| throwaway8725 wrote:
| I was trying to get it working and it seems like running `fig
| login` in the terminal and then restarting the app enables the
| terminal autocomplete!
| charles_f wrote:
| How does that align with Amazon's product line? Is Fig an online
| product?
| SoftwareDev6 wrote:
| Pretty cool for the Fig team.
| dexterdog wrote:
| Probably not the entire team.
| nicechianti wrote:
| [dead]
| ranting-moth wrote:
| How does one join AWS?
| ilc wrote:
| 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.
| throwawayfigs wrote:
| [flagged]
| asadm wrote:
| leetcode and reducing self-respect
| shermix011 wrote:
| So AWS's dev ex will get better?
| firstSpeaker wrote:
| very likely this will become part of AWS CodeWhisperer. I
| wouldnt be surprised if MSFT or GOOG going after WARP for
| example to counter balance.
| varispeed wrote:
| [flagged]
| [deleted]
| msoad wrote:
| is this an aquahire?
| KolmogorovComp wrote:
| To spare someone else a research, it's another term for 'talent
| acquisition' [0].
|
| [0]: https://en.wikipedia.org/wiki/Acqui-hiring
| krembo wrote:
| In times of employers market it's less likely to see aquahires
| ilc wrote:
| The market is starting to shift. It ain't where it was a year
| and a half ago... but the numbers say, it ain't what it was a
| few months ago.
| [deleted]
| mzg wrote:
| No, presumably these employees will be based on dry land
| Brajeshwar wrote:
| I'm not one that laughs at others' auto-correct bloopers. I
| have made quite a lot of mistakes myself. But your quick
| reply made me laugh for a good 90-sec or so.
| tough wrote:
| lmao some times auto-correct typo's are better than what
| you wrote indeed
| wpietri wrote:
| Right? To me it's more than just a cheap joke because it
| opens such possibilities. My first thought was of Amazon
| expanding out under Puget Sound in Bioshock-esque sunken
| office buildings.
| stevenally wrote:
| No, it's an aquahire. They're joining Amazon...
| [deleted]
| ibejoeb wrote:
| Rumor is they're going to offshore the whole operation...
| cjaybo wrote:
| Once they dry off after leaving the hiring pool at least
| kashnote wrote:
| Slow. Clap.
| throwawayfigs wrote:
| "I am thrilled to announce that the Fig team will be joining
| Amazon Web Services (AWS) and Amazon has acquired Fig's
| technology! "
|
| That's possibly the most inefficient way of saying "AWS bought
| Fig" but I guess it makes some people happier to frame it that
| way
|
| In any event, I'll pass on "the CLI with a subscription that
| sends telemetry".
|
| Paying hard earned dollars _every month_ for a terminal is
| something so out of the realm of the possible for me I 'm
| honestly baffled to see this has any customers...
| hedgehog wrote:
| 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 common
| when big companies buy much smaller companies because doing a
| full purchase can be a lot more complicated.
| guytv wrote:
| ... and ther's a big difference in taxation.
| hedgehog wrote:
| 100% I would imagine there are big differences on both
| sides, and possibly some ways to exempt some of the payment
| for assets against the cost of building them. People don't
| usually write much about this level of detail but it would
| be interesting to see.
| guytv wrote:
| If the arrangement involved both a tech purchase and a
| contractual obligation for employees to stay with AWS for a set
| period, simply saying "Fig was acquired" wouldn't be accurate.
| Given that Amazon is a publicly traded company, making such
| misleading statements is a no-go.
| hoffs wrote:
| This seem like perfect replacement of Amazon's cloud shell
| thing
| tesseract wrote:
| > That's possibly the most inefficient way of saying "AWS
| bought Fig" but I guess it makes some people happier to frame
| it that way
|
| Often that kind of language is employed when the actual
| transaction was structured as an asset sale coupled with en-
| masse hiring of the team, rather than a true acquisition of the
| company as a complete entity, which is not an unusual scenario
| when a company is in distress.
| [deleted]
| dang wrote:
| We usually change such titles to something like "$Acquirer
| aquires $Acquiree" and I've done that above now.
| hot_gril wrote:
| Amazon buying Fig doesn't imply the team joins AWS.
| gdsdfe wrote:
| when a company buys another company it kinda does the
| opposite would be the outlier
| onion2k wrote:
| It's much more common for the acquired company to continue
| as an entity in its own right with only the board changing
| in the short term, and often continuing as a brand within
| the acquirer's business in the long term. Integrating a
| existing team into a company is hard. That said, Amazon has
| a lot of experience doing exactly that. I think they'll be
| fine.
| hot_gril wrote:
| Amazon isn't the same thing as AWS. Amazon might have
| bought Fig and kept the team separate, or they might've
| kept the tech and shortly after let the team go.
| [deleted]
| [deleted]
| bastardoperator wrote:
| I could never love it, but hopefully that's a nice exit for
| everyone involved. Congrats.
| rmorey wrote:
| I love this product, have contributed several times to it, and
| I'm a little torn. One thing I am thinking about now, is that the
| completion specs are MIT-licensed, and it should be possible to
| use them to re-implement a basic open-source version of the
| autocompletion product... https://github.com/withfig/autocomplete
| theusus wrote:
| [flagged]
| marstall wrote:
| maybe don't comment then?
|
| It's a legit cool product that, among other things, lets you
| use natural language in the unix command line.
| ilaksh wrote:
| Is there anything similar for Linux?
| topato wrote:
| There is a Linux and (I believe) a Windows binary of Fig
| available. You might need to hunt a bit to find it, at least, I
| needed to last year. Their Discord used to be the place for
| that info.
| KomoD wrote:
| Except we (new users) can't use it regardless, since signups
| are closed.
| candiddevmike wrote:
| Seems like direnv and shell scripts in a shared git repo could
| be similar:
|
| https://direnv.net/
| dinckelman wrote:
| As a regular terminal user, I didn't find Fig particularly useful
| to begin with, but this just made me remove it entirely
| ae_throw wrote:
| [flagged]
| gabereiser wrote:
| Congratulations!? I do hope that means AWS's ever growing cli
| commands will be all fig now (or will be)? It's getting a bit
| long in the tooth. What about support outside of AWS? Will fig
| still be as awesome in iTerm2 with what-ever-is-in-%PATH%?
| 404mm wrote:
| He's thrilled because it's good for him, not for the users.
| johnnyanmac wrote:
| can't blame them. work on what seems to be a obviously needed
| tool, manage it for 2.5 years, then get "not acquired" by
| Amazon to take it off your hands, especially since the money
| was coming from enterprise and larger teams to begin with.
| merryje wrote:
| > 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.
| hot_gril wrote:
| If they aren't making money directly off Fig, they're
| integrating it somehow.
| w0mbat wrote:
| Except people just hearing about Fig now can't sign up.
| candiddevmike wrote:
| It means they're abandoning the product IME
| seizethecheese wrote:
| Is it not?
|
| Any venture funded product has a sword of Damocles over its
| head. After acquisition the company product is much less
| likely to be shut down in the long run (unless it's Google).
| miah_ wrote:
| No, after acquisition usually the existing product is
| usually shutdown or phased out while its features are
| absorbed into some <new thing>.
|
| With Google, everything has a huge chance of being
| shutdown, unless its Gmail or Search, but in both of those
| cases they will also continue to get worse over time.
| hot_gril wrote:
| or at least become more annoyingly entangled with stuff,
| like Minecraft + Microsoft
| jsnell wrote:
| Days since AWS last announced they were killing a devtool
| service: 4
|
| (https://news.ycombinator.com/item?id=37254198)
| candiddevmike wrote:
| The blog post reads like an acqui-hire, which almost always
| means the product gets shut down or open sourced and left
| for dead.
| w-ll wrote:
| Wait, this is Autocomplete for $12/month?
| k4rli wrote:
| Based on their frontpage example videos, it seems to be for Mac
| users who don't know any better. I don't see anything useful
| that isn't FOSS already.
| yohannparis wrote:
| 1. Packaging solution in an easy to use tool is what software
| engineers do. Nothing wrong with non-FOSS solution.
|
| 2. You could provide a list of FOSS solutions to replace
| Fig.io, even better write a tutorial on how to install and
| setup those solutions.
| hot_gril wrote:
| Either the FOSS solutions are lacking something or all those
| corporate customers are fools.
| daotoad wrote:
| Even if the only thing fig adds is easier set up and
| integration and consistency of setup between users that
| could be enough to justify the cost.
|
| Saving an hour of engineering time spent fiddling with your
| CLI config every year makes this a good value for a
| business.
| hot_gril wrote:
| Yes. Plenty of people know how to DIY or can figure it
| out, it's not a special skill. They just don't consider
| it worthwhile.
| Brajeshwar wrote:
| Wait till you learn about Raycast. https://www.raycast.com
|
| I've heard a lot of good things about Raycast. I'm very tempted
| to jump ship from Alfred. Still hanging on.
| orliesaurus wrote:
| I use Raycast - it's pretty dope and I also made my own
| extensions
| randomsofr wrote:
| ive been using raycast on a new computer, i prefer alfred,
| much faster, and i know the tooling better.
| mavamaarten wrote:
| Try it. I've jumped ship a while ago, and it's amazing. I
| miss it a lot on Linux and Windows, FlowLauncher doesn't feel
| nearly as polished and I already forgot which launcher I use
| on my Linux install.
|
| The ones I love the most are Keepass, Bitrise, and the fact
| that you can just press enter to join the Google Meet call
| attached to the next upcoming meeting.
| dexterdog wrote:
| I was a 10-ish year paid user of alfred and decided to try
| raycast about a year ago. I've never gone back to alfred.
| [deleted]
| [deleted]
| snoose wrote:
| No, its free, just some "advanced" features cost money
| l5870uoo9y wrote:
| I reckon scripts and secrets sharing within teams is the
| primary feature customers pay for.
| [deleted]
| ibdf wrote:
| It does more than just autocomplete and it does it well.
| pbmango wrote:
| Congrats! Big fan of Fig and excited to see the UX brought to aws
| CLIs
| eikenberry wrote:
| I feel sorry for their remote employees as their company just
| sold them out.
___________________________________________________________________
(page generated 2023-08-28 23:01 UTC)