blocks|key|343576|text|我认为web更难，你必须担心状态，网络，并更多地关注加载，安全性等等。关于浏览器兼容性，AJax，CSS+arrghhh的噩梦呢？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|343577|OTOH因为桌面的边界更少，也许在设计上更明智，但当你拥有更多的功能时，它就会稍微困难一点--尽管我不同意这一点。|343578|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I reckon web is harder, you have to worry about state, network, and pay more attention to things like loading, security the list goes on. How about the nightmare which is browser compatibilty, AJax, CSS arrghhh.

OTOH Because the desktop has less boundaries maybe design wise it is slightly harder as you have more capabilities - I don't agree with that though.

blocks|key|3329477|text|我认为每个人都有自己的巨大复杂性，这使得他们面临着独特的挑战，根据你问的是谁，你会得到不同的答案。Web程序员可能认为桌面应用程序比web项目更难，这仅仅是因为他们不熟悉媒体。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3329478|桌面用户可能会发现web应用更难编码，因为他们必须考虑更多的CSS设计问题和使用AJAX协议的通信。|3329479|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I think that each has their own massive complications that make them unique challenges and you will get a different answer based upon who you ask. Web programmers may think that desktop applications are harder than web projects simply due to unfamiliarity with the medium. 

Desktop people may find that web apps are much harder to code for because they have to take into account a lot more design issues with CSS and communication using AJAX protocols.

blocks|key|342106|text|我非常怀疑web程序员是否需要了解winapi.I。我说GUI编程需要更多的时间来学习。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|342107|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I highly doubt web programmers need to know the winapi.I say GUI programming takes more time to be learnt.

blocks|key|3329489|text|根据我的经验，Web开发比较困难，你不能轻松地维护状态；另外，你还必须处理格式化问题(css很棒，但很难掌握)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3329490|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Web development is harder in my experience, you don't have the luxury of maintaining state easily; plus you have to deal with the formatting issues (css is great but it is hard to master).

blocks|key|3116815|text|我的网页开发是更多的stressfull...you必须与Internet+Explorer的不遵守标准，缓慢的连接，奇怪的css行为，浏览器漏洞作斗争。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3116816|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

IMHO Web Develoment is more stressfull...you must fight with Internet Explorer non compliance to the standard, slow connection, strange css behavior, browser exploit.

blocks|key|3329511|text|使用桌面应用程序，您不必像在web上那样处理诸如应用程序状态之类的问题。HTTP是一种无状态协议，因此开发人员的工作是确定如何为用户会话维护应用程序的当前状态。台式机可以使用TCP/IP并保持与服务器的连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3329512|使用web，很容易创建一个引人注目的用户界面，因为您可以使用Javascript、Flash等添加动画。当应用程序是以数据为中心的，并且应用程序状态是一个问题时，开发人员需要做更多的工作。|3329513|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

With desktop applications you do not have to deal with issues such as application state in the same way you do on the web. HTTP is a stateless protocol, so it's the developer's job to identify how to maintain the current state of the application for the user's session. A desktop can can use TCP/IP and maintain a connection to a server.

With the web, it is very easy to create a compelling user interface, as you can add animations with Javascript, Flash, etc. It is more work for the developer when the application is data centric, and application state is an issue.

blocks|key|3329523|text|我在日常工作中既要做这两件事，也可以诚实地说，开发桌面应用程序的唯一有效原因是因为用户不会一直保持连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3329524|分发/维护桌面应用程序的问题总是依赖于用户，而web应用程序可以在没有任何用户参与的情况下进行调试。这永远不应该最小化，因为它可能会花费大量的时间来调试一个爱达荷州的用户没有其他用户的缺陷。|3329525|两者的发展采取了不同的心态。Web本质上是无状态的，而桌面是全状态的。当在两者之间切换时，我经常感到沮丧，因为我习惯了其中一个，然后在另一个中尝试相同的模式/技术，但它失败了。|3329526|归根结底，这取决于您试图解决的问题。如果你不能建立一个网络服务器，那么你的选择是有限的。如果你想让用户在西弗吉尼亚使用它，那么你几乎没有什么选择。|3329527|问题中的更多信息将有所帮助，因为这个问题几乎太广泛了，无法涵盖。|3329528|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I get to work on both in my day job and can honestly say the only valid reason to develop a desktop app is because the user is not going to be connected at all times. 

