Some Opinions on linb

In the previous article, I talked about the trend of using short names of $ and _ in linb. This article talks about some technical issues.

To obtain the source code of linb, we need to provide "any proof of publicity made for this site". This is not surprising. I think the author will probably do more on the personal site that exchanges links.

Your stuff is good. First, try it for users. Since I have not tried it, I do not know if you are really good. How can I help you with promotion? This requirement is not only unreasonable, but also creates obstacles to initial acceptance. This requirement may be applied to many JS Code reporters (their purpose is to use code, and the "Kneeling" and "spitting blood" that you see on various BBS and forums are all such people) effective, but the true developer's personality must be: He is very cautious in maintaining his professional image and will never promote or publicize things he hasn't really recognized. However, if an item is recognized by real experts, its benefits are far greater than those of a group of small P-kids. For example, you can see that prototype has almost no documentation. But it is recognized by some real experts in the community. Many people write articles and write tutorials to promote it. Did you see prototype saying that you would like to help me publicize it before downloading it? No. On the contrary, prototype homepage is so concise:

• Download the latest version (1.4.0)
• Just. Js, Please
• Browse the Subversion Repository

Pay special attention to the "just the. JS, please". Yes, please use it directly! Linb, please learn this one.

In addition, although linb claims to be open source, its SC is compressed by the Dean Edwards compression, and its form is difficult to calculate the source code. Of course, what Dean does is not a real obfuscator, so a certain level of comrades can still restore the source code that can be viewed and understood. Although I don't know the form of its complete linb release, let me take a look at linb with a small heart. I guess he still doesn't provide the real source code, but just gives the compressed version.

From the perspective of linb's dual license, I assert that linb only wants to use open source.

In fact, without real open source, there is no "marketplace" development method. Although others cannot see your secrets, you also lose the help of others, such as code review and bug discovery, provide patches and so on.

Of course, this is not a problem for linb. ajile has only compressed versions since a specific version. Compared with Dean Edwards, the creator of the compressors, this kind of blind eye is not worth mentioning. Is the commercial value of Dean's amazing IE7 (yes, all the people I know that boast JavaScript masters have to be amazed at IE7) smaller than linb or ajile?

Furthermore, self-confidence in the Code is actually not a manifestation of self-confidence. In addition, for SC and ajile of linb, I think the package/import mechanism of pies is better. For example, both SC and ajile require code organization in a special way. I will discuss it in detail later.

As another Chinese JS framework project, linb still hopes to improve itself and promote it. Just as the author realizes that to be accepted by the mainstream, he must write documents in English. I really hope that linb can show the Javascript developers in China the level and confidence they have in the JS community.

Updated on April 9, July 12: Today, I browsed the linb website again and found that it has provided the source code for download. I'm glad to see that linb is becoming more elegant.