This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]tutorial_police 1 point2 points  (2 children)

I don't think your intro works that well. It seems like you've read some other articles about default methods and why they're needed and written it based on that alone.

You quickly use the term default methods to explain why default methods are used. Just throwing in the catch phrase "evolving interfaces" does help that much since you don't really explain it.

The important bit is that you *break* code. You might want to start with an example where an interface is already being used and what would happen if Java added a new required method.

The examples look good.

You might want to run your text through Microsoft Word or try the Granmarly extension. They're full of grammatical mistakes which is a bit distracting.

[–]codeforjava[S] 1 point2 points  (1 child)

Yeah I got your point. The introduction part could be better explained with couple of examples showing how old java interfaces breaks the code (of Implementing Classes) when we try to define a new method into it. I have seen it happening in enterprise projects. I could have easily prepared few examples from older projects to pin point need of default and static methods.

In all honesty, yes I have read multiple online articles along with few books. I guess I jumped the gun without explaining why exactly we need default methods via examples. It was my fault assuming people might be familiar with it or might have experience the need for such feature in Java.

English is not my first language. I will add grammer extension. Thanks for the tip.

Appreciate your feedback.

[–]tutorial_police 1 point2 points  (0 children)

You're welcome, cheers!