Live data from Hacker News

Facebook PathPicker

facebook.github.io

81–90 of 168 posts

Re: Facebook PathPicker

#81
post #4

This reminds me of https://github.com/mooz/percol

Percol was actually a source of inspiration as well, but I got tired of typing things like: git checkout $(git branch | percol) Since I had to almost compose my command beforehand rather than decide once I saw the output. So we take the opposite approach. Great UI though!

Does fpp support history for its command prompt? With the percol approach, you can easily re-run the same command with a different selection.

Re: Facebook PathPicker

#82
post #38

Earlier quoted context omitted.

If it's pure python why not use pip?

@rmc we have a dependency on a bash script as well, since we need to redirect stdin to tty input and such. So getting the bash file to distribute with PIP and symlink as well was slightly complicated. I only recently realized that the entire program could be ported over to python (the stdin redirection is supported in python as well) but I still think homebrew is slightly more popular than having pip installed, espec…

pip would probably be a lot better from a cross-platform perspective then something really obscure like linuxbrew.

Re: Facebook PathPicker

#83
post #80

Haven't we learned by now, my fellow HN readers? All of Facebook's open source "gifts" are patent Trojan horses. Go take a look at their PATENTS file before going anywhere near this stuff. The fact that Facebook, at such a level of wealth and success, gets away with this stuff is despicable. It's also an insult to the great legacy of companies like Sun, which gave freely without strangling its beneficiaries. It says…

False. They fixed it about a month ago.

>Notwithstanding the foregoing, if Facebook or any of its subsidiaries or corporate affiliates files a lawsuit alleging patent infringement against you in the first instance, and you respond by filing a patent infringement counterclaim in that lawsuit against that party that is unrelated to the Software, the license granted hereunder will not terminate under section (i) of this paragraph due to such counterclaim.

Source: https://github.com/facebook/PathPicker/blob/master/PATENTS

See also the announcement of the change: https://news.ycombinator.com/item?id=9356508

Re: Facebook PathPicker

#84
post #80

Haven't we learned by now, my fellow HN readers? All of Facebook's open source "gifts" are patent Trojan horses. Go take a look at their PATENTS file before going anywhere near this stuff. The fact that Facebook, at such a level of wealth and success, gets away with this stuff is despicable. It's also an insult to the great legacy of companies like Sun, which gave freely without strangling its beneficiaries. It says…

What is a patent Trojan horse? I just read the PATENTS file, but cannot think of a scenario that could affect me negatively. Can you give one?

Re: Facebook PathPicker

#85
I have a similar workflow already that may be of use to vim users. I pipe file lists (from grep etc) into vim (using a '-' to tell vim to read from stdin):

  grep -nri searchterm * | vim - 
You can then use 'gF' over a file name to open the file in question (and be taken to the right line number if specified in the form somefile.txt:42). You can use 'gF' to open the file in a new tab, or 'F' to open the file in a split instead.

As an added bonus you can re-filter the file list from within vim to, for example, remove things from a test directory without having to run the original command again:

  :%!grep -v ^test

Re: Facebook PathPicker

#87
post #76

Dozens of cool utilities like this are created every week and launched at Show HN, but without "Facebook" in their names you need at least 10 of them to get the many points this thread has gathered.

Same goes for Google, but you could argue that it's for a reason. FB/Google have a reputation to uphold and they strive to make sure their name isn't associated with subpar stuff. Plus, they have a lot of brilliant developers to work on this stuff. In the end of the day, it's largely about knowing which of these cool utilities have a better chance of being usable and well thought-out, as nobody wants to spend time on figuring out a utility which turns out to be unusable.

Re: Facebook PathPicker

#88
post #25

Some people, when confronted with a command line problem, think "I know, I'll use my mouse." Now they have two problems. I'm joking, and this looks neat, but the optimal solution is almost certainly to keep your hands on the keyboard while in the shell.

Couldn't agree more staunch! I silently weep every time I have to use the mouse during development

Just turn that frown upside down. Use your mouse for all input and get rid of that pesky keyboard.

Re: Facebook PathPicker

#89
post #38

Earlier quoted context omitted.

@andyl We are working on getting a linuxbrew recipe working. There's shouldn't be anything blocking this from working on linux systems (assuming Python 2.7 is installed). In the meantime you can try the manual installation method listed in the README: https://github.com/facebook/pathpicker/ @itsbits Why do you say that? curious if you found anything

If it's pure python why not use pip?

If it works on Linux, why not use linuxbrew?

Re: Facebook PathPicker

#90
post #84
post #80

Haven't we learned by now, my fellow HN readers? All of Facebook's open source "gifts" are patent Trojan horses. Go take a look at their PATENTS file before going anywhere near this stuff. The fact that Facebook, at such a level of wealth and success, gets away with this stuff is despicable. It's also an insult to the great legacy of companies like Sun, which gave freely without strangling its beneficiaries. It says…

What is a patent Trojan horse? I just read the PATENTS file, but cannot think of a scenario that could affect me negatively. Can you give one?

(IANAL, I did complain here about the old patents file)

An older version of their patents file used language that suggested to some that the license would be void if you attempted to defend against a patent suit from Facebook and it could therefore be dangerous to use.

They recently updated the file to clarify some terms, particularly the one the parent is complaining about, and I haven't heard anybody complaining about the new language.

Post reply on HN