News for hackers. Stuff that matters.
Re:Practical Common Lisp (2005) by na85 on Saturday January 08, 2022 @12:27PM (#29853848)
I'm positing that any project of sufficient complexity is a good candidate for object oriented, yes.

I don't see how a single developer can reason about an entire codebase of hundreds of thousands of LOC.

Re:Practical Common Lisp (2005) by toomanydoubts on Saturday January 08, 2022 @01:03PM (#29854281)
You should probably try writing something under a functional paradigm, emphasizing immutability and pure functions. You'll quickly see how that will help you reason about a large functional project.
Re:Practical Common Lisp (2005) by jlg23 on Saturday January 08, 2022 @12:35PM (#29853962)
Functional programmers argue that pure functions are easier to reason about than functions that drag in state (like methods in OOP tend to).
Re:Practical Common Lisp (2005) by na85 on Saturday January 08, 2022 @03:17PM (#29855713)
Please list some real-world software of significant complexity that is 100% purely functional.
Re:Practical Common Lisp (2005) by jlg23 on Saturday January 08, 2022 @05:02PM (#29856845)
Where does the "100% purely functional" requirement come from? By some strict definition, this is impossible, because you'd not have any means of communicating the result of your computation.

In pure OOP speak: A "final static" method is easier to reason about than some non-static, non-final method. (But when a method is defined as "final" and "static", the providing class only serves as a namespace - where is the OOP in that?)

Re:Practical Common Lisp (2005) by toomanydoubts on Sunday January 09, 2022 @05:04PM (#29867776)
Hasura, Pandoc, XMonad?