C # design patterns should be eclectic

Just as everyone has their own personality, each development language also has its own personality.

 

In the project, we can apply the development experience of one language to another, but the effect is not necessarily good, because:

·The language has its own shortcomings: it is not only time-consuming and labor-consuming to implement short points, but also unsatisfactory results.

·Language has its own strengths: however, in order to keep up with the previous experience to make things fit, the result is not the essence of language.

 

I believe you have also discovered that it is written in one language.Hello WorldIt is one thing. Writing an application is one thing. Writing an application is completely another thing. This is engineering.CodeIt is different from the "Toys" code. The implementation of knowledge in textbooks to projects cannot be illustrated. The development language and target environment need to be considered, and the design mode is no exception.

 

Maybe you will feel that using generics, delegation, events, attributes, configuration files, and other methods is inconsistent with the content introduced in design patterns, but don't forget that the book design patterns has been published so far.20In the meantime, both the development language and the technical platform have "changed to the human ",Gof 23The idea of mode not only influences our Language designers and platform designers who are at the forefront of technology, but also subtly integrates the idea of mode into their work achievements, as a user, we are "pushing" others. Everything starts from the "Wheel", which is somewhat economic.

 

In the project, we should useC #In this way, your understanding of the design model is cast into your own results, and the implementation is concise and direct.