4 ms·
Well, it was discovered in the process of developing Fig, and they posted it in their blog as a result. Where else? You're right, it's not a great look for any
by forgotmypw17 5y ago
Well, it was discovered in the process of developing Fig, and they posted it in their blog as a result. Where else?
You're right, it's not a great look for any project to post a criticism of another, largely unrelated project. But where else would they post it?
Posting it like this helps it get the exposure it needs. I think posting it to brew's bugtracker would just get it lost.
- herpderperator 5y agoThe criticism of brew's instructions is warranted to be completely honest, they could certainly word that one sentence a little better. But the way I interpreted the parent comment is that it makes Fig employees appear less capable because they don't understand intricacies of the shell, but as I described in my other comment, not everyone has to be an expert of the shell. Brew is not a "power user" tool, it's a package manager for macOS. Instructions should be clear for all types of users.
- mschrage 5y agoTo clarify, a decent number of Fig users (not employees) have been running into this issue. We host our answers to common support requests on Github Discussions!
- indigodaddy 5y agoI meant that a multitude of employees had misunderstood the instructions. If you take a breath and think about what that first line is doing for a few seconds, you’d never put that into your profile.
- forgotmypw17 5y agoI think the article says that they discovered the issue because of Fig users contacting them for support with it, not from Fig developers doing it themselves.
- actually_a_dog 5y agoI wouldn’t even call it criticism. It’s a legitimate issue and a legitimate fix. That’s not criticism; that’s just called “software engineering.” Now, had they submitted a pull request with a clearer instruction, that would truly be the bazaar functioning as intended.
- deleted 5y ago[deleted]