blocks|key|3334599|text|我会在这个标签上加上主观标签;)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3334600|就我个人而言，我认为它不会成为标准，尽管它将用于非常适合它的领域。|3334601|我认为它不会成为标准，因为它最适合应用程序的某些层，但不太适合其他层，如UI。|3334602|因此，几个层的开发将继续在C#或VB中进行。从公司的角度来看，即使F#对于应用程序的某一部分来说是更好的工具，他们也会倾向于用C#或VB编写它，以保持一致性，因为他们的程序员会更熟练地使用这些语言，所以将来更容易找到新员工。|3334603|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I would add the subjective tag to that one ;)

Personally, I don't think it will become the norm although it will be used in areas where it is well suited.

I don't think it will become the norm because it is best suited to certain layers of the application, but isn't well suited to other layers like UI.

Because of this, development of several layers will continue in C# or VB. From a company's perspective, even if F# is the better tool for one part of the application, they will tend to write it in C# or VB anyway to maintain consistency, because their programmers will be more adept in those languages and so that future hires will be easier to find.

blocks|key|920467|text|这在短期内不会发生。你用命令式编程风格养育了一百万的程序员，他们需要很长一段时间才能适应。如果有的话。这是一种完全不同的思考方式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|920468|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|$]]

It won't happen anytime soon. You have a million programmers brought up with the imperative programming style and it wil take them quite a while to adjust. If ever. It's a whole different way of thinking.

blocks|key|116850|text|我怀疑这些想法会比实际的F#使用更重要……例如，我预计(特别是随着多核升级)不变的设计将在C#中蓬勃发展。但我并没有看到人们从C#转向F#。这两个我都试过了，C#+(对我来说)肯定会让事情变得更容易维护和理解。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|116851|不要忘记，对于委托和闭包的lambda，我们有很大的能力在C#中编写函数式的代码。|116852|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 suspect the ideas will take more importance than the actual F# usage... for example, I expect (especially as multi-core escalates) that immutable design will flourish in C#. But I don't see people switching from C# to F#. I've tried both, and C# definitely (for me) keeps things more maintainable and understandable.

Don't forget that with delegates, and with lambdas for closures, we have a lot of ability to write in the functional style from within C#.

blocks|key|4180339|text|大约10-15年。这大致就是任何新语言(而不仅仅是旧语言上的一抹油漆)获得吸引力所需要的。以Python和Ruby为例，它们都是在90年代早期开始的，现在才真正获得了发展势头。也有例外--+C#就是其中之一。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4180340|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|$]]

About 10-15 years. That's roughly what it takes for any new language (not just a lick of paint on an older language) to gain traction. Take for example Python and Ruby - both started in the early 90's and really only gaining momentum now. There are exceptions - C# being one.

blocks|key|925073|text|我想这要看你做什么生意了。在我的行业中，它已经达到了这一步，其中包括金融上下文中的定量分析，其中大部分涉及到编写函数。在订单处理上下文中，我认为函数式语言没有多大用处。但我可能错了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|925074|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|$]]

Depends what your business is, I guess. It's already getting there in my line, which includes quantitative analysis in a financial context, much of which involves writing functions. In an order-processing context, to pick something commonplace, I don't see much use for a functional language. But I could be wrong.

blocks|key|3334677|text|我认为人们已经看到了它的某些原则的价值。人们不得不开始在标准过程语言中使用OOP范例很长一段时间，然后才有了基于这个概念构建的语言变得流行起来。即使在那时，人们也编写了一些不太理想的OOP代码；因此，现在有无数关于这个主题的书籍、模式和最佳实践。我可以看到函数式编程也出现了类似的趋势。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3334678|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 think already people are seeing value in certain principles of it. People had to start using an OOP paradigm in standard procedural languages for a long time before languages built with that concept in mind became popular. Even then, people wrote some less-than-optimal OOP code; hence the zillions of books, patterns, and best practices on the subject now. I could see a similar trend emerging with functional programming.

blocks|key|4180359|text|我希望的不是推动F#接管任何其他.net语言，而是他们会为VS2010添加功能，让您在同一项目中拥有多种编程语言。据我所知，你今天不能这么做，但我可能错了。这将很容易让人们拥有一个F#文件，用于他们需要的某一方面，然后C#或VB用于其他方面(UI逻辑、状态等)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4180360|人们一直把F#当作一门革命性的新语言……它唯一的革命性是它是一种构建在.NET之上的函数式语言，所以仅仅因为它是新的，并不意味着它将成为标准。看看Erlang和Haskell..。它们都是函数式语言，都已经存在了大约20年，而且都没有在大学之外得到广泛的接受。|4180361|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|$]]

What i hope for is rather than pushing for F# to take over any other .net language, that they would add the ability to VS2010 for you to have multiple programming languages in the same project. As far as I know you can't do that today, but I could be wrong. This would easily allow people to have a F# file for one aspect of a thing they need, and then C# or VB for the rest (UI logic, state, etc). 

And people keep treating F# as if it's a revolutionary new language... the only thing revolutionary about it is that it is a functional language built on .NET. so just because it's new, that doesn't mean it's going to become the norm. Look at Erlang and Haskell... they're both functional languages that have been around for about 2 decades each, and neither has reached mass acceptance outside of universities.

With the recent news about F# being included with Visual Studio 2010, I got to thinking ... how soon before I see functional programming take hold in the usual "line of business app" space?

How long before the line of business app in F# becomes the norm?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

随着最近关于F#包含在Visual Studio2010中的新闻，我开始思考...我要多久才能看到函数式编程在通常的“业务线应用程序”领域站稳脚跟？

问F#中的业务线应用程序要多久才能成为标准？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问F#中的业务线应用程序要多久才能成为标准？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问F#中的业务线应用程序要多久才能成为标准？
EN