On Thursday, 4 July 2013 at 07:20:18 UTC, Russel Winder wrote:
[..]
Many programmers are still using 1970s approaches to
programming, even
though they may be 20-something, because that is what they have
been
taught to do. As long as they use sequence, selection and
iteration that
is all they need.
Even on the work environment.
Every time I see the usual shell and vi/emacs combo it brings me
back memories of when my home computer was a Timex 2068.
Or as someone puts it,
http://andrewbrookins.com/tech/one-year-later-an-epic-review-of-pycharm-2-7-from-a-vim-users-perspective/
And neither of these groups worry about test coverage that much.
To be honest in the fortune 500 companies very few do. We always
try to push for it in our consulting projects, but not all
customers
buy into it, specially if the project requires interaction with
the
in-house developers.
FOOPLOG may have failed but Scala has brought programming to
functional
AND object-oriented. Groovy, Kotlin, Ceylon, etc. are pushing
at this as
well. It is all about the balance of use of internal and
external
iteration not treating it as warfare. Python had its own
consideration
of these issues in the Python 2 → Python 3 change.
I think Microsoft plays a big role here. By sponsoring OCaml,
Haskel and F# development, as well as, introducing FP to the
enterprise via LINQ.
Native still seems to be in the 1990s OO vs. functional war:
internal OR
external. cf. C++, Go, D, Rust, Haskell, OCaml, F#, etc.
The main issue is that this is very human related.
Sometimes you really need a few generations to make people adopt
new ideas.
--
Paulo
