Lind-Wasm Frontend

[rennergade]

Rick has mentioned a few times that making Lind easy/convenient to use for potential users will be very important. Currently we have a handful of scripts to compile/run/debug programs that are somewhat hard to read and a bit confusing.

I'm starting this issue to brainstorm what we might like the Lind frontend to look like and then hopefully better develop tools with the help of Rick and Matt.

[JustinCappos]

The frontend is something that the Docker, Microsoft, Google, TestifySec, etc. folks will have the clearest perspective. Let's get our backend actually working and then we can start to bug them.

[rennergade]

The frontend is something that the Docker, Microsoft, Google, TestifySec, etc. folks will have the clearest perspective. Let's get our backend actually working and then we can start to bug them.

Ok that sounds good. For now @m-hemmings is going to use this issue to post suggestions on making our tooling easier to use for our purposes.

[rickmcgeer]

Sorry to be slow on this one. I agree with @JustinCappos that getting the back end in shape first is the right call (the front end's shape is determined by the back end). But I also think that as we build (and I will do my part in this) we should make note of the issues we run into. I'm doing this NOW on another project -- as I code and test, capture the environmental assumptions and workflow steps in markdown files in the repo. I know (believe me, I'm guilty!) that it's really easy to just do stuff to get around a compile/build/workflow issue and then consign it to a memory hole. But this has bitten me a million times, so I've gotten into the habit of writing short notes about every issue I run into....something I really recommend to @m-hemmings and everyone.
And thank God for Github, which makes it easy to capture this...