Nitrous Service Shutdown – November 14th

Re:Nitrous Service Shutdown – November 14th by jlarocco on Monday October 31, 2016 @08:25PM (#12842308)

I guess I'd turn the question around and ask what problems are browser based IDEs trying to solve and what advantage do they have over regular IDEs?

I'm a full-time C++ developer, which probably isn't the target for most browser IDEs, but I'll throw in my two cents anyway.

My perception is that browser based IDEs are inflexible, fragile, slow, and don't scale. It's not even clear to me how a browser based IDE is supposed to work in my environment. Do I clone our source repo locally and open the file from there somehow? Do I clone it to the cloud somewhere? How does a browser IDE handle the third party libraries we link to? Where is compilation done? Where does the executable go? Am I able to debug and step through the binary in the browser? What if there's a GUI component?

And don't even get me started on the clunkiness of text editing in a browser compared to an editor like Emacs or Vim.

The whole concept of a browser based IDE just seems like a poorly thought out abuse of web technology.

[ Parent | on HN ]

Re:Nitrous Service Shutdown – November 14th by sytse on Monday October 31, 2016 @10:14PM (#12842856)

Good points, running the environment in the cloud and the editor locally helps with some of the points, but doing debugging is hard. As a ex ruby developer I'm used to having an editor without the other IDE functions. I guess that IDE in the cloud is a big step from editor in the cloud.

[ Parent | on HN ]