in reply to Thoughts on "Go"?

Well thank goodness someone has had the cahones to use interfaces instead of inheritance.

I've been saying that for years to no effect.

I maintain the code for a context-oriented template language which I use to make web pages and find vastly superior to PHP or "template toolkit" or whatever.

But man, I get kicked for not having objects and inheritance in my template language every time I talk about it publicly.

Will people decry the lack of a "true" object oriented model in Go? Or perhaps would-be naysayers will be swayed by Google's halo?

Replies are listed 'Best First'.
Re^2: Thoughts on "Go"?
by wazoox (Prior) on Nov 16, 2009 at 14:12 UTC
    Well thank goodness someone has had the cahones to use interfaces instead of inheritance.
    I've been saying that for years to no effect.

    Weird, wasn't Java all about de-emphasizing inheritance to privilege interfaces instead? BTW, I've been saying it for years to no effect neither, but it hardly surprises me :)

    I maintain the code for a context-oriented template language which I use to make web pages and find vastly superior to PHP or "template toolkit" or whatever.

    Which is? care to share, perhaps?

    But man, I get kicked for not having objects and inheritance in my template language every time I talk about it publicly.
    Will people decry the lack of a "true" object oriented model in Go? Or perhaps would-be naysayers will be swayed by Google's halo?

    Object orientation may not be a primary concern for a system development language anyway. Or else.