This discussion has inspired me to try once again to express my sense of what I
mean by complexity. It's probably too rambly for most people, but some may find
it interesting:
http://theprogrammersparadox.blogspot.ca/2012/06/what-is-complexity.html
Paul.
>________________________________
> From: Miles Fidelman <mfidel...@meetinghouse.net>
>To: Fundamentals of New Computing <fonc@vpri.org>
>Sent: Saturday, June 16, 2012 3:20:22 PM
>Subject: Re: [fonc] The Web Will Die When OOP Dies
>
>BGB wrote:
>>
>> a problem is partly how exactly one defines "complex":
>> one definition is in terms of "visible complexity", where basically adding a
>> feature causes code to become harder to understand, more tangled, ...
>>
>> another definition, apparently more popular among programmers, is to simply
>> obsess on the total amount of code in a project, and just automatically
>> assume that a 1 Mloc project is much harder to understand and maintain than
>> a 100 kloc project.
>
>And there are functional and behavioral complexity - i.e., REAL complexity, in
>the information theory sense.
>
>I expect that there is some correlation between minimizing visual complexity
>and lines of code (e.g., by using domain specific languages), and being able
>to deal with more complex problem spaces and/or develop more sophisticated
>approaches to problems.
>
>Miles
>
>
>
>-- In theory, there is no difference between theory and practice.
>In practice, there is. .... Yogi Berra
>
>_______________________________________________
>fonc mailing list
>fonc@vpri.org
>http://vpri.org/mailman/listinfo/fonc
>
>
>
_______________________________________________
fonc mailing list
fonc@vpri.org
http://vpri.org/mailman/listinfo/fonc
