brendanfalk

I think the real problem here is "decision making" as opposed to "collaboration"

I can't think of a single time where having someone else review my work or give me feedback is a meaningfully bad thing. It's an opportunity to learn. But getting feedback is different to making the final decision.

Instead, the real problem is the either 1) lack of knowing who makes the final decision or 2) requiring everyone must agree to a final decision. You will move a lot faster if you know who the final decision maker is, ideally have fewer (or only one person) making that final decision, and encourage people to make decisions quickly (most decisions are reversible anyway)

We built the Shell Plugin Store into Fig[https://fig.io] to solve a lot of the problems mentioned in this thread. Namely: * Plugins are hard to install/uninstall * Plugins are hard to customise once installed * Plugins add bloat and/or degrade performance in shell load time * It's hard to find plugins in the first place (there is not centralised directory) * It's hard to sync plugins and configurations across devices

In Fig, adding a plugin is easy as clicking a button. And if you have issues with it, you can uninstall in a click too

Founder of Fig here. For context, Fig integrates with your existing terminal and shell.

A few things we've found: 1. Developers are understandably opinionated about their terminal/shell setup. It's a matter of personal productivity. 2. We have noticed a general trend of more terminal use happening in IDE, not a standalone terminal. 3. Most terminal "collaboration" happens asynchronously not synchronously (e.g. shared scripts, CLIs, secrets etc as opposed to live terminal sharing) 4. Most of the collaboration happens at the shell level not the terminal level

Given the above, we made the conscious conscious decision not to build our own terminal.

Happy to elaborate more

Interested!

This Google Trend graph shows an increase popularity. The increase has been fairly linear since 2014 but there were notable spikes in late 2021 and early 2022

https://trends.google.com/trends/explore?date=all&geo=US&q=%...

RegExr is my go to tool for testing regex. It’s always been able to solve my needs and I’ve never had any need to change. In saying that, I’ve always wondered if regexr is missing out on something that other regex build/test tools have?

What other regex tools do people use and why?

◧ Fig | https://fig.io | ONSITE (San Francisco) // REMOTE (US timezones) | Full-time

Fig makes engineers and their teams more productive in the terminal.

- Mission: re-imagine the terminal. First, autocomplete (https://github.com/withfig/autocomplete), then fully-fledged App Store with apps like these (https://fig.io/blog/post/launching-fig)

- Why: 50M+ engineers use the terminal. It has barely changed since the 70s.

- Investors: Y Combinator, General Catalyst, Kleiner Perkins, founders/execs of Stripe, GitHub, Heroku

- Traction: One of the largest Hacker News launches of all time; our users love us: twitter.com/fig

We are looking for people who are excited about reimagining the terminal/shell/CLI. We have plenty of open roles:

* Systems Engineer (Rust/C/C++): https://fig.io/jobs/systems

* Full-Stack Engineer (Typescript): https://fig.io/jobs/full-stack-typescript

* Support Engineer (Bash/Shell/CLI): https://fig.io/jobs/support-engineer

Please apply or message brendan AT fig DOT io, we are very responsive!

◧ Fig | https://fig.io | ONSITE (San Francisco) // REMOTE (US timezones) | Full-time

Fig makes engineers and their teams more productive in the terminal.

- Mission: re-imagine the terminal. First, autocomplete (https://github.com/withfig/autocomplete), then fully-fledged App Store with apps like these (https://withfig.com/videos/old-sizzle-reel.mp4)

- Why: 50M+ engineers use the terminal. It has barely changed since the 70s.

- Investors: Y Combinator, General Catalyst, Kleiner Perkins, founders/execs of Stripe, GitHub, Heroku

- Traction: One of the largest Hacker News launches of all time; our users love us: twitter.com/fig

We are looking for people who are excited about reimagining the terminal/shell/CLI. We have plenty of open roles:

* Systems Engineer (Rust/C/C++): https://fig.io/jobs/systems

* Full-Stack Engineer (Typescript): https://fig.io/jobs/full-stack-typescript

* Support Engineer (Bash/Shell/CLI): https://fig.io/jobs/support-engineer

Please apply or message brendan AT fig DOT io, we are very responsive!

But also just to clarify, the intention for this post was how to fix this issue if it had already occurred NOT a "how to install brew correctly" guide.

If the issue had occurred, you wouldn't need to run the eval command again, it would have already been run 1,000 times from your .zprofile. Hence I suggest just to delete all references of it then add back one.

But I do take your point that my post could also have been seen as ambiguous and hence added in your suggested changes.

Agree! I will update this. Good catch. Thank you!

Completely agree. There is a tradeoff between letting user do everything themselves such that they know exactly what's happening in their system vs just doing it for them and making sure they don't make a mistake.

Perhaps a better implementation would be a choice:

    You need too add  `eval "$(/bin/brew shellenv)"` to your dotfiles. Would you like us to do this for you?

    1. Yes
    2. No I will do this myself

Whoops. Forgot to include the https in the link. That always gets me. Thanks for the heads up

Co-founder of Fig (https://fig.io) here.

I'm pleased that there is more innovation in the terminal emulator space. For a tool used by just about every developer, not a ton has changed since the launch of the VT100 [1] in the 70s.

Fig adds autocomplete [2] to your existing terminal. Soon, we're launching the ability for you to build your own visual apps and shortcuts (like these: https://fig.io/videos/old-sizzle-reel.mp4) and share them with your team or the community.

Rather than building our own terminal, we integrate with the terminals you already use (even the one embedded in your IDE). This means everyone on a team can collaborate but keep using their existing terminal and shell setup.

We are excited to integrate Fig with Warp.

[1] https://en.wikipedia.org/wiki/VT100

[2] https://github.com/withfig/autocomplete

Yes! Linux: https://github.com/withfig/fig/issues/34 Windows: https://github.com/withfig/fig/issues/35

Yep I mistyped. Meant to say standard "suggestion" format. Trying to imply that each suggestion conforms to a specific standard that we have set but that lets you customise things like the text it suggests, what is inserted, icon etc

> An obvious extension would be pulling out argparse

Yes absolutely. A lot of possibility. We hope to create a whole new way of building terminal apps!

Not yet, but we are working on integrations. Want to subscribe to the relevant issues:

Alacritty: https://github.com/withfig/fig/issues/28 Kitty: https://github.com/withfig/fig/issues/26 More: https://github.com/withfig/fig/issues?q=is%3Aissue+is%3Aopen...

We plan on adding collaboration features for teams in the future. Autocomplete will always be free for individuals!

> Looks really cool, but I would always use zsh-auto-complete.

Thanks for this feedback. Would love to dig in a little more here. What is it about Fig that turns you off? Is it the idea of having a GUI in the terminal?

> Personally, something like this w.r.t. VC means that incentives will diverge and they lose touch with what it means to be a dev tool.

> Most abstractly I think the misaligned incentives is what happens. I'm not convinced that VCs get dev tools and don't ruin them.

I'd love to hear a little more about your thoughts here. We've committed to making autocomplete free for individuals. In your opinion, what else can dev tool companies like ours do to make you feel more comfortable?

Glad you're liking it!

Our server also crashed when we first posted this.

Try running `fig update` in your terminal. This will download the most up to date version of Fig's completion specs

Yes it will!

See this example: https://fig.io/images/slideshow/screenshots/ssh.png

It should work out of the box, but you may have some issues if you have multiple SSH connections to the same remote machine or if your remote machine uses an async prompt (like powerlevel10k).

If you have any issues, feel free to email me and I'll help get you set up brendan AT fig DOT io

Early versions of Fig essentially used a keylogger to predict what you had typed in the terminal. This is not optimal from a security or product standpoint.

We have since integrated with the shells themselves (e.g. with zsh's line editor, ZLE for zsh). This allows us to get what you've typed more accurately and for your shell only. We are also working on new integration done exclusively through pseudoterminals.

Both of the cases above mean our Linux integration will simply be for window management!

You can see how all of our integrations with bash, zsh, fish, SSH, Docker etc work here: https://github.com/withfig/config

Thanks so much!

Yes - we would love to build our own terminal one day. I agree, a first party experience will make Fig much better. We think a good terminal needs to be fast, cross platform, customisable, and extendable (this is easier said than done).

That said, one day we hope to build team-based tools too. Developers like to choose their tools - we would love to make Fig work, even if you weren't using a Fig terminal. We likely will also do the hard work of integrating with the existing terminals. You choose your tools and Fig is an integration on top.

If you're interested, here are some of the things we plan on expanding into. https://fig.io/videos/old-sizzle-reel.mp4

Glad to hear - is VSCode exploration the same as VSCode Insiders? If so, I believe we do support this too (However I guess the whole idea of Insiders is it is constantly being updated so maybe our integration recently broke).

If it's different, want to create an issue for us and we'll get to it this week? https://github.com/withfig/fig

We're hoping to get onto Linux and Windows soon! We opted to focus on a fast, macOS only version first. However, we built autocomplete in web technologies (html/css/js). This means autocomplete will be able to go cross platform, along with other apps we hope to build in the future!

As in, if you SSH into a remote machine, Fig can offer completions for that remote machine. Same thing if you are running an interactive terminal for a docker container.

This image may help clarify: https://fig.io/images/slideshow/screenshots/ssh.png

Glad you are liking it!

VSCode terminal should be supported out of the box. Go to ◧ > Settings and make sure the VSCode Integration is ticked. (You may also have to restart VSCode.)

re Fig's icon: haha yes we could definitely do with a new icon. Our previous icon was an emoji pear (yes a pear, not a Fig) so at least our current one is a step up from that! We take the feedback on board and will investigate some new logo designs

I hear you and I agree. This is a huge oversight on our part and we will make the disableTelemetry command turn off all telemetry. This will come out in our next build