Recomendados
Más contenido relacionado
Destacado
Destacado (20)
Último
Último (20)
45 F#antastic minutes!
- 1. 45 F#antastic minutes! Getting Started with F# Alex Casquete acasquete
- 3. Functional Programming is not new but is ignored until now
- 4. The Challenges Process large datasets Scale to processors & computers Easily testing Declarative logic
- 5. “Take the next ticket from a list. If the ticket is not printed, send to print. If there are more tickets in the list, go to the begining.”
- 6. “Run the first command for every customer for which the second command returns true.”
- 7. “Send to print every ticket that is not printed.”
- 8. “Take the next ticket from a list. If the ticket is not printed, send to print. If there are more tickets in the list, go to the begining.” “Send to print every ticket that is not printed.”
- 9. Thinking difɘrɘntly Say “what” rather than “how”
- 10. Thinking difɘrɘntly in C# Imperative foreach (Ticket t in Tickets) { if (!t.IsPrinted) { Print(t); } } Declarative Tickets .Where(t=>!t.IsPrinted).ToList() .ForEach(t => Print(t));
- 11. Functional Basic Concepts Demo: From C# to F#
- 13. <ironic> 10 Reasons not to use Functional Programming </ironic>
- 14. Reason 1 I don't want to follow the latest fad
- 15. Reason 2 I get paid by the line I get paid by the line I get paid by the line
- 16. Reason 3 { I love me some curly braces }
- 17. Reason 4 string s = “I like to see explicit types”;
- 18. Reason 5 I like to fix vugs
- 19. Reason 6 I live in the debugger
- 20. Reason 7 I don't want to think about every little detail
- 21. Reason 8 I like to check for != nulls
- 22. Reason 9 I like to use design patterns everywhere
- 23. Reason 10 It's very freaky
- 24. Why use F#? The Five C’s
- 26. Understanding F#
- 27. F# 3.0 Data, Services, Information Access F# 2.0 Transformations, Analysis, Algorithms, Code, Parallel C#, HTML5, JS Presentation, Publication, Experience
- 28. Type providers Demo: OData, WSDL
- 29. More Resources?