Heya @smith.adriane, thought I’d look at updating those docstrings. Which led me to want to see what my docstrings looked like in cljdoc. But there’s a thing or two preventing me from doing a cljdoc local preview. One thing is that we are referencing your fork of https://github.com/phronmophobic/vt via git deps. Do you think you’ll publish this to Clojars? Also… curious… are the cljs portions of vt relevant to your fork?

Oh, I can push a jar to clojars sometime today. It's not much work, so happy to just take care of it if it's blocking something.

The cljs portions don't really seem useful right now. Why do you ask?

Was just locally hacking around vt fork not being on clojars yet. And my current cljdoc error relates to cljdoc failing to eval cljs. Might not be a problem. But if cljs in vt was definitely extra cruft, was going to suggest we turf it, to avoid any extra complexity.

I guess you’ll need that vt fork up on clojars eventually anyway to be able to deploy membrane.term to clojars, yeah?

I’m in no real hurry for any of this, just toodling about.

yea, might as well

Oh and given https://blog.asciinema.org/post/smaller-faster/, we should probably reimplement everything in Rust.

I saw that. seems weird to me. It seems like the problem he's trying to solve is replay terminal sequences, increase performance, reduce payload, and avoid dependency conflicts

the way I would do that is use vt on the server side to produce a state machine that minimally does the work of transitioning between frames.

and just send that minified js file that does just that

rather than sending a full terminal emulator

and rewriting everything in rust

Yeah, well… he’s not got your brain in his head.

very true

he did have some cool demo terminal programs that would be interesting to try