4 ms·
Totally agreed, the Monaco component is already in place and pre-dates VS Code. It raises queries about what you do after the editor is running though (i.e. wh
by headmelted 10y ago
Totally agreed, the Monaco component is already in place and pre-dates VS Code.
It raises queries about what you do after the editor is running though (i.e. where does your terminal live? What about your interpreters/compilers?).
It quickly gets to the point of looking at SSH to another box like Cloud9 does it, at which point you may as well just run Code there and remote to it.
- skybrian 10y agoNot really buying it. Sending each keystroke and paint update over the network isn't a great experience on slow networks; even just ssh has noticeable lag. (Mosh is designed to fix this, but it's not trusted in most places yet.) Being able to run the UI locally and using ssh to load/save edits to files seems like a better way to deal with latency.
- nilliams 10y agoHuh? For an editor in the browser you don't send every keystroke and paint update over the network. The UI is effectively local, you would only need to send regular network updates for 'autosave', and it wouldn't be to keystroke granularity.