3 ms·

> Benefits: No NPM dependencies While excessive dependencies is a problem and a liability, reinventing the wheel is even a bigger problem! NPM is there to solv

> Benefits: No NPM dependencies While excessive dependencies is a problem and a liability, reinventing the wheel is even a bigger problem! NPM is there to solve a problem and when used correctly it brings HUGE benefits in many ways. Listing this as a benefit is clearly not understanding what NPM is for and part of the classical Not Invented Here.

mbel 10y ago
Not relying on package manager does not imply that they rewritten all the functionality provided by relevant packages. They may still use 3rd party libraries but instead of adding dependency to package manager, they may pull their sources in build script or copy the sources into their own source tree.
- franciscop 10y ago
  That is true but also a small nightmare for anyone in Node.js ecosystem who wants to contribute. However from a quick glance it doesn't seem like it, it seems like they depend on total.js framework as expected. Only the main framework file index.js is already 15k lines long: https://github.com/totaljs/framework/blob/master/index.js https://github.com/totaljs/framework/blob/master/index.js
- ezekg 10y ago
  Seeing as the index.js file is 15,482 lines of code[0] all attributed to a single author, I seriously doubt it. [0]: https://github.com/totaljs/framework/blob/master/index.js https://github.com/totaljs/framework/blob/master/index.js Edit: apparently that's not the right repo… looks like the comments are right that the source code for the messenger app is not on GitHub.
  - nulagrithom 10y ago
    Took me a bit to figure out that Total.js is a framework and the Slack clone (Messenger) is built on top of it. Total.js itself appears to be 15k lines in a single file with no dependencies, built and maintained by one guy (for the most part). Insanity.
    - KajMagnus 10y ago
      In which way is that I insane? (I might be a tad bit more insane :-/ )
wolco 10y ago
There are a lot of use cases for no npm dependencies. For many who live behind a firewall in dev standalone packages can be a blessing.
tmaly 10y ago
I think there is a trade off, look at what happened with the left-pad dependency. Having no dependencies is great, but you need a rather large community of contributors to offset that or you end up with a stagnant undocumented bundle of source code.
- aeorgnoieang 10y ago
  > what happened with the left-pad dependency But that could happen to any dependency. Arguably, left-pad was the least-worst dependency for "what happened" to have happened.

mbel 10y ago

Not relying on package manager does not imply that they rewritten all the functionality provided by relevant packages. They may still use 3rd party libraries but instead of adding dependency to package manager, they may pull their sources in build script or copy the sources into their own source tree.

franciscop 10y ago
That is true but also a small nightmare for anyone in Node.js ecosystem who wants to contribute. However from a quick glance it doesn't seem like it, it seems like they depend on total.js framework as expected. Only the main framework file index.js is already 15k lines long: https://github.com/totaljs/framework/blob/master/index.js https://github.com/totaljs/framework/blob/master/index.js
ezekg 10y ago
Seeing as the index.js file is 15,482 lines of code[0] all attributed to a single author, I seriously doubt it. [0]: https://github.com/totaljs/framework/blob/master/index.js https://github.com/totaljs/framework/blob/master/index.js Edit: apparently that's not the right repo… looks like the comments are right that the source code for the messenger app is not on GitHub.
- nulagrithom 10y ago
  Took me a bit to figure out that Total.js is a framework and the Slack clone (Messenger) is built on top of it. Total.js itself appears to be 15k lines in a single file with no dependencies, built and maintained by one guy (for the most part). Insanity.
  - KajMagnus 10y ago
    In which way is that I insane? (I might be a tad bit more insane :-/ )

wolco 10y ago

There are a lot of use cases for no npm dependencies. For many who live behind a firewall in dev standalone packages can be a blessing.

tmaly 10y ago

I think there is a trade off, look at what happened with the left-pad dependency. Having no dependencies is great, but you need a rather large community of contributors to offset that or you end up with a stagnant undocumented bundle of source code.

aeorgnoieang 10y ago
> what happened with the left-pad dependency But that could happen to any dependency. Arguably, left-pad was the least-worst dependency for "what happened" to have happened.