soc

> is there a reason why JNA is not considered an option here Sadly JNA is rather big, it would turn this < 10kB library into a 3.7MB one. :-/...

@alexarchambault good work! Do you know how large the binaries turned out? I'm experimenting with an approach in [dirs-cli](https://github.com/dirs-dev/dirs-cli-rs) and end up with 30KiB (16KiB with `upx`). Though I still...

Thanks! I will read it in more detail later, just so you are aware there is some work happening in https://github.com/dirs-dev/directories-net, I was hoping to get this polished, released and...

The current approach also needs a .NET runtime, so we would not introduce a new dependency but remove the PowerShell one.

The problem is that I would need to ship and maintain native x86, amd64, arm32, arm64 dlls. The devices I own cover 0% of that.

My main concern is the ARM situation, because I think even more approaches and fallbacks on increasingly obscure platforms puts us into a situation where it gets really hard to...

Thanks for the report, @bluefireoly! Could you check whether the problem also exists on PowerShell 6? Also, the non-null paths returned in your output look weird too. What was the...

I think creating a multi-release jar might make sense, as the next release I'm targeting is the one in which Project Panama ships. Question is whether just creating the module-info.class...

Ok, great, then let's go this route. Though I would do this after I migrated to the organization (I registered `dirs.dev` earlier that I want to use instead of `soc.github.io`).

@alexarchambault Could we do this as a separate module? Such that people who only need the library can use it without dragging in CLI/parsing code? (Maybe named `directories-jvm-cli` or something?)