Designing a consistent language is *very* hard

[Joakim]

On Saturday, 28 April 2012 at 08:18:34 UTC, Guillaume Chatelet 
wrote:
> Sorry for the noise but I think a few language designer out 
> there might like this one :
> http://me.veekun.com/blog/2012/04/09/php-a-fractal-of-bad-design/
>
> I think Walter and Andrei will smile ( or cry ) reading it.
> It's no trolling here, I do think this post is very valuable 
> and relevant from a language design perspective.
Bump.  Nick linked this blog post in another thread and after 
nosing around his blog, I found another good blog post the guy 
wrote earlier this year:

http://me.veekun.com/blog/2013/03/03/the-controller-pattern-is-awful-and-other-oo-heresy/

This could be an important strength to highlight in D, since it 
doesn't have the OO constraints that Java imposes.  Although, I 
have run into this problem myself when poking around a D project 
filled with OO boilerplate, with the single function that 
actually did anything hidden away in a private method in some 
unexpected class.  Perhaps it's because the project was still 
being written and the author found it easier to write all his 
class superstructure first, but I suspect even the finished 
project had far too much of this OO debris.

The problems of that project can't be blamed on D of course, but 
that unfortunate mentality seeps in from other languages, which 
hopefully blog posts like this and better idiomatic D can combat.