Documentation Tooling

Nope, lets not drag this finished help topic down a tangent.
Moving this to a new topic.

It is easy to create a new topic and you can even link to other topics, specific posts, or copy a quote from some other topic. So please do that, instead of changing what the topic was about. (Helping somebody accomplish something specific)


I don’t really care what other languages do, you need a server running it, because browsers decided that running webassembly from a file resource is not allowed for some reason. I think that is the thing that should be questioned, if webassembly is supposed to be secure and sandboxed, then why can’t it be run from a file? That is what I find strange.

But I also don’t think it makes sense to argue about these trivial matters, unless you actually want to do something about it. Otherwise it just is pointless bike-shedding “lets do it like everyone else”, well no, lets not, the current documentation has made the implementation simpler without needing to replicate a whole bunch of logic in javascript.

If needing to run a webserver stops you from using the documentation, that seems silly.

I agree that it could be simpler to run the webserver and have it serve the documentation for a number of libraries, without repeated manual setups or having to craft customized build steps to run a browser (although if that is like 3 lines in the application it doesn’t seem that important to avoid that), but I think it is partly the community that should come up with something that smoothes out the rough edges and creates tooling for that.

The specific piece of software is a webserver, which isn’t some obscure unknown software, where you would have reasons for not wanting to run it.

1 Like