3 ms·
Yeah, but they are 2 IDEs not a single IDE. You are running two copies not one copy with two instances. I then need to jump between programs to edit code.
by protomyth 8y ago
Yeah, but they are 2 IDEs not a single IDE. You are running two copies not one copy with two instances. I then need to jump between programs to edit code.
- igouy 8y agoSo when I asked "What will that let you do?", the only "benefit" you-can-think-of is the possibility of switching from editing code in visualnc64.im to editing code in quad.im without a mouse-click ?
- protomyth 8y agoSo when I asked "What will that let you do?", the only "benefit" you-can-think-of is the possibility of switching from editing code in visualnc64.im to editing code in quad.im without a mouse-click? No, that would not be enough to make anything work. What I can think of is an IDE that had access to all the VMs running and some plumbing for the VMs to communicate. I would love to be able to spin-up Smalltalk VMs so I can simulate a full system on my desk. Having separate IDEs running means I don't have any integration so I have to debug in multiple different IDEs when tracing communications. I can imagine some of the debugging and code inspection that could be extended to look at code running simultaneously in multiple VMs.
- igouy 8y agoAlready mentioned up thread — Distributed Smalltalk. "Open a debugger where you can trace the full stack on all involved machines." "Inspect objects in the debugger or open inspectors on any of the objects, regardless of the system they are running on." April 1995 Hewlett Packard Journal, Figure 7 page 90 https://www.hpl.hp.com/hpjournal/95apr/apr95a11.pdf https://www.hpl.hp.com/hpjournal/95apr/apr95a11.pdf
- protomyth 8y agoI want it all, not just debugging. Distributed Smalltalk didn't do it all in one IDE.