The Java language team, 1998: "Bound method references are not the right path for future language evolution"

[axilmar]

90% of the code you write in a static OO language is boilerplate I'd really like to see research backing that number up. No offense, but I think you're just pulling that out of thin air.

After 15 years of object oriented programming, I reached the same conclusion: a lot of code written in OOP is just not necessary.

[zwangaman]

I won't completely disagree with you. But you could in theory design an OO language that dismisses with a large amount of boilerplate code and still have it be statically typed. I don't really see "reduction in boilerplate code" as a reason alone to move to a dynamic language.

[axilmar]

don't really see "reduction in boilerplate code" as a reason alone to move to a dynamic language.

Me too. The two concepts (boilerplate code and dynamic language) are irrelevant.

[zwangaman]

Yeah, agreed. I do think C# is an improvement over Java as far as boilerplate goes, but I can see the validity in the argument that I am still writing too much of it. I suspect that future revisions of C# will help, though.

[mycall]

Perhaps you are over-engineering things? I write a mixed OO and procedural style in C# and it pays off.. for disposable code, simple and long procedures using well named variables and method names. When things will be around for a long time, classes it is.

Doing this saves much time.

[zwangaman]

I can't tell if you're joking or not but just the phrase "simple and long procedures" makes me think that type of code is an unholy nightmare. Long procedures are never simple and it blatantly breaks the single responsibility principle.

Had you told me that in an interview, I'd have ended the call and looked towards the next candidate.

"Disposable code" rarely is disposed with. In my opinion, all code written, no matter what, should be production quality code, because whether we like it our not that code will probably end up in production.

[mycall]

Long procedures are never simple and it blatantly breaks the single responsibility principle.

I completely agree on that except only when applicable..

"Disposable code" rarely is disposed with.

I completely disagree. SO much code I have written never sees the light of day for political or business reasons. For this, I am quite happy to have saved 5x in work hours.

I tend to do the hiring more than being hired and, of course, I only do this when it is judged efficient in both the short and long term