“Why Functional Programming in Java is Dangerous” cafe.elharo.com/programming/…

Jan 20, 2013 · 1:37 PM UTC

15
105
108
Replying to @stilkov
@stilkov the point is, use the right tools for the right job, but once you are using that tool, use it the way it was meant to be used?
1
@qanderson7 Yes, that's at least how I read it
Replying to @stilkov
@stilkov a bit of a flawed argument.. laziness is not a prerequisite for functional programming. An interesting read .. existentialtype.wordpress.co…
1
4
Replying to @stilkov
@stilkov cc:@martinfowler "Why Programming in Java is Dangerous" npr.org/blogs/thetwo-way/201…
Replying to @stilkov
@stilkov but does your warning still apply with iterator-based google collections? Still need caution, but won't blow Java stack.
Replying to @stilkov
@stilkov cc:@martinfowler Should be "why junior programmers need mentoring". A Java dev would define infinite sequence as Iterable not List
1
2
Replying to @stilkov
@stilkov Nonsense. Functional != lazy and a "very smart programmer" would know that
Replying to @stilkov
@stilkov Here's a Ruby example where programmers do stuff that the language designers didn't expect/optimize for: tonyarcieri.com/dci-in-ruby-…
2
Replying to @stilkov
@stilkov You are confusing lazyness and FP (OCaml, for instance, is a sucessful non-lazy functionnal language) CC @DarkSoul4242
Replying to @stilkov
@stilkov I am not that smart (no Ph.D) but I immediately spotted List as not being an adequate functional datastructure