Avi Press

@driccio thanks for bringing this up and apologies for the difficulty. For completeness, did you encounter these issues when installing via Scarf, stack, or is this even just when pulling...

Got it, thanks for the info. This isn't surprising because both curl-runnings and scarf rely on the same haskell libraries under the hood. Sounds like we'll need to ship statically...

A model I'd like to mention is an experiment in this space that I've been working on, Scarf ([https://github.com/aviaviavi/scarf](https://github.com/aviaviavi/scarf), [https://scarf.sh](https://scarf.sh)). For now it only focuses on CLI tools, system packages,...

Thanks for pointing this out! A memory leak would not be entirely surprising, I wasn't coding particularly carefully with respect to memory. I'm not the most familiar with space leaks...

Hi @jviotti, thanks for asking! Currently there isn't anything that gets all the way to static html/css/js, but there is a (poorly documented) `--no-server` flag you can pass to toodles...

Neat idea, would certainly be easier than clicking through to the resulting source code page. I think this change would end up being moderately tricky, from complexity around tracking the...

Love the drop down idea! Specifying other keywords is also a great idea, captured separately in #8

I think I'll opt to leave this open to track the project selection aspect, I think it's a good feature to add

I like it! While I can see the benefit (and fun!) of building this into the backend, I'm thinking it might be a pre-optimization. To me it sounds easier to...

I meant the latter. The javascript that powers the web UI of toodles should be able to handle this, so I was suggesting there might not be any Haskell to...