I have recently been doing the research on dynamic agents, often there will be such a feeling.
For example, Java itself provides Dynamic Proxy, and is not as complex by techniques such as THUNK in Delphi. For serialization, Java / .NET also has a ready-made implementation.
In the past few days, I found a HashMap when I realize the Remoting server, and I became a trouble on Delphi. If it is C , there is ready-made std :: Map available, new Java and .Net also have support for GP, but Delphi is not. If you want to simulate the Java wiping method, you will encounter another question: Delphi does not have a GC, which is easy to cause memory leakage. Moreover, Delphi does not support allocating objects in Stack, so things like smartptr cannot be implemented. The results in the end, with polymorphism, it is ugly, and it is not good to estimate performance. Depressed ~~
When I discussed GC a few days ago, GrayMemory mentioned that C always wants to add good features to others (of course, mainly through the library, rather than modifying the language). In fact, other languages are the same, programmers are always unfounded.
The language has grinded our thinking, and we also determined the scope of our thinking.
This sentence is more experienced for the masters.
It used to be different languages, but now, it is only the views established within the same type of language. For different types of languages, the differences are sometimes nature.
For example, Python, who is recently being learned. For this type of dynamic language, OO's idea has been very different from traditional C / Java. The principle of some classic DIPs like OO is not important, AOP is also very natural, GP is not necessary, and it is not necessary to say those design patterns.
However, there is a very important issue that must be lost, and the performance of dynamic language is still a very important issue.
