On 10/08/17 02:47 AM, Henrik Johansson wrote:
I beg to differ. Most Java apps I have seen over many years almost
unanimously suffer from over-modeling.
A former customer did a deep, thoughtful, *thorough* model of bracket
tournaments, without any attempt to abstract the salient features. Java
represented it beautifully, in complete detail...
So it's now impossible for a single person to keep it in their brain,
and every attempt to change it introduces new, surprising "features".
In effect, the ability to represent anything easily led to our error: we
Go (or C) doesn't actually address over-modeling: it's merely harder to
do, and we're less likely to make that error, just as a side-effect (;-))
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
dav...@spamcop.net | -- Mark Twain
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.