在F＃开发ASP.NET和ASP.NET MVC应用程序的缺点？ [英] Drawbacks of developing ASP.NET and ASP.NET MVC apps in F#?

问题描述

我想尝试在F＃中的开发ASP.NET和ASP.NET MVC应用。我喜欢用汉语语言功能，并且我的脑海功能模式适合使用HTTP和网络不是命令式编程（当然F＃都可以做）。

I would like to try developing ASP.NET and ASP.NET MVC apps in F#. I enjoy using functional langauges, and to my mind the functional paradigm fits better with HTTP and the web than imperative programming (though of course F# can do both).

我只打算在试图F＃的一些个人项目，但我希望最终F＃将被视为C＃一个有效的替代合适的商业ASP.NET项目。

I am only intending on trying F# for some personal projects, though I hope that eventually F# will be seen as a valid alternative to C# for suitable commercial ASP.NET projects.

什么缺陷和粗糙的边缘在那里目前使用F＃与ASP.NET？一个明显的缺点是，F＃是要比C＃比较晦涩，所以有少code样品和F＃有经验的程序员。

What pitfalls and rough edges are there currently for using F# with ASP.NET? One obvious disadvantage is that F# is much more obscure than C#, so there are less code samples and experienced programmers for F#.

我应该知道的？还有哪些潜在的问题

推荐答案

我个人是F＃的忠实粉丝。我NDjango解析器/渲染引擎是写在F＃。

Personally I am a big fan of F#. My NDjango parser/rendering engine is written in F#.

但尝试做在F＃中的一切是很困难的。要添加到您的这是现在还没有的事情列表：

But trying to do everything in F# can be difficult. To add to your list of the things which are not there yet:

• 有对视觉不支持
  设计师 - 既不web表单，也不
  的WinForms。你可以写的
  适当的code手动，当然

• There is no support for visual designers - neither webforms nor winforms. You can write the appropriate code manually, of course

没有code完成

在调试F＃是一个挑战，特别是因为匿名封锁

Debugging in F# can be a challenge, in particular because of anonymous closures

编译器诊断可以，因为类型推断的是误导 - 一个错字可以在很远的地方产生深远的影响

Compiler Diagnostics can be misleading because of type inference - one typo can have profound impact in far away places

我最大的忌讳就是文件顺序事'的规则。你必须指定在该文件将被编译的顺序

My biggest pet peeve is the 'file order matter' rule. You have to specify the order in which the files will be compiled

绝不这是一个完整的清单。在另一端有人可能希望，部分观点将在最终版本中得到解决。

By no means this is a complete list. On the other end one might hope that some of these points will be addressed in final release.

尽管所有列出的（及非上市）的问题我在F＃中享受编程 - 有时它给出了编码一个很清爽的角度来看，我已经使用了一些由F＃在我的C＃code启发的招数开始。

Despite of all of the listed (and unlisted) problems I enjoy programming in F# - sometimes it gives a very refreshing perspective on the coding and I already started using some of the tricks inspired by F# in my C# code.

只是不要去疯了。

这篇关于在F＃开发ASP.NET和ASP.NET MVC应用程序的缺点？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！