487 karma · joined May 3, 2012
https://dystroy.org
I've reached a soft point where the application is very useful to me, and ergonomics are right IMO.
I have big ideas for a next version but the work could only be "justified" by other users.
And I have no idea whether this application will even find users past me and two friends.
So, HN, do you find this useful ?
Nowadays, a similar effort would have to be community driven, and open-source, and include the deep discussions for domain specializations.
So yes you can easily start hacking something in fortran or c++, and the cognitive load is probably much smaller, but then you have the risk of being eaten by your bugs, or of not working on some problems just because the tool you make is so badly designed you give up doing the necessary changes.
For my first program (task scheduling, regexes, redis, rest), everything was simple and obvious, it was made in about 3 days.
My second program was dealing with several kinds of graphs, optimal sub string addressing, and then I hit the painful points and it took me several weeks of this side project to get my head around the complex concepts of Rust, and several months to really feel at ease.
There's a subset of problems for which Rust is "easy" and it's probably possible, with some guidance and occasional help, to organize one's work around those.
I'm not sure there's a real difference here.
The language is young and you don't certify a software solution every two days or don't rewrite your nuclear power station code every day.
Very experienced programmers switched to Rust because it makes it possible to build large scale industrial programs both efficient and reliable. They won't switch to C++ just because they think they're good enough to live dangerously.
(btw I work on plant control and yes I write parts in Rust)
Two big incentives that you see in most human activities:
* build something for other people
* try to be recognized
Money is a tool to make society work, it isn't really what people live for. People inherently want to contribute to society.
but seriously, how to install from source is clearly shown
If it's for any kind of file, then you can override the Enter: https://dystroy.org/broot/documentation/tricks/#open-files-w...
More usually you define a few shortcuts for your specific needs : https://dystroy.org/broot/documentation/configuration/#verbs...
(I made a new release)
Right now the best option is to define the skin in the config file (see https://dystroy.org/broot/documentation/configuration/#white...) and I've added a new issue requesting that broot detects if a white skin seems more suitable.
I've been told that the bash file path I use on mac is wrong though: https://github.com/Canop/broot/issues/84
and I guess people more used to black-and-white could submit a better one
* on a file it opens the file (in the same terminal if possible, depending on the system file opening) * on a directory it does a cd to that directory and comes back to the terminal (if broot was launched with the br command)
I'd like Mac users to chime in and answer you now: I can't really test on mac.