4 ms·
No one prevents you to use immutable structures in OOP. Getting some help from language is nice, but after 10+ years of programming all those patterns (e.g. im
by deepsun 12y ago
No one prevents you to use immutable structures in OOP.
Getting some help from language is nice, but after 10+ years of programming all those patterns (e.g. immutable) become so natural, that you don't really think much about them. Because you know what data structure you want, and see what language offers you. So the whole "which language" deal doesn't make so much difference (although it's easier/harder in some languages). Tooling/libs and community matters way more.
- the_af 12y ago> No one prevents you to use immutable structures in OOP. No one prevents you, but what about the code other people write?
- deepsun 12y agoGood point. Fortunately, I had pretty good engineers in my recent teams, but, remembering my older projects, I totally agree with you that it's good when language makes it hard to write bad code for less competent engineers.
- fallat 12y agoYou've hit the nail right on the head. People praising FP don't realize (but start to after awhile) that you should combine the FP paradigm with /OTHER/ paradigms as well. Your arsenal of patterns will help you write code. Don't limit yourself to one.
- sklogic 12y agoAs long as there is no decent pattern matching in most of the OO languages, they're pretty useless. No matter how big is community and how hip is tooling.