3 ms·
Ah, first I thought this was about TonicDev, didn't recognize Tonic and part of Stripe didn't make sense. Then it turned out to be what I thought anyways. Good
by diggan 10y ago
Ah, first I thought this was about TonicDev, didn't recognize Tonic and part of Stripe didn't make sense. Then it turned out to be what I thought anyways. Good to hear news from you, I think the idea is amazing and it's easy to write explanations with RunKit.
I have two questions for you.
1) Offline mode, please! I've opened the feedback on uservoice at October 27, 2015 (https://tonicdev.uservoice.com/forums/273722-general/suggestions/10407894-running-tonicdev-locally https://tonicdev.uservoice.com/forums/273722-general/suggest...), there should be some self-hosted version for us to use. Which kind of leads me to what I think is blocking the offline mode
2) module-fs < is this planned to open source at one point? Sounds like a interesting solution, what I've done before is to hook up require to be async and then download the packages when they are being used, but not very friendly
- tolmasky 10y agoHi diggan, Offline mode is an interesting problem. For example, module-fs is 1 part code, 99 parts infrastructure really. We have 3.5TB of installed packages, stored internally in a content-addressable way, and then exposed as a file system through FUSE. module-fs seems to be something that only becomes powerful when you have ALL packages, thus really having similar performance characteristics of having already installed the packages. The solutions I've seen that try to download packages in the background, etc. don't quite provide this magical "I only need to require it" feeling. Its similar to the issue we have with providing real time-traveling locally: in my experience "time-traveling" has never taken off because its eternally stuck in demo-mode, as all code eventually interacts with the outside world. By snapshotting the entire computer, I think we've pushed this feature over the edge to the point that people use it without realizing it on RunKit, it is of course natural that going back in a REPL also goes back to a previous state. But locally, this feature once again doesn't seem to immediately make sense. At that point the question becomes what part of RunKit would we offer locally? Just the object viewers? I ask this non-rhetorically btw, I am happy to hear what you imagine a "local" RunKit to look like, and if it makes sense we'd certainly consider pursuing it.