4 ms·
" // use .Not(), for me, is more elegant than use the '!' operator " That's like doing "#define BEGIN {" in C. I'd also make a note that if you're considering
by MichaelGG 13y ago
" // use .Not(), for me, is more elegant than use the '!' operator "
That's like doing "#define BEGIN {" in C.
I'd also make a note that if you're considering .NET, F# is a better language than C# in nearly every aspect. C#'s development is practically stagnated, at least from an outsider's point of view.
As a comparison, the F# code of his example is just:
type Student = { Age: int; Name: string }
let student = { Age = 17; Name = "Paulo Ortins" }
let PrintAdultStudent student = if student.Age > 18 then printfn "%s" student.Name
That's 176 significant chars versus 267, and as normally formatted, 3 lines versus ~9. Once you start using F#, going back to C# is just painful due to the incredible verbosity and lack of critical things like pattern matching (active patterns are amazing) and good type inference.
- pauloortins 13y agoIs possible to use F# for web applications ?
- _random_ 13y agoYes, but you have to make an effort. Quick google: http://tomasp.net/blog/fsharp-mvc-web.aspx/ http://tomasp.net/blog/fsharp-mvc-web.aspx/
- MichaelGG 13y agoSince then, F# has a full LINQ-to-SQL generator (via the Type Providers mechanism), so you don't need that part of the interop. Also, this is more of a Visual Studio/web framework issue. The VS people chose to ignore F# with their project type specifications. And the MVC people are very C# oriented, depending on C#-compiler implementation details for many of their methods. Frameworks like WebSharper, for example, allow you to use full F# across the stack. On the other hand, using MVC with F# controllers is very smooth, and you can use C# on the rendering engine, as there's rarely much code at all going into the actual view part.
- profquail 13y agoThat article is 3.5 years old -- much has changed since then. The F# Foundation site has up-to-date information: http://fsharp.org/webstacks/ http://fsharp.org/webstacks/ About the only thing I know of that you can't do with F# right now (in terms of web development) is write inline code in ASP.NET MVC Razor views. That's not too big a deal though, since you can still write the guts of the application (e.g., your controllers) in F#.
- pionar 13y agoI don't know how you can say the C#'s development is practically stagnated. Evidence? Async/await was just added in C# 5.0.
- pauloortins 13y ago+1
- MichaelGG 13y agoBecause in 5 years of development now, C# has only shipped two major features: dynamic and async. Both of which F# has had since 2007 (maybe dynamic was 2008). Both of which F# implemented better (as libraries, so you don't need intrinsic compiler support). Async's design comes from F#'s design. But without comparing it to F#, Microsoft has not polished the C# 3.0 design. Expression trees are still half implemented (no way to call one exptree from another). MS created anonymous types, but neglected to add simple types like tuples (let alone anything more advanced). Type inference is still ridiculously limited in scope: - Neither parameters nor members can be type inferred. - Local function vars can't be type inferred (because they chose identical syntax for expression trees). - Generic constraints can't be type inferred. - Generic parameters have limited inference. If one parameter can't be inferred, you _must_ specify all of them. On one of the developer blogs, they noted that the reason fields couldn't be inferred was really due to internal compiler codebase complexity. Yet 5 years later, that's still not taken care of. Basically, they aimed for the LINQ outcome, and implemented the required feature set only within the context of LINQ, not for the language as a whole. Which is fine for V3. But then they just left it at that.
- com2kid 13y agoC# has tuples[1], but I'll agree they are not built into the language. Being able to have multiple return values from a function would be really nice rather than having to go return Tuple.Create(valueA, valueB); Likewise being able to declare functions as returning multiple values in a natural fashion would be really cool. But both of those changes are very much sugar, neither of them would make the language more powerful. [1]http://msdn.microsoft.com/en-us/library/system.tuple.aspx http://msdn.microsoft.com/en-us/library/system.tuple.aspx