Earlier quoted context omitted.
Indeed, Python would be a good language to implement this in terms of ease of development, but it's very difficult to distribute a standalone binary (which I wanted to do). The built-in curses support of Python is also not cross-platform I think.
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.
Show HN: tere – A Faster Alternative to cd+ls
171–180 of 206 posts
Re: Show HN: tere – A Faster Alternative to cd+ls
#172Earlier 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
Re: Show HN: tere – A Faster Alternative to cd+ls
#173Earlier quoted context omitted.
Atrocious but exceptionally battle-tested?
It was the best option a long while ago, and basically resulted in a kind of vendor lock in of sorts. Musl is far superior as a libc, but most Linux software is written for glibc and has quirks that make porting hard.
Nope. It’s better at some things but with so many caveats that this is just dumb to claim.
Re: Show HN: tere – A Faster Alternative to cd+ls
#174Earlier quoted context omitted.
You're saying it's "a common term", but I'd literally never heard it before a Rust library with this exact name appeared. Isn't this by any chance circular reasoning? That it became "a common term" because of this library? In that case you couldn't justify the name of the library by saying that it was "a common term" at that time.
I can assure you this Rust library did not invent the term https://trends.google.com/trends/explore?date=all&geo=US&q=s...
Re: Show HN: tere – A Faster Alternative to cd+ls
#175Earlier quoted context omitted.
To be fair most of those newbies are probably writing scripts that use relative directories so they require them being run in the same directory. Newbies tend to reinforce bad habits like that which makes it harder to break out of those ruts.
(cd ./some/path; ./script.sh)
cd "$(dirname $0)"Re: Show HN: tere – A Faster Alternative to cd+ls
#176Good to see the idea getting more traction!
Re: Show HN: tere – A Faster Alternative to cd+ls
#177I strongly dislike the idea of automatically jumping into a folder when there’s only one match: it feels like a feature optimised for very slow typers that actively penalises fast typers, because it makes things generally unpredictable: will one character be enough to navigate, or two, or three? It depends on the siblings, and if you type more characters than are required, you will be penalised by ending up somewhere…
I think you're underestimating how efficient your brain can get at guesstimating how many characters are required to navigate to a directory, especially when the directory structure is familiar (at which point I virtually never overshoot).
And, I still find value in this feature despite being a fast typist (90 WPM).
Re: Show HN: tere – A Faster Alternative to cd+ls
#178Reminds me a bit of Helm mode in Emacs, nice!
Re: Show HN: tere – A Faster Alternative to cd+ls
#179Looks like Emacs built-in dired, except, that it is not integrated into Emacs.
Re: Show HN: tere – A Faster Alternative to cd+ls
#180Earlier 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.