Peter is the former President of the New Zealand Open Source Society. He is currently working on Business Workflow Automation, and is the core maintainer for Gravity Workflow a GPL workflow engine.
Linking functional programming with static methods is probably a mistake, but I've been reading some interesting critiques of OO which got be thinking about why singletons are used when state is not being maintained. I know there are some benefits from singletons, but increasingly these are also under attack by functional programming fans. However my mistake was linking static methods and functional programming.
This raises a question. If you have an existing Java application should I even try to shift to functional programming? Can they co-exist? Is there a bridge? I don't really have the perspective and am happy to get advice from others.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Linking functional programming with static methods is probably a mistake, but I've been reading some interesting critiques of OO which got be thinking about why singletons are used when state is not being maintained. I know there are some benefits from singletons, but increasingly these are also under attack by functional programming fans. However my mistake was linking static methods and functional programming.
This raises a question. If you have an existing Java application should I even try to shift to functional programming? Can they co-exist? Is there a bridge? I don't really have the perspective and am happy to get advice from others.