Distributing/maintaining a desktop app has problems that are always dependent on the user while a web app can be debugged without any involvement from the user. This should never be minimized as it can take an inordinate amount of time to debug a defect that one user in Idaho has that no other user has.

Development on the two takes a different mentality. Web is stateless by nature and desktop is statefull. When switching between the two I often get frustrated because I get use to one then try the same pattern/technique in the other and it fails.

Ultimately it depends on the problem you are trying to solve. If you can't stand up a web server then your options are limited. If you want users to use it in the wiles of West Virginia then you have few choices. 

More information in the question would help as this question is almost too broad to cover.

blocks|key|3329550|text|哇，我对到目前为止的答案感到惊讶。这两个我都做过了，过去是桌面版，现在几乎都是web版。我发现web开发更容易开发，更容易支持，也更容易部署和部署。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3329551|我永远不会选择在桌面上开发一些东西，如果有任何可能性可以在web上进行开发的话。|3329552|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Wow, I am surprised at the answers so far. I've done both, desktop in the past and almost all web now. I find web development much easier to develop, much easier to support and much much easier to rollout and deploy.

I would never choose to develop something on the desktop if there was any possibility of doing it on the web instead.

blocks|key|344523|text|大多数时候，开发web应用程序要容易得多，并且使得部署和推出新版本的一个大问题消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|344524|你不必处理不同的操作系统版本、安装库、注册表、COM等。你有不同的浏览器要处理，但这不是一笔交易。|344525|我无法想象每个月将桌面应用程序部署到2-300万个客户端--这在网站上工作得很好。|344526|就web开发的开发而言，您有：|344527|344528|更短的执行路径|unordered-list-item|344529|更少的状态要管理|344530|，您几乎不必自己处理并行性|344531|要管理的资源少得多或没有资源-无操作系统处理|344532|<|344533|>F29>|344534|344535|唯一的缺点是，它通常需要更多的时间来设置开发机器，并且web应用程序的调试更难。在目前的工具状态下，调试不再是什么大问题。|344536|所以，如果可能的话，总是更喜欢web+app。|344537|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|18|8|@]|9|@]|A|$]]|$1|N|3|O|5|K|7|19|8|@]|9|@]|A|$]]|$1|P|3|Q|5|K|7|1A|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1B|8|@]|9|@]|A|$]]|$1|T|3|U|5|K|7|1C|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1F|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|11|$]]

Most of the time developing web apps is a lot easier and makes one of the big problems - deployment and roll out of new versions, disappear.

You don't have to deal with different operation system versions, installed libraries, registry, COM, etc. You have different browsers to deal with, but it a lot less of a deal.

I can't imagine deploying desktop application to 2-3 Millions of clients every month - something that is working fine with web sites.

As far as development goes with web development you have :

<ul>
<li>shorter execution paths </li>
<li>less state to manage</li>
<li>you hardly have to deal with parallelism yourself</li>
<li>a lot less or none resources to manage - no OS handles </li>
</ul>

The only disadvantage is that it usually takes more to setup development machine and debugging of web apps was harder. With the current state of tools the debugging isn't that much of a problem any more.

So always prefer web app if it possible.

blocks|key|3329638|text|桌面应用程序是未来的发展方向。当前的web技术(HTML、Javascript、HTTP等)在设计时从未考虑过应用程序。它是为文档而设计的。你会感觉到你写的每一行代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3329639|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Desktop apps are the way to go. The current web technology (HTML, Javascript, HTTP, ...) was never designed with applications in mind. It was designed for documents. And you feel that with every line of code you write.

