Disagree with "What's important is thought, not language."

Whenever there is a language dispute, you will see this sentence. It sounds reasonable, because most of the same functions can be done with different software.

In particular, when confronted with a specific problem, it is indeed a thought that can help solve the problem. But the problem is not a small specific problem, but a mature and usable product, such as the full use of the language of all the convenience features to achieve. each language will have its own characteristics (mainly different philosophical guidance, historical factors, grammatical rules, implementation methods, naming rules, etc.), plus each language has its own library, of course, including controls, which will cause a product will be deeply bound to the language , This can be achieved by simply translating it in a different language. For example, my company has a product originally DELPHI7 implementation, but the new version using C + + and QT development, my favorite and most major language is Delphi, but also have all the old version of the source code, but even so, in the new version of the development process, almost no reference to Delphi any code, More than just reference it in terms of user habits and interface design factors, because the language and language, libraries and libraries, the difference is really too big. This is not to say that I did this project, but that I thought of it (according to the observations of many projects), but this project really deepened my judgment. You can do it in a different language, but it's a daunting workload, and it's tiring to include some of the libraries that you're not familiar with.

A negative example is, I have a lot of ideas, even thinking, even I have done a good semi-finished, but who will help me to complete it into a usable product? The implementation of the time will encounter countless problems, even if there is no mention of what is worth mentioning the difficulties, still have to spend countless time. So what is the meaning of this so-called thought?

Another reason is that after more than more than 10 years of study and thinking, want to become a top technology master, must be VIP machine, equivalent to understand all aspects of Delphi, become part of their own body, like the gold helmet pilot Shanga said: know not, familiar enough, to really enter the subconscious, To be conditioned. All subconscious, all reflex, are part of the body, hands and feet can be casually changed? programming without air combat so cruel, hard 10 in order to rob a few seconds of time and timing, either lose their own life or victory, but not become a master of programming I am also not reconciled, because that equates to chronic suicide. For me, I feel comfortable using C + + programming, but still feel that Delphi is a part of my body, well, later on it.

Finally, I feel that Delphi language is almost a philosophical system, is the result of a variety of implementation methods and performance tradeoff, Windows almost omnipotent, so it is almost omnipotent, and Delphi itself is composed of dozens of masters, want to understand and grasp its aspects very difficult , it feels so hard to master. But I'll keep trying.

Disagree with "What's important is thought, not language."