Jake Goulding

I have a [WIP branch](https://github.com/integer32llc/rust-playground/tree/css-modules-3) converting to CSS modules. As part of that, I plan on adding a dark mode for the whole site, and had indeed planned on using...

> Would this also convert to a dark theme for the compiler/output window It's not yet implemented, so it might vary, but that was my intent, yes. That being said,...

> put a small note somewhere mentioning new dark theme support yep, there's already support for notes like that (such as when editions were released or pointing people to the...

> How is the progress going All current progress has been reported in this issue. How would you like to help?

Yes, the ideas are fine. How do you propose to help make the ideas actual? > your WIP branch doesn't seem to exist Yes, the playground uses CSS modules now.

Maybe also use the cache information to denote if the displayed output tab(s) are out-of sync with the current code / options.

> any kind of caching today, or does all compilation start from a clean state in the Docker image Depends what "caching" encompasses. We [build all the dependencies](https://github.com/integer32llc/rust-playground/blob/master/compiler/base/Dockerfile#L67-L68) and bundle...

The idea that I've been mulling around in my head is to add a more interactive / long-running paradigm. My pie-in-the-sky thoughts: - Frontend establishes a WebSocket connection to the...

> almost as fast as normal local incremental compilation I think there's a buried assumption here that would be good to prove out first. If you write hello world locally,...

> and 7.8 seconds for a clean build: This isn't quite an accurate comparison as it's going to rebuild `textwrap` and all of its dependencies. You'll likely even see Cargo...