blocks|key|3117036|text|这两种应用程序都有优点和缺点。例如，web应用程序可能需要考虑不同的浏览器，并且在web中获得可用的UI比在windows窗体中更难。然而，web应用程序也有一些优势。首先想到的是部署，不需要担心不同的平台(只是不同的浏览器-是的，为不同的平台开发比为不同的浏览器开发更难)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3117037|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Both kind of apps have advantages and disadvantages. for instance, web apps might need to take different browsers into consideration and getting a usable UI is harder in web than in windows forms. However, web apps do have some advantages too. the first one that pops to mind is deployment and no need to worry about different platforms (just different browsers - yes, it's harder to develop for different platforms than for different browsers).

blocks|key|3329674|text|大多数答案(至少到目前为止)似乎都集中在实现选择的难易程度上。应用程序的整个目标，无论是基于桌面还是基于web，都是为了服务于最终用户。这必须是讨论的起点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3329675|在大多数情况下，Web应用程序无法提供像桌面应用程序那样丰富和交互的体验。由于可用的小部件、网络延迟、应用程序窗口必须(通常)存在于另一个应用程序中等原因，存在太多的限制。|3329676|也就是说，很多时候界面不需要大量的小部件，网络延迟不是什么大问题，在浏览器窗口中运行是一个优势。gmail和stack+overflow是基于web的应用程序的主要例子，它们不需要特别丰富的界面。|3329677|因此，在决定使用哪种技术时，首先要考虑用户。他们是否需要高性能、丰富的UI？他们需要能够毫不费力地通过网络与其他人共享他们的数据吗？这是一个他们一天使用8个小时的应用程序，还是只是随意使用？他们将主要使用它来编辑本地文件还是与网络中的人进行协作？|3329678|对于那些说"web应用总是更好“的人，让我问你这个问题:想想你每天使用的工具。你的文本编辑器、编程IDE、浏览器、电子邮件客户端。其中哪些是web应用程序？可能没有，也许除了你的电子邮件客户端。这就是为什么你不想要一个基于web的IDE来编写软件(或者写一本书，或者做严肃的图像处理)的原因。|3329679|这一切都归结于用户和他们的目标是什么。有时基于web的UI最能满足他们的需求，有时则是桌面UI。有时这两个都行。当然，您还需要权衡选项，如分发和更新、跨平台可用性等，但这一切都是从用户及其目标开始的。如果你专注于满足你的最终用户，答案可能会变得相当明显。|3329680|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Most of the answers (so far, anyway) seem to focus on how easy or hard the choice will be to implement. The whole goal of an application, desktop or web based alike, is to serve the end user. That must be the starting point of the discussion.

Web apps simply cannot provide as rich and interactive experience as a desktop app in most cases. There are just too many limitations due to available widgets, network latency, the fact your app window must (typically) live within another application and so on.

That being said, many times interfaces don't need a large set of widgets, network latency isn't much of an issue, and running from within a browser window is an advantage. gmail and stack overflow are prime examples of web based apps that don't need a particularly rich interface.

So, when trying to decide which technology to use first consider the user. Do they need a high performance, rich UI? Do they need to be able to effortlessly share their data with others across the net? Is this an app they'll use eight hours a day or on just a casual basis? Will they use it mostly to edit local files or to collaborate with people across a network?

For those who say "web apps are always better", let me ask you this question: think about the tools you use every day. Your text editor, programming IDE, your browser, your email client. Which of those are web apps? Probably none, except for maybe your email client. There's a reason why you wouldn't want a web-based IDE for writing software (or writing a book, or doing serious image manipulation). 

It all boils down to the user and what their goals are. Sometimes their needs are best met with a web based UI, sometimes with a desktop UI. Sometimes either will do. Of course you also need to weigh options such as distribution and update, cross platform availability, etc. but it all starts with the user and their goals. If you are focused on satisfying your end user the answer will likely become fairly obvious.

blocks|key|342246|text|两者之间有相当多的差异，这会带来挑战或好处。对于web应用程序：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|342247|342248|State请求没有状态，需要通过跨所有请求或cookie传递会话变量来管理。这是web应用程序中的开销，ASP.NET经常因为会话data.|unordered-list-item|offset|length|style|BOLD|342249|Centralized的巨大斑点而受到抨击-将更改推送到web应用程序就像更新服务器上的比特一样容易，而桌面应用程序则需要向所有用户推出补丁。集中化的性质也使得分析等工作变得更容易。这是一个很大的便利。我记得GMail一度在4小时内修复了一个安全漏洞。相比之下，仍然有大量易受攻击的未打补丁的windows机器退出there.|342250|Architectural+-胖服务器，瘦客户机使web应用程序平台不可知。它还有助于管理平衡……例如，根据资源的分配，可以在客户端或服务器上完成表排序、错误检查、数学计算或图形(例如在闪存的情况下)。由于有了瘦客户端，这意味着可以彻底检修服务器，而不会影响客户端。这种级别的灵活性是真正的convenient.|342251|Security+-桌面应用程序运行在可信的环境中，它们可以自由地做任何事情，因为web应用程序运行在沙箱环境中，这使得它们对客户端来说更安全。然而，web应用程序需要一些配置，因为它与证书、activex控件等on.|342252|Versioning相关-对于桌面应用程序来说，版本控制的成本要高得多。这可以追溯到更繁琐的推出更改的过程。而且，跳跃主版本号意味着通过用户升级来增加收入。在web应用程序中，版本控制主要是由开发人员自己完成的，并且更容易进行小的迭代增强。这就是为什么桌面应用程序仍然遵循瀑布式开发周期的原因，因为推出更改的成本很高，而且您必须在第一时间获得更改。桌面应用程序还具有向后兼容性的代价，例如支持Windows98、XP和Vista或支持较旧的处理器、驱动程序，因此on.|342253|Environment+-+Web应用程序在可预测的环境中运行，这也是非常方便的。IE/FF/Opera等之间存在跨浏览器开发问题，但测试和调试要比在具有不同图形处理器、防病毒软件或builds.|342254|Responsiveness的桌面系统上运行复杂应用程序容易得多-由于回发，Web应用程序的响应速度较慢，但AJAX使这变得更加容易和有趣。|342255|342256|我确信我还遗漏了许多其他要点，但这是我对web应用程序开发的偏颇答案。|342257|entityMap^0|0|0|0|5|0|0|B|0|0|D|0|0|8|0|0|A|0|0|B|0|0|E|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|12|8|@$F|13|G|14|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|15|8|@$F|16|G|17|H|I]]|9|@]|A|$]]|$1|L|3|M|5|E|7|18|8|@$F|19|G|1A|H|I]]|9|@]|A|$]]|$1|N|3|O|5|E|7|1B|8|@$F|1C|G|1D|H|I]]|9|@]|A|$]]|$1|P|3|Q|5|E|7|1E|8|@$F|1F|G|1G|H|I]]|9|@]|A|$]]|$1|R|3|S|5|E|7|1H|8|@$F|1I|G|1J|H|I]]|9|@]|A|$]]|$1|T|3|U|5|E|7|1K|8|@$F|1L|G|1M|H|I]]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1O|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|Z|$]]

