3 ms·
A solution might be to change the hiring process to test FP concepts instead of OO, or to use a lisp- so users do not need to learn a complex type system in add
by bgorman 8y ago
A solution might be to change the hiring process to test FP concepts instead of OO, or to use a lisp- so users do not need to learn a complex type system in addition to FP.
- dvlsg 8y agoIf they are using C# (I'm making that assumption - I could be mistaken), the type system in F# isn't a huge leap in terms of learnability. It wasn't that way in my experience, anyways. The learning curve seems to be with other aspects - like where the hell do I put my I/O? Error handling? How do I trace (or write) all these functions that are piped or composed together? Questions like those are what I tend to see. Both personally and when pointing other people to F#.
- seanmcdirmid 8y agoAs an ML, F# isn’t a pure FP, so I/O and error handling shouldn’t be that hard. But ya, functional oragami will make debugging harder even in C#.