【正文】 a project at work, and I publish any reusable package from that work that I create. My project ends up factored better, and I end up with a bunch of building blocks I can reuse elsewhere (and then I do!). Sometimes random people from the interwebs even fix my bugs before I notice them! This approach is not unusual at all either, at least in the munity. The munity is lead by developers that have each published literally hundreds of packages. I don’t even know how this is possible. Of course there’s absolutely nothing to stop other languages from following suit, so it seems to me like munity culture is the deciding factor. Massive monolithic frameworks like Ruby on Rails tend to not take hold in the munity mindshare, I think due in part to this “tiny module aesthetic”, and it’s all the better for it. It seems to me that monolithic frameworks like Rails don’t have a clear notion of what does not belong in Rails, and so they tend to expand indefinitely to include everything an application could need. This leads to people trying to assert that Rails is the best solution for all problems, and having a cooling effect on innovation within the web application space in the Ruby munity. The tiny module aesthetic also leads to an ecosystem of extreme reuse. When a package doesn’t do more than is absolutely necessary, it’s very easy to understand and to integrate into other applications. Conversely, while massive monolithic frameworks tend to appear in a lot of enduser applications, they rarely never end up being dependencies in other packages themselves. It seems unfortunate to me that so much great software should be so difficult to reuse. git and monoculture To be honest, few things are more boring to me in software development than version control, and I find the plexity of git to be a bit silly and mostly unnecessary for me, but I’ve never heard of a developer that doesn’t use it, and there’s huge value in that kind of monoculture. It means that they all speak with a mon language and there’s no impedance when you want to contribute to someone else’s projects. has a similar effect in lowering the barriers for crosspollination between developers. I’ve only very rarely seen a project that wasn’t on github. This means I immediately know exactly where to find source code if I want to contribute. The pluses and minuses of a github monoculture go far beyond this, but there’s probably enough fodder there for an entirely different post. Permissive Licensing packages tend to use extremely permissive licensing like MIT and BSD licensing. In fact, the default license for a package created by `npm init` is BSD. I think this is another sign of the times. Very few people care anymore if someone else forks and doesn’t contribute back. There’s very little to gain in not contributing back anyway because of the cost of maintaining your own fork. This is important because no one wants to have to deal with dependencies that make them think about legal repercussions, or give them extra responsibilities. Licenses like the GPL end up having a cooling effect on softwarereuse for this exact reason. 附錄二 外文翻譯（中文翻譯）Nodejs社區(qū)因為有一系列穩(wěn)定的API，加上原生擴展的開發(fā)來管理進程。 為了不影響用戶體驗，我們設計的‘Interactive’ 請求只需要。 這篇文章同時也介紹putecluster 模塊：，可以用來很方便的管理進程，從來二線分布式計算?？傊?，我以后要多專心研究軟件開發(fā)，以更加飽滿的熱情投入到本專業(yè)的學習中去，認真做好每一件事情，爭取得到更多的收獲。本系統(tǒng)功能雖簡單，但目的的了解基于nodejs應用程序的開發(fā)過程，如果要完善系統(tǒng)還需更多的時間。 運行客戶端打開瀏覽器，輸入localhost：3000，系統(tǒng)就可運行系統(tǒng)運行之后，進入登錄界面：輸入昵稱就可進入聊天。第八章 軟件使用說明書本章演示在單機條件下運行聊天工具，模擬實現(xiàn)聊天過程。預覽效果如下：圖68第七章 系統(tǒng)測試測試系統(tǒng)Windows 7，測試瀏覽器Google Chrome。 user39。status39。 (39。 var p = (39。 joined39。system39。這里實現(xiàn)顯示在線用戶數(shù)及在聊天主界面中以系統(tǒng)身份顯示用戶連接離開等信息。me39。 (39。 if ( == 13 amp。messageInput39。messageInput39。 }。).value。).addEventListener(39。}, false)。 (39。 ()。colorStyle39。click39。圖65IE及FF中均是一個普通的文本框，不過不影響使用，只是用戶只能通過輸入具體的顏色值來進行顏色設置，沒有Chrome里面那么方便直觀。 }。img class=emoji src=../content/emoji/39。 if (emojiIndex totalEmojiNum) { result = (match[0], 39。圖64部分代碼如下：_showEmoji: function(msg) { var match, result = msg, reg = /\[emoji:\d+\]/g, emojiIndex, totalEmojiNum = (39。圖63文字總是很難表達出說話時的面部表情的，于是表情就誕生了。 (file)。 (39。39。39。, 39。system39。).addEventListener(39。而base64格式的圖片直接可以指定為圖片的src，這樣就可以將圖片用img標簽顯示在頁面了。圖片不同于文字，但通過將圖片轉(zhuǎn)化為字符串形式后，便可以像發(fā)送普通文本消息一樣發(fā)送圖片了，只是在顯示的時候?qū)⑺€原為圖片。}.emoji{ display: inline。 padding: 2px。 position: absolute。 float: right。 height: 90px。 opacity: 0。}/*custom the file input*/.imageLable { position: relative。}.items { height: 30px。 overflow: auto。 margin: 5px 0px。 width: 100%。 display: block。 left: 0。}loginWrapper { position: fixed。 height: 640px。 title=font color / input id=emoji type=button value=emoji title=emoji / label for=sendImage class=imageLable input type=button value=image / input id=sendImage type=file value=image/ /label input id=clearBtn type=button value=clear title=clear screen / /div textarea id=messageInput placeHolder=enter to send/textarea input id=sendBtn type=button value=SEND div id=emojiWrapper /div /div /div div id=loginWrapper p id=infoconnecting to server.../p div id=nickWrapper input type=text placeHolder=nickname id=nicknameInput / input type=button value=OK id=loginBtn / /div /div script src=//script script src=scripts//script /body/html：html, body { margin: 0。主界面的構(gòu)建，因為是比較大眾化的應用了，界面不用多想，腦海中已經(jīng)有大致的雛形，它有一個呈現(xiàn)消息的主窗體，還有一個輸入消息的文本框，同時需要一個發(fā)送消息的按鈕