HNHacker News
TopNewBestAskShowJobs

dystroy

487 karma · joined May 3, 2012

Freelance Rust programmer and FOSS author.

https://dystroy.org

submissionscomments
dystroy··on Show HN: Rhit, a Nginx Log Explorer
I'm sorry but I don't understand your comment.
dystroy··on Show HN: Rhit, a Nginx Log Explorer
This is an application I made for my own use, and which already made me discover a lot of things, like the various kinds of attacks, the fact some big companies use my server as a CDN serving a JS script on a sensitive page, that some old game I had forgotten were still played, or that there were some readers for my blog...

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 ?

dystroy··on Why scientists are turning to Rust
I loved Numerical Recipes but it's the product of an old time. It was terribly useful but also in some complex parts very buggy and badly optimized.

Nowadays, a similar effort would have to be community driven, and open-source, and include the deep discussions for domain specializations.

dystroy··on Why scientists are turning to Rust
Hard to answer this question but I worked with scientists who were wasting an incredible amount of time debugging their badly designed fortran or c++ programs, or just hitting walls when they shouldn't.

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.

dystroy··on Why scientists are turning to Rust
It really depends on the problems you work on.

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.

dystroy··on Moderna Covid vaccine candidate almost 95% effective, trials show
Isn't the difference more due to tests levels and announcement precautions ? Pfizer's announced temperature looks like the one for very long term ARN storage while standard fridge for a month doesn't look like it should alter ARN much.

I'm not sure there's a real difference here.

dystroy··on Zig cc: A drop-in replacement for GCC/Clang
This makes zero sense and it's not about emotion.

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)

dystroy··on Show HN: Lapin, a Terminal Game in Rust
It's a game for kids and their parents but what might interest devs here is that it showcases a few Rust topics in a small and hopefully clear program, for example easy parallelism, (de)serialization, extensive use of types for sanity, state+transition app architecture, as well as a few higher level patterns.
dystroy··on My FOSS Story
> I don't really understand why anyone would do FOSS, beyond the ideological.

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.

dystroy··on Broot – A new way to see and navigate directory trees
I am Broot, and root, on so many computers now !

but seriously, how to install from source is clearly shown

dystroy··on Broot – A new way to see and navigate directory trees
No, I unfortunately doesn't maintain myself the brew formulas, I don't even know how those things work (I'm not a mac user).
dystroy··on Broot – A new way to see and navigate directory trees
You can very easily configure broot : https://github.com/Canop/broot/issues/24#issuecomment-572481...
dystroy··on Broot – A new way to see and navigate directory trees
There's an issue for that (it's a few hours old). This is a top priority and should be fixed before next week.
dystroy··on Broot – A new way to see and navigate directory trees
If it's only for text files, you should configure the system opening.

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...

dystroy··on Broot – A new way to see and navigate directory trees
There's one but there was a problem for fish on mac until a few minutes ago...

(I made a new release)

dystroy··on Broot – A new way to see and navigate directory trees
By default the standard file opening provided by the system is used but you can override it: https://dystroy.org/broot/documentation/tricks/#open-files-w...
dystroy··on Broot – A new way to see and navigate directory trees
There's currently no search on paths, only on filenames.
dystroy··on Broot – A new way to see and navigate directory trees
The reason I don't mention brew today is that I don't manage the formula myself and I don't check it. I'm not even sure of what it does.
dystroy··on Broot – A new way to see and navigate directory trees
You can't just respect the terminal colors because the colors you add wouldn't be readable.

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.

dystroy··on Broot – A new way to see and navigate directory trees
You can define your own shortcuts for navigation. See for example this: https://github.com/Canop/broot/issues/24#issuecomment-572481...
dystroy··on Broot – A new way to see and navigate directory trees
When devs give a link to their twitter account, their chat, etc. they certainly wouldn't mind reading a kind personal comment from time to time.
dystroy··on Broot – A new way to see and navigate directory trees
Hum... this is quite an outdated part of the documentation, sorry about that. You can do :e
dystroy··on Broot – A new way to see and navigate directory trees
You can use ctrl-p and ctrl-n. You wouldn't be the first one : https://github.com/Canop/broot/issues/24#issuecomment-572481...
dystroy··on Broot – A new way to see and navigate directory trees
The problem with using "j" to go down is that it prevents you from using "j" to filter files having a "j" in their name.
dystroy··on Broot – A new way to see and navigate directory trees
There's a brew formula, yes. You can do `brew install broot`.

I've been told that the bash file path I use on mac is wrong though: https://github.com/Canop/broot/issues/84

dystroy··on Broot – A new way to see and navigate directory trees
The sizes are cached so they should not be recomputed (if you don't hit F5 or don't do any change (like rm, cp, etc.) from broot.
dystroy··on Broot – A new way to see and navigate directory trees
It should be possible. I'll open an issue for that. edit: https://github.com/Canop/broot/issues/87
dystroy··on Broot – A new way to see and navigate directory trees
The skin is customizable. There's one that I propose for black-on-white: https://dystroy.org/broot/documentation/configuration/#white...

and I guess people more used to black-and-white could submit a better one

dystroy··on Broot – A new way to see and navigate directory trees
OK so we'll have to define another shortcut (which should already be doable with simple configuration).
dystroy··on Broot – A new way to see and navigate directory trees
It's not supposed to do the same thing. alt-enter closes vim:

* 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.

← PreviousPage 3 of 4Next →