There are quite a few differences between the two which create challenges or benefits. For web applications:

<ul>
<li>State - HTTP requests have no state and needs to be managed by passing session variables across all requests or cookies. This is an overhead in web applications and ASP.NET has often comes under fire for huge blobs of session data.</li>
<li>Centralized - Pushing a change to a web application is as easy as updating the bits on the server versus desktop applications where patches have to be rolled out to all users. The centralized nature also makes it easier to do analytics and such. This is a big convenience. I recall GMail at one point fixed a security holes in under 4 hours. In contrast, there are still plenty of vulnerable unpatched windows machines out there.</li>
<li>Architectural - fat server, thin clients make web apps platform agnostic. It also helps in managing balance... for example table sorting, error checking, mathematical computations or graphics (in the case of flash for example) can be done on either client or server depending on allocation of resources. Because of the thin client, it means that it is possible to completely overhaul the server without affecting impacting the client at all. This level of flexibility is really convenient.</li>
<li>Security - Desktop applications run in a trusted environment where they are free to do anything where as web applications run in a sand-boxed environment which make them inherently more secure for the client. However, web applications require some amount of configuration as it pertains to certificates, activex controls and so on.</li>
<li>Versioning - The cost of versioning is much higher for desktop applications. This goes back to the more tedious process of pushing out changes. And then again, jumping major version numbers means increased revenue by way of user upgrades. In web applications, the versioning is mostly for the developers themselves and it's much easier to do small iterative enhancements. That's the reason why desktop applications still adhere to waterfall development cycle because pushing out changes is costly and you must get it the first time. Desktop applications also have the cost of backward compatibility such as supporting Windows 98, XP and Vista or supporting older processors, drivers and so on.</li>
<li>Environment - Web applications run in a predictable environment which again is very convenient. There are cross-browser development issues between IE/FF/Opera etc but it's much easier to test and debug than say running a complex application on a desktop system with varying graphics processors, anti-virus software or builds.</li>
<li>Responsiveness - Web applications have slower responsiveness because of post-backs but AJAX has made this a whole lot easier and more fun.</li>
</ul>

