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.Ĭentralised point of failure - no control over backups, redundancy, etc - its in the hands of the developers of the service. 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) 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.Įxposed to bugs - some people have wierd personal rules like they dont touch v1 software. 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įorced upgrade - big corporations are still running. 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.īig / 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.
Just being devils advocate here and listing the disadvantages: 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. So I think the use of a browser-based IDE is very project dependent.
0 kommentar(er)
