4 ms·

I wouldn't because: 1. You need a lot of computing power for editors/IDEs. You want things to happen instantly, and that usually isn't the case with web-based

by edanm 16y ago

I wouldn't because: 1. You need a lot of computing power for editors/IDEs. You want things to happen instantly, and that usually isn't the case with web-based stuff. 2. Browsers haven't reached the point where you can make really great editors in them. 3. You're usually dealing with local files, and browser-based editors wouldn't do well with that (you have to have local files because there are a lot of files, you need to compile them, etc.). 4. When I sit down to program, I usually sit down on a computer I own which has a lot of very specific programs and a very specific environment. This includes, but is not limited to, the editor. I can't do web dev these days without having Firefox + Firebug installed, not to mention having Python/Django installed for most of my projects, etc. So having a web-based editor won't help me in programming on other machines anyway.

sanderjd 16y ago
Thanks for sating my curiosity! Some interesting points. 1. Not sure I agree here, I'd have to see some benchmarks of similar types of operations in local editors and javascript, but I think it should be roughly equivalent to, say, Eclipse's java-driven interface. 2. I think this is a good point, but I wonder what it is they don't yet have. "Can make really great editors in them" is a pretty vague requirement. 3. I personally think this is historical baggage. There is no reason the server hosting the editor (or another server communicated with that server) could not host your files. Hell, most open source projects are already done this way, hosted on github/sourceforge/etc. - downloading the project locally would be an unnecessary step if the code-hosters offered solid editing options. 4. This is probably the main point, to me. It's not enough to just edit through the web, because there are too many other things you need to do as well, which are even more difficult to detach from a local machine.

by edanm 16y ago

sanderjd 16y ago

Thanks for sating my curiosity! Some interesting points. 1. Not sure I agree here, I'd have to see some benchmarks of similar types of operations in local editors and javascript, but I think it should be roughly equivalent to, say, Eclipse's java-driven interface. 2. I think this is a good point, but I wonder what it is they don't yet have. "Can make really great editors in them" is a pretty vague requirement. 3. I personally think this is historical baggage. There is no reason the server hosting the editor (or another server communicated with that server) could not host your files. Hell, most open source projects are already done this way, hosted on github/sourceforge/etc. - downloading the project locally would be an unnecessary step if the code-hosters offered solid editing options. 4. This is probably the main point, to me. It's not enough to just edit through the web, because there are too many other things you need to do as well, which are even more difficult to detach from a local machine.