3 ms·
There's a big disconnect here; if you think there's some compelling use case for having shared state in a central location, then anything that gives your centra
by jerf 16y ago
There's a big disconnect here; if you think there's some compelling use case for having shared state in a central location, then anything that gives your central service access to that shared state will meet that need. That does not mean this shared location is necessarily "the cloud", nor does it mean you "must" actually literally serve the IDE out of the cloud so it can live in the browser. That's just today's mantra, tomorrow's will be something else. You simply must have the state moved somewhere where it can be analyzed, or even simply shared P2P with no central node.
This is taking on an immense amount of pain for what sounds like gain that can be had for far cheaper in every conceivable way with a much simpler and less boil-the-ocean approach. Whatever benefit you think this is going to bring when it's done, why not prototype that now?
- fierarul 16y ago>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 agoDon'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.