continuing on on comments made here
http://www.futurealoof.com/posts/momentum.html
This article is the analysis of why nodejs is (and will be ) a more successful platform than its contemporaries (python ruby etc).
...In the earlier days of node you could write anything. The advantage of nothing being compatible is that there is a much greater opportunity to attract people interested in writing virtually anything. That means a greater potential for early investment, which creates early momentum, which you can only lose over time so maximizing that early growth is the most important thing....
(my comment: one thing to note here is that Java had a similar potential early on. The virtual machine created a very isolated world where no existing (C/C++) lib could be brought in. However, that was seen then as a disadvantage and the "parents" of that platform attempted to alleviate it by expanding a massive "standard" set of libraries that emulated the previous world and choked any potential for early on community investment.)
Other interesting article from this guy's blog:
http://www.futurealoof.com/posts/momentum.html
This article is the analysis of why nodejs is (and will be ) a more successful platform than its contemporaries (python ruby etc).
...In the earlier days of node you could write anything. The advantage of nothing being compatible is that there is a much greater opportunity to attract people interested in writing virtually anything. That means a greater potential for early investment, which creates early momentum, which you can only lose over time so maximizing that early growth is the most important thing....
(my comment: one thing to note here is that Java had a similar potential early on. The virtual machine created a very isolated world where no existing (C/C++) lib could be brought in. However, that was seen then as a disadvantage and the "parents" of that platform attempted to alleviate it by expanding a massive "standard" set of libraries that emulated the previous world and choked any potential for early on community investment.)
Other interesting article from this guy's blog:
http://www.futurealoof.com/posts/nodemodules-in-git.html
Summary of that post:
Summary of that post:
If you are building an app or a web service or anything that is "deployed" then you should include node_modules in the repo but not binary targets
If you are building a package/module (ie sth that is used by other packages/modules or apps ) then do not include the node_modules in the See for example
deploys:
or packages
No comments:
Post a Comment