4 ms·

>Whatever benefit you think this is going to bring when it's done, why not prototype that now? The biggest benefit is removing the need for a configured, physi

>Whatever benefit you think this is going to bring when it's done, why not prototype that now? The biggest benefit is removing the need for a configured, physically accesible, machine in order to do your work. Imagine visiting the parents for a weekend and being able to fix a small but urgent bug and do a commit using either something you have with you (like your webkit-based device) or what they have there (low-powered machine). Using a browser seems the most natural.

hesitz 16y ago
Don't the various methods of attaching to a remote desktop work well enough? I sometimes work in an IDE remotely on Windows using the native RDC or just VNC. Works great, smooth and fast, I would be happy to work that way for a couple of days if I was without my own machine. I don't see a big upside to sinking huge time and effort into a Web IDE when remote desktops fill most of the important use cases. Also, how many developers are you thinking will be sharing the server using a Web IDE? For any compiled language I see compilation steps as big CPU hogs, severely limiting shared usage. Even with interpreted languages I suspect there would be CPU-sharing problems. Again, remote desktop seems a better solution.