Whether a language is actually mastered depends not on how much you have learned, but on what you have done.

let's take petabytes for example. It used to be simple and easy to learn. It wasn't just to drag and drop several widgets, double-click to write some Code . It's easy. You must always think that a language is like this, let me tell you what a big mistake you have! In a word, whether a language is actually mastered is not about how much you have learned, but about what you have done. Looking at the following window, you will know that Pb can make such a wonderful interface. It seems that Pb is still profound and profound:

some people may say, what should I do? The old petabytes are different from those in Java and. Net fields. How can I compare them? Yes, for B/S architecture, Pb cannot compare with Java and. net, but for C/S architecture, Java and. NET may not be more petabytes. PB, the development cycle is short, and there is a data window, this is a unique control, in the aspect of processing a large amount of data, there is no language ratio!
I used to write a signature like this in Feixin: I have no development experience for more than 10 years. I will not talk about the advantages and disadvantages of a language. Some of my friends are puzzled and even asked me with a certain question. If I have less than a decade of development experience, can I not feel the advantages or disadvantages of a language? My answer is not to talk about it, but not to replace it with articles . If you have any ideas, let me talk about it, but do not express it in articles. Otherwise, it will be criticized by some senior people! I once saw such a post on csdn ------- a good example of this problem. The post author is an old programmer who worked as a petabyte in Year 89. He is ready to give up petabyte and turn to Java and. net. He is also senior and has posted such a post. However, there is another post entitled: "reply: Keep petabyte and die". This is a post posted by a senior author who is 15 years old. At the beginning of the post, I said: I have been using PB for almost 15 years, old brother. You seem to have been focusing on version 6.5 for nine years. I know it too well, do not use a new employee. The post is very lively and intense. If you are interested, you can go to these two links and check them out!
original post:
http://topic.csdn.net/u/20080819/16/0d9dbacd-0aae-4b3a-9c9a-3ede6270eebc.html? 50915746
reply post:
http://topic.csdn.net/u/20080825/19/6f3018b3-640b-4130-b76f-a4b126295b5f.html?

1085567716

conclusion: Pb AND Pb. I know more about you and want to learn more. For example, some encapsulated things that others do well should not be used, why is it not a project for an old Program engineer, others have accumulated several years of encapsulated classes, objects, and methods at hand. You can use them directly at that time, so it is not a matter to start a project, for those frameworks, there is no need to consolidate them. You only need to do some business processing. Therefore, from now on, I need to prepare for accumulation ....