Re:Rob Pike's Rules of Programming (1989)
by cutler on Saturday September 16, 2017 @05:34PM
(#15266881)
".. in the modern world", "... younger generation". Maybe you're just getting old? If "OOP had it right all along" there wouldn't be a revival of interest in FP. OOP encourages mutable state and the bigger your programme the harder it is to keep track of it. Rampant mutable state also makes concurrency difficult and concurrency is now more important than it was due to multi-core hardware.
Re:Rob Pike's Rules of Programming (1989)
by inimino on Sunday September 17, 2017 @12:19AM
(#15268216)
I'm wondering what on earth "large and often sparsely populated objects" has to do with functional programming, could you elaborate on that?
Re:Rob Pike's Rules of Programming (1989)
by icebraining on Saturday September 16, 2017 @05:06PM
(#15266762)
"Object-oriented design is the roman numerals of computing." -- Rob Pike
(He also designed his latest language without inheritance)
In my current job we have lots of large and often 'sparsely populated' objects which means basically you can never count on any of the properties you were hoping would be present will actually be present. This means the data objects are essentially useless (at least for knowing what data you have to work with as you are writing code), and violate Pike's rules mentioned about data object design being critically important. In the modern world the younger generation of developers thinks "functional programming is great, and OOP (inheritance, etc) is obsolete", and only after 20yrs of coding they look back and eventually realize OOP had it right all along.
In architectures with massive numbers of sparsely populated objects only the guy who originally wrote any given function will be able to understand it, and everyone else who tries to work in the code is pretty much screwed.