That would imply it is written for PowerShell specifically ([1]), and would come with several expectations (like returning PSObject objects, and other good practices).
My guess is parsability. It’s easier to look for sentinel ``` blocks as opposed to building an HTML processor. An XML processor would have been easier, but people like Markdown. So, here we are.
Is that an issue? There’s only one reasonable implementation of Typst too, and both AsciiDoc and Typst are fully supported by Pandoc, which supports a wide selection of writers (output formats).
I would phrase that as what Tailscale does that is more convenient than wg. If you “barely know what a subnet is” go for it. wg is easy as pie though, and just don’t maintain 90 tunnels… You don’t need a full mesh. An extra hop or two, especially within a lan, won’t hurt.
I would recommend WireGuard as well, I primarily use it with Tailscale as backup. WG is straightforward to set up, and with LLM the knowledge gap is now nothing if you have trouble with it
The slow enshittification of every product touched by LLMs these last few years (ESPECIALLY by Microsoft, who goes all-in) kind of “disproves” your point.
Reliable agent-coded development only seems to work for small codebases. (And it’s amazing in Ruby for some reasons.)
reply