Explaining the value of this is hard and I guess it boils down to the convenience of accessing everything via an URL. Of course everything you have in a browser may be done by applications talking to some server.
I'm basically hoping that an open-source cloud-based IDE will bring more to the table that just ssh x forwarding. What I've learned from a continuous integration server is that automation is important, but the test/build results are mostly separated from your IDE project -- integrating the two seems valuable.
Also, workspace configuration is a pain just as it is migrating to another machine. I'd rather just work as close to the (versioned) source code tree as possible.
It seems to me that having an offline IDE is odd when we are always connected, everything we produce goes back online (commit, emails) and we produce it usually by inspecting online resources (bugtracker, emails, google).
I'm basically hoping that an open-source cloud-based IDE will bring more to the table that just ssh x forwarding. What I've learned from a continuous integration server is that automation is important, but the test/build results are mostly separated from your IDE project -- integrating the two seems valuable.
Also, workspace configuration is a pain just as it is migrating to another machine. I'd rather just work as close to the (versioned) source code tree as possible.
It seems to me that having an offline IDE is odd when we are always connected, everything we produce goes back online (commit, emails) and we produce it usually by inspecting online resources (bugtracker, emails, google).