3 ms·
My team at the Node Knockout hackathon implemented an editor-agnostic version of this feature last weekend. I guess it is an idea whose time is come. https://w
by twitchard 9y ago
My team at the Node Knockout hackathon implemented an editor-agnostic version of this feature last weekend. I guess it is an idea whose time is come.
https://www.nodeknockout.com/entries/35-nodeist-colony https://www.nodeknockout.com/entries/35-nodeist-colony
For me, the editor-agnosticism is the most important feature I would want my live coding experience to have. My team uses a mixture of Vim, Sublime, Emacs, VS Code, and Atom, and we have configurations we are comfortable with. It's too bad that this seems to be happening well within the confines of each editor's ecosystem, and not by some common protocol that all editors could share.
- cbcoutinho 9y agoThe team behind this feature think that editor-agnosticism is also really important, that's why they split up this project into atom-teletype and teletype-core. AFAICT the 'core' library could be used to implement a package in any of the electron based editors.
- derefr 9y agoCould the protocol implemented by teletype-core be (easily) spoken by a non-electron editor, or is there an inherent impedance mismatch where e.g. the protocol structures its data in ways amenable to DOM manipulations of text but not to other text buffer formats?
- maxbrunsfeld 9y agoThe protocol isn't coupled to the DOM or Electron in any way. The one thing that makes it easier to implement in electron is that it uses the WebRTC standard for peer to peer connections.
- Karrot_Kream 9y agoWebRTC is a beast of a protocol to implement, and so far browsers have had the canonical implementation. There's a few C++ libraries out there, but even then it's a lacking ecosystem.