基于云/基于 Web 的 IDE 的优点/缺点是什么？
我在拉斯维加斯举办 DevConnections 时写下这篇文章。 Visual Studio 2010 已经发布，我现在已经将这个 3GB 的巨兽安装到我的机器上。 （我承认，它有一些不错的功能。）
然而，虽然安装垄断了我的计算机资源，但我开始希望我的 IDE 更像 Google 文档（即时可用、随处可用、易于共享、易于协作、自然版本化）。
一些 Google（和 StackOverflow）搜索让我找到：
我很清楚这些 IDE 缺少 VS 2010 中存在的许多功能。但是，这不是我的问题。相反，我想知道基于 Web 的 IDE 可能有什么好处？假设一家公司投入时间来创建缺失的功能，那么有什么缺点呢？
I'm writing this as DevConnections in Las Vegas is happening. Visual Studio 2010 has been released and I now have this 3GB beast installed to my machine. (I'll admit, it has some nice features.)
However, while the install was monopolizing my computer's resources I began to wish that my IDE worked more like Google Documents (instantly available, available anywhere, easy to share, easy to collaborate, naturally versioned).
A few Google (and StackOverflow) searches led me to :
I'm well aware that these IDE's are missing a lot of what exists in VS 2010. However, that isn't my question. Instead, I'm wondering what benefits a web-based IDE might have? Assuming a company invests the time to create the missing features, what is the downside?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
优点：
缺点：
正如您所看到的，它的许多好处也是潜在的缺点。所以我认为基于浏览器的 IDE 的使用非常依赖于项目。
然而，恕我直言，我认为基于浏览器的 IDE 没有足够的功能或提供足够的必要服务来取代大多数现代企业中的桌面 IDE。
Benefits:
Drawbacks:
As you can see, many of its benefits are also potential drawbacks. So I think the use of a browser-based IDE is very project dependent.
However, IMHO, I don't think browser-based IDEs have enough features or provide enough necessary services to replace desktop IDEs in most modern enterprises.
只是在这里做魔鬼倡导者并列出缺点：
断开连接！
事实上，您并不真正拥有任何软件 - 如果您停止支付每月账单，您将无法再访问它，但您可以在首次付款后继续使用离线安装的产品。
大型/有价值的项目可能会因为没有将源代码隐藏在他们控制的网络中而感到不舒服——一个被黑的帐户和他们的主要 IP 都在网络上。
有限的扩展生态系统 - 对于在线服务，通常可以对其进行控制，例如 Facebook，但没有人告诉 resharper 他们可以包含哪些功能
强制升级 - 大公司仍在运行 .net 2.0（.net 4 刚刚推出）。他们可能行动缓慢，被迫使用最新、最好的应用程序版本对他们来说可能太快了。
暴露于错误 - 有些人有奇怪的个人规则，例如他们不接触 v1 软件。如果您始终拥有最新版本，那么您将面临生产力消耗错误的打击（安全更新与功能更新是不同的类别，但如果您运行的是桌面软件，您仍然可以隔离安全漏洞并决定自己的升级原因）
互操作性 - 也许您的应用程序可以与另一个应用程序配合使用 - 他们可能无法跟上主应用程序的发布速度，并且互操作性功能可能会滞后，而其他开发人员正在迎头赶上。
集中故障点——无法控制备份、冗余等——掌握在服务开发人员手中。
就我个人而言，我发现基于云的服务非常方便，随着时间的推移，现在我有一台笔记本电脑、一台台式机和一台工作计算机，我的朋友也有计算机，在批次之间同步数据变得很麻烦。在现阶段，我们仍在处理网络上的玩具应用程序，但希望几年后 Silverlight 能够对此产生重大影响。
Just being devils advocate here and listing the disadvantages:
Disconnection!
The fact that you don't really own any software - if you stop paying the monthly bills you can't access it any more but you can keep using offline installed products after the initial payment.
Big / valuable projects may be uncomfortable not having their source code tucked away inside a network they control - one hacked account and their main IP is out on the net.
Limited extension ecosystem - with online services there is generally a control over it like facebook for example, but nobody tells resharper what features they can include
Forced upgrade - big corporations are still running .net 2.0 (.net 4 just came out). They can be slow to move and being forced to use the latest and greatest version of the app could be a too fast a pace for them.
Exposed to bugs - some people have wierd personal rules like they dont touch v1 software. If you always have the latest version you are exposing yourself to being hit by productivity consuming errors (security updates are a different category to feature updates but still if you are running desktop software you can isolate your security exposure and decide your own reasons to upgrade)
Interoperability - perhaps your app works with another app - they might not be able to keep up with the release pace of the main app and the interoperability functionality might lag while the other developers play catch up.
Centralised point of failure - no control over backups, redundancy, etc - its in the hands of the developers of the service.
Personally I find cloud based services very convenient and as time goes on now that I have a laptop and a desktop and a work computer and my friends have computers it becomes a chore to sync data between the lot. At the current stage we are still dealing with toy apps on the web but hopefully in a few years Silverlight will put a big dent in that.
Web 的功能本质上不如本机应用程序。另外，你如何编译和测试你的代码？任何理智的网络主机都不会允许陌生人在他们的服务器上编译、运行和测试他们的代码。
The web is inheritly less featureful than a native application. Also, how do you compile and test out your code? No sane web host will let strangers compile, run, and test their code on their servers.
除了“无处不在”的可用性（注意引号）之外，您还可以获得在服务器上编辑代码的“好处”。因此，您可以跳过当今许多服务器端应用程序所需的许多部署步骤。编辑代码就像编辑博客一样简单，但它也可能是一种诅咒。您仍然需要一种将开发与生产分开的方法。
但即便如此，如果您使用博客或许多 CMS 应用程序，每天都有数百万人使用“基于 Web 的 IDES”，因此显然对特定应用程序领域具有适用性。我可以告诉你，有时我希望修复已部署应用程序上的快速错误，就像单击“编辑”按钮一样简单。
Besides "ubiquitous" availability (note the quotes), you get the "benefit" of editing code on the server. So, you get to skip many of the deployment steps that are necessary for many server side apps today. There's a simplicity of editing code like you'd edit a blog, but it can also be a curse as well. You still need a way to separate development from production.
But that said, if you use the Blog or many CMS applications, millions of folks use "Web based IDES" every day, so there's obviously applicability for specific application areas. I can tell you there are times I wish fixing a quick bug on a deployed app were as simply as clicking an "edit" button.