I am sure there are many other points I am missing but that's my biased answer for web application development.

blocks|key|3329792|text|这完全取决于：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3329793|3329794|您需要执行哪种类型的应用程序？|ordered-list-item|3329795|3329796|还有--你叫什么web应用程序？Silverlight或Flash应用程序都可以这样做，你可以从桌面或浏览器使用它。今天的Ajax应用程序与桌面应用程序没有太大的不同，但是使用DHTML开发不太简单的东西要困难得多(即使您使用的是jQuery甚至GWT这样的框架)。|3329797|假设HTML或DHTML作为web应用程序：|3329798|我在web/ajax和桌面开发上花了很多年，我的经验也是一样的--我做过很多复杂的web应用和桌面应用。有了好的C#工具包和工具和足够的经验，我可以在相同或更短的时间内创建比web应用程序更好的桌面应用程序。但有些类型的应用程序不能作为桌面应用程序，因为需要将它们作为web应用程序来完成。|3329799|桌面开发为什么更简单的原因：|offset|length|style|BOLD|3329800|RAD语言类型安全，代码hints|3329801|Performance+of+code+x10-1000+%2B+performance+profilers|unordered-list-item|3329802|
|3329803|3329804|3329805|无需使用堆栈跟踪、编辑和browsers|3329806|3329807|Informative检查所有堆栈异常中的所有内容即可使用多线程(如果您知道如何使用它)|3329808|3329809|3329810|3329811|整体可预测性和代码稳定性|3329812|3329813|RAD+tools|3329814|
<代码>G223|3329815|在很长一段时间内，web应用程序的几个优势是：|3329816|3329817|图形用户界面框架-+HTML%2BCSS|3329818|It's用户可以更轻松地开始使用它|3329819|应用程序的内容可以通过搜索引擎|3329820|找到|3329821|现在我们都有了强大的GUI框架，比如用于WPF/Silverlight应用程序的XAML。第二点可以通过Silverlight/Flash应用程序(我将其视为桌面应用程序)来涵盖。第三种方法可以用于RIA，但需要一些努力(+ajax应用程序也是如此)。|3329822|如果你的目标是简单的东西，并且不了解现代桌面/ria开发工具和技术，这可能是开发web应用程序的另一个好理由。但正如我所说的--我希望它是简单的东西。|3329823|entityMap^0|0|0|0|0|0|0|0|B|3|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1Z|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|20|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|21|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|22|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|23|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|24|8|@$O|25|P|26|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|27|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|28|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|29|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|W|7|2A|8|@]|9|@]|A|$]]|$1|10|3|Y|5|6|7|2B|8|@]|9|@]|A|$]]|$1|11|3|12|5|W|7|2C|8|@]|9|@]|A|$]]|$1|13|3|Y|5|6|7|2D|8|@]|9|@]|A|$]]|$1|14|3|15|5|W|7|2E|8|@]|9|@]|A|$]]|$1|16|3|Y|5|6|7|2F|8|@]|9|@]|A|$]]|$1|17|3|-4|5|W|7|2G|8|@]|9|@]|A|$]]|$1|18|3|Y|5|6|7|2H|8|@]|9|@]|A|$]]|$1|19|3|1A|5|W|7|2I|8|@]|9|@]|A|$]]|$1|1B|3|Y|5|6|7|2J|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|W|7|2K|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|2L|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|2M|8|@]|9|@]|A|$]]|$1|1I|3|-4|5|6|7|2N|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|E|7|2O|8|@]|9|@]|A|$]]|$1|1L|3|1M|5|E|7|2P|8|@]|9|@]|A|$]]|$1|1N|3|1O|5|E|7|2Q|8|@]|9|@]|A|$]]|$1|1P|3|1Q|5|6|7|2R|8|@]|9|@]|A|$]]|$1|1R|3|1S|5|6|7|2S|8|@]|9|@]|A|$]]|$1|1T|3|1U|5|6|7|2T|8|@]|9|@]|A|$]]|$1|1V|3|-4|5|6|7|2U|8|@]|9|@]|A|$]]]|1W|$]]

