Post

he's based now. the operating system of the future will use a capability restricted database instead of a traditional file system

Yeah they are one of the undersung extension points of PowerShell. And I keep meaning to write an "object provider". Does this sound cool to you? CD into properties and subproperties? Invoke-item into methods?

i'm not very familiar with the internals of .net or powershell, but wouldn't that break parts of the interface like Set-Item, Remove-Item, New-Item? the idea of providers generically is nice though. i currently use nushell, but its concept of $env.PWD is somewhat coupled to a file tree

Nope, it wouldn't break them. Providers are designed to provide a file-system like experience atop of an arbitrary data store. Multiple ones run side by side. On Linux, you'll have one for filesystem, variables, environment variables, functions, and aliases.

0 reposts1 like

On Windows there's also the registry provider ( which, admittedly, works in somewhat funky ways ). If you ever have to deal with #IIS - first, I'm sorry, and second, the IIS provider is your friend. There are a few community providers as well ( but way more cmdlets )