well there are quirks with the userland. `xdg-open` is an odd one out. Wayland is some amalgam of remote desktop instead of a normal compositor. The filesystem is case-insensitive, which is not POSIX compliant (WSL is allowed to create illegal names that Windows can't deal with; but notably, users might expect case-insensitive filesystem paths to be accepted when invoking WSL apps; but they generally aren't). webpki trust anchors are not supposed to be rooted in WSL but i have no idea if they are or if there's some cursed way to make them represent the windows trust store.
there's probably some jank about network interfaces. no way those are seamlessly managed across WSL and Windows with no compromises.
yes, WSL is just a Hyper-V guest, running real Linux kernel, next to Windows. it's not a thing running inside Windows, it's genuinely Linux. in that sense, one might say that syscalls have no quirks. it's not like the Linux part is wrong.
but the Hyper-V environment (and certainly the parts connecting it to the Windows desktop) is not alike in every way to a typical Linux distro. it very much still has quirks, just not in *kernel behavior*.
sodiboo :pride_heart:
npub1j3…ry2uc
2026-11-02 15:26:31 UTC
in reply to nevent1q…g83p
Author Public Key
npub1j3w0f8cxz6rkt7jen58z9paevv9yne883xnt0xrew5zkakelns2sxry2ucSeen on
wss://relay.momostr.pinkPublished at
2026-11-02 15:26:31 UTCEvent JSON
{
"id": "6f1f899b70585ad3b2c123755fc86767771f46498259e38edb18d5d05720a09a",
"pubkey": "945cf49f06168765fa599d0e2287b9630a49e4e789a6b7987975056edb3f9c15",
"created_at": 1793633191,
"kind": 1,
"tags": [
[
"p",
"474b2203650e801dfe61d7ea94ffc5c31e86857f00c7a3e8433b77b27858a973"
],
[
"p",
"1d839ee22f0fd3400823777c7515c454c2b14e2ebd4220bbfa39d6f4c142d770"
],
[
"e",
"1d3737d1321cea0e61cac4c08e0565c0fbc06edf7274a2e5c5d9e57a86fc9686",
"",
"root",
"474b2203650e801dfe61d7ea94ffc5c31e86857f00c7a3e8433b77b27858a973"
],
[
"content-warning",
"WSL quirks"
],
[
"e",
"baa267ce4d891a32143f2ddb798892245747fdcfddec8ee09cdb17c333800c2d",
"",
"reply",
"1d839ee22f0fd3400823777c7515c454c2b14e2ebd4220bbfa39d6f4c142d770"
],
[
"proxy",
"https://gaysex.cloud/notes/at2z7d4qaz8p002n",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://gaysex.cloud/notes/at2z7d4qaz8p002n",
"pink.momostr"
],
[
"-"
]
],
"content": "well there are quirks with the userland. `xdg-open` is an odd one out. Wayland is some amalgam of remote desktop instead of a normal compositor. The filesystem is case-insensitive, which is not POSIX compliant (WSL is allowed to create illegal names that Windows can't deal with; but notably, users might expect case-insensitive filesystem paths to be accepted when invoking WSL apps; but they generally aren't). webpki trust anchors are not supposed to be rooted in WSL but i have no idea if they are or if there's some cursed way to make them represent the windows trust store.\nthere's probably some jank about network interfaces. no way those are seamlessly managed across WSL and Windows with no compromises.\n\nyes, WSL is just a Hyper-V guest, running real Linux kernel, next to Windows. it's not a thing running inside Windows, it's genuinely Linux. in that sense, one might say that syscalls have no quirks. it's not like the Linux part is wrong.\n\nbut the Hyper-V environment (and certainly the parts connecting it to the Windows desktop) is not alike in every way to a typical Linux distro. it very much still has quirks, just not in *kernel behavior*.",
"sig": "e504844e3d4085575a01808c57c13e0bebaf03b6ae1bbe96dd5649d16473c3dce4881d06ceab901802f235a70d49cbbb02707b0bfab1975d1b5cad7035ea421b"
}