Get Rid Of Non RunMe CodePaths
Opened this issue · 0 comments
jlewi commented
I think it makes sense to go all in on RunMe.dev.
For the reasons noted in tn004_runme.md; I think RunMe.dev provides a much better frontend and UX than what Foyle is doing. So we should just reuse it.
The main thing we loose is the RunMe.Dev doesn't currently support running in vscode for web. I think it makes more sense to improve RunMe.dev to support that than trying to continue to maintain a separate stack.
There's a lot of code we can probably get rid of once we rely fully on RunMe
- Executor
- Assets Manager
- StaticServing of vscode for web
- Building vscode for web assets
- Although we might want to keep it around for testing RunMe.Dev in vscode for web