4 ms·
Oh, or we could add drive specifiers (maybe letters for ease of typing?) and then a reserved character before the root path separator to signify the change in c
by c0pium 3y ago
Oh, or we could add drive specifiers (maybe letters for ease of typing?) and then a reserved character before the root path separator to signify the change in context.
Something like c:/dir_name could really take off…
- packetlost 3y agoI find this snarky comment hilarious while also being disgusted at the implication
- bombcar 3y agowww.example.com.c:
- somat 3y agoI laughed, but wanted to acknowledge that the single tree filesystem is a pretty great invention. I like how the plan 9 ethos is "if it's a tree, it goes in the filesystem somewhere" dns.. in the filesystem. html dom? looks like a tree to me, in it goes. And I think this is the fundamental problem with the windows registry. Because it sounds like a really great idea. "A dedicated database to store all configs in" However in reality it sort of sucks. I think this is because now you have a second strange tree that has different special access methods and usage.
- c0pium 3y agoExcept that is how the registry works. Get-ChildItem -Path HKCU:\ | Select-Object Name works exactly how you think it will. https://learn.microsoft.com/en-us/powershell/scripting/samples/working-with-registry-keys?view=powershell-7.4 https://learn.microsoft.com/en-us/powershell/scripting/sampl...