I find it surprising that a filesystem feature is so tightly coupled to a specific programming language. Why is it not an API that lets you begin/commit a "channel program" from any language, then execute zfs commands within session? Surely speed of execution is not so big of a constraint.
I have a special place in my heart for these sort of "weird" features, which seem really exotic compared to the standard POSIX APIs we're all used to. I just enjoy thinking about alternatives and new ways of doing and architecting things. Even if I can't think of a practical use for such a feature, I always appreciate the novelty. It makes me wonder about the future. Are the typical POSIX-style APIs still going to be dominant 50 or 100 years from now, or will new APIs and ideas start to replace them?
> kernel operations are faster than userland operations<p>Call me a pedant but this grinds my gears. The speed my CPU will carry out instructions is not determined by if it's in a kernel or user context. Avoiding making switches between those contexts certainly means less work though.
Not to be confused with <a href="https://en.wikipedia.org/wiki/Channel_I/O#Channel_program" rel="nofollow">https://en.wikipedia.org/wiki/Channel_I/O#Channel_program</a>