gdgghhhhh

The key is forming a team of maintainers.

I'm optimistic.

In case someone wonders why bcachefs is sadly no longer part of the mainline kernel. Start reading here: https://lwn.net/Articles/1027289/

So, they "decided" it's not a derivative and thus can be listened under MIT instead of GPL....

Oh. I was not aware of that

/proc is a Linux thing.

It's amazing how many of the "experts" here don't get that bcachefs != btrfs

Also consider putting Firefox itself into a jail. E.g. using bubblewrap on Linux: https://gist.github.com/richardweinberger/cae9edeafeec4cdf65...

FWIW, the missing source has been released.

In this context, this is worth a read: https://hachyderm.io/@josefbacik/114755106269205960

politely, yes.

I wonder how well it works with heavily nested files. AFAIU, this is a recursive parser.

The title really confused me until I realized this has nothing to do with https://millcomputing.com/ :-)

Speaking of helix, does is support vim key bindings? Last time I tried, it was kinda disappointing to be forced to learn a completely key binding set.

I wonder how the code looks, it must be a maze of "on error goto" lines to not crash at the slightest error.

The program doesn't look like a typical VB6 application, I guess the author draws all UI elements himself?

No Kent, really.

I suggest reading the whole mail thread before judging. The CoC decision was the last resort.

Don't get me wrong, OSS does not mean it will build in any random configuration on any distro. The source is there. Maybe 7zip could do better, but still...

Perf trace is also worth noting. It was much less performance overhead than strace. https://man7.org/linux/man-pages/man1/perf-trace.1.html