he/him 
Not enough JS tools have cachable artifacts. Warm starts could be so much faster.
Show this thread
Even better if those artifacts are per-file, and contain no absolute paths. Shared caches! Critical for scaling for a large company/codebase. A cache shared between all dev machines. Not a capability you see often with open source JS tooling.
-
-
Here’s my plug: I had to think about this from the beginning with Rome. Having workers was a good constraint because all messages had to be serializable. Good boundary for thinking about these artifacts.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
https://github.com/electron-userland/electron-compile … does this, the cache is based solely on the content + the compiler options (so when you change a tsconfig setting, the cache implicitly gets thrown out)
-
I very much was thinking about Git's "Content-based" addressing when I wrote it, it's a useful pattern for compilers! Especially because it means you can sync the caches around without worrying about file paths
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.