191–200 of 206 posts
Earlier quoted context omitted.
That's true, but OP did ask a question "How come...". Your answer is that the Rust ecosystem is to blame for encouraging micro-dependencies, like Node.js, and not the author. I think that's a pretty reasonable take! But it doesn't mean that there's not a problem.
Code reuse was once considered a virtue.
Earlier quoted context omitted.
You can say this about literally any criticism ever. I hate it and it blows chunks. It is the ultimate libertarian way of striking down any discussion: do not criticise, even in any small way, because it's a free market and you can just make another one, so never EVER even THINK of discussing anything. I'm not saying that there should be some kind of totalitarian regime that enforces naming, I'm simply saying that ye…
> I'm simply saying that yeah it kinda sucks that Rust devs tend towards cutesy names over ones that convey functionality. Are you using Rust? If not, why does it matter what they choose to name their libraries. This is my entire point, you're coming in as an outsider criticizing something that is clearly not a problem to Rust devs . If actual Rust developers are using them to the point where they're popular enough t…
This is exactly cultish thing about Rust, that unless someone is praising Rust, they are free to keep their mouth shut.
Congrats for getting this out! > I also wanted an excuse to learn This is the best reason ever, and not just for you: seeing your GIF I thought "could I achieve that with fzf?". Turns out, yes I can: function fcd() { local dir; while true; do # exit with ^D dir="$(ls -a1p | grep '/$' | grep -v '^./$' | fzf --height 40% --reverse --no-multi --preview 'pwd' --preview-window=up,1,border-none --no-info)" if [[ -z "${dir}…
# For fuzzy-jumping down your home directory.
# See http://richardmavis.info/fuzzy-jumping
function fcd {
cache=~/.config/home-dirs-list
if (( $# == 0 )); then
if [ -e $cache ]; then
cd "`fzf --height=10 $cache
elif [ -e $cache ]; then
cd "`cat ${cache} | grep $1 | fzf --height=10`"
else
echo "No directory cache."
cd `find $1 -type d | fzf --height=10`
fi
else
echo "Usage: fcd [DIR]|--cache"
fi
}Congrats for getting this out! > I also wanted an excuse to learn This is the best reason ever, and not just for you: seeing your GIF I thought "could I achieve that with fzf?". Turns out, yes I can: function fcd() { local dir; while true; do # exit with ^D dir="$(ls -a1p | grep '/$' | grep -v '^./$' | fzf --height 40% --reverse --no-multi --preview 'pwd' --preview-window=up,1,border-none --no-info)" if [[ -z "${dir}…
bind -x '"\C-p": cd "$(dirname "$(fd | fzf )")"'
Definitely worth to check out sdn which also serves perfectly as cd+ls replacement: https://git.janouch.name/p/sdn I also submitted few days ago here on HN: https://news.ycombinator.com/item?id=32081263
Indeed, this looks very similar! I added it to the list in the README. To compile it, I had to sudo apt-get install libacl1-dev, which was not mentioned in the instructions.
Ideally, I would provide pre-built packages from CI, of course.
Earlier quoted context omitted.
I tried to avoid bloat as much as possible, and I would argue that the non-transitive deps are pretty essential. I'l look into tweaking some features as suggested in sibling to trim it further down. But you're right that it could always be simpler, in fact I wrote tere originally in C with curses as the only dependency, and it compiles >10x faster. But there I had to manually write some (pretty certainly buggy) unico…
I wonder, have you considered D? Seems almost ideal to me for this kind of small tooling, and it's unlikely to break because of dependency version changes caused by the thirty-seventh party.
With rust you just check in your Cargo.lock file to your VCS and then the versions of your dependencies and their dependencies (etc) are pinned, so if it works now then it will always work. For dependencies on crates.io authors don’t even have the option to remove a version once it’s published.
Upgrading dependencies is an explicit operation, so you only do it when required and run your tests afterwards.
In practice I’ve had far fewer issues with dependency versions using rust than I’ve had using dynamic system libraries in the C/C++ ecosystem
Earlier quoted context omitted.
Well, that's Rust for you. They somehow think that having a boatload of dependencies with nondescript names (smawk, parking_lot_core, serde, clap - I feel like I'm having a stroke) is a feature. I'm not even joking.
The aggressive replies on this thread. holy s**t. That's what I mean when I say Rust community is toxic here https://news.ycombinator.com/item?id=32105449
For context, I totally agree that rust often ends up with more dependencies than I would like and that crate names are often super unhelpful, but I downvoted the comment.
Earlier quoted context omitted.
Standalone Python apps as binaries tend to be poorly performant, and huge (due to shipping an interpreter, stdlib, deps, etc) in my experience. Assuming you get it working at all.
I'd prefer an informative rebuttal if people disagree with nibbleshifter, because I want to learn.
Earlier quoted context omitted.
I think you were highlighting an important potential usability issue; the delay might be ok, but I still prefer a keystroke, such as enter, to confirm selection.
> The auto-cd can also be turned off with a CLI option. Which was seemingly addressed as well, no?