It all depends: 

<ol>
<li>What is your developer experience?</li>
<li>What type of application you need to do?</li>
</ol>

And also - what you're calling web apps? Silverlight or Flash apps both can be done such way that you can use it from desktop or from browser. Ajax applications today not very different from desktop applications, but it's much harder to develop something not too simple with DHTML (even if you're taking frameworks like jQuery or even GWT).

Assuming HTML or DHTML as a web applications:

I've spent many years in web/ajax and desktop development and my experience is equal - I've done bunch of complex web application and desktop ones. Having good toolkit and tools for C# and enough experience I can create better desktop application than web one within same or shorter timeframe. But some type of applications CAN'T be done as desktop because it's a requirement to do them as a web apps.

Reasons why desktop development is simplier:

<ol>
<li>Language type safety, code hints</li>
<li>Performance of code x10-1000 + performance profilers</li>
<li>No need to check everything in all browsers</li>
<li>Informative exceptions with stack-trace, edit and continue</li>
<li>Ability to use multi-threading (if you know how to use it)</li>
<li>Overall predictability and stability of code</li>
<li>RAD tools</li>
</ol>

For the very long time several advantages of web apps were:

<ol>
<li>GUI Framework - HTML+CSS</li>
<li>It's easier for users to start using it</li>
<li>Content of applications can be found by search engines</li>
</ol>

Now we all have strong GUI Frameworks like XAML for WPF/Silverlight apps. Second point can be covered by Silverlight/Flash applications (which I'm treating as desktop ones). Third one can be done for RIA, but requires some effort (same applies to ajax apps).

If you're targeting something simple and don't know modern desktop/ria development tools and techniques that might be another good reason for developing web application. But as I've said - I hope it would be something simple.

I am having some issues with managers, because they believe that (intuitively) creating desktop apps is easier than creating web apps (because you have less constraints). But in my opinion, it is more difficult because of some reasons:

<ul>
<li>The literature for desktop apps is vastly smaller than for web apps</li>
<li>Coding panels and buttons is harder than using a declarative approach (HTML)</li>
<li>The stateless nature of http forces you to rethink in a request/response fashion</li>
</ul>

I'm looking for solid reasoning on GUI vs. Desktop apps. I strongly believe desktop is are harder to develop because of my experience with some toolkits, but If if someone care to respond otherwise, please feel free to fundament your reasoning.

<hr>

Edit: I recovered my original question, since someone edited it and it lost the original content. If someone chooses to edit the question, please post some meaningful comment so I can at least know why some portion was changed.

What are the benefits and challenges of developing web apps vs desktop apps?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我和经理们有一些问题，因为他们相信(直觉上)创建桌面应用程序比创建web应用程序更容易(因为你有更少的限制)。但在我看来，由于一些原因，它变得更加困难：桌面应用程序的文档比web应用程序小得多编码面板和按钮比使用声明性方法更难 http的无状态特性迫使您以请求/响应的方式重新思考我正在寻找关于GUI与桌面应用程序的坚实...

问与桌面应用相比，开发web应用的好处和挑战是什么？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问与桌面应用相比，开发web应用的好处和挑战是什么？EN