10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jonathan Allen on Oct 18, 2007
F# is a highly influential language from Microsoft Research. It is based on the ML family of languages, but also incorporates concepts from C#, LINQ, and Haskell. Running on the CLR, it can leverage any .NET library.
According to Somasegar, "[Microsoft's developer division] will be partnering with Don Syme and others in Microsoft Research to fully integrate the F# language into Visual Studio and continue innovating and evolving F#." This means F# will be treated as a first-class language on the .NET platform.
This isn't the first time Microsoft has introduced a language other than the big three, Managed C++, C#, and Visual Basic, to the .NET platform. J#, a clone of Java 1.1, and JScript.NET had compilers but limited or no Visual Studio support. More recently, IronPython and IronRuby compilers were added as open source projects. What makes F# unusual is that it is the first language to be based primarily on Functional Programming rather than some form of Object Oriented Programming. The last non-OOP language from Microsoft, aside from T-SQL, is the venerable xBase language, FoxPro.
No timeline has been set for this initial release, but it most likely will not be with Visual Studio 2008.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
SCM best practices for multiple processes, releases & distributed teams
Hate to quibble, but F# is an functional-OOPs hybrid language. It is not strictly function, as is the case with ML or Haskell. Although I can't claim I know the language yet, I am studying the subject, and I have defined standard CLR classes in F#.
Perhaps this is what you meant, but just in case. Visual FoxPro has been elegantly OOP since 1994. It is not .Net-based, i.e., it doesn't run on the CLR. There is a version being built (www.etecnologia.net) to compile into .Net, with some examples here (groups.google.com/group/vfpnet-compiler-communi...), but this is all non-Microsoft driven.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
2 comments
Watch Thread Reply