5 ms·

You are just making stuff up. You still can not articulate why these dependencies are unnecessary. That you in particular might have no use for the features th

• rs186 1y ago
  > You still can not articulate why these dependencies are unnecessary. No, because I don't have to answer that question. I can simply choose not to use this project, like what I do with npm projects. There is a project that's 500kb in code with 120 dependencies, when another one is 100kb with 10 dependencies that's also well maintained? I'll choose the latter without question, as long as it satisfies my needs. I don't care why the other one has 120 dependencies or try to justify that.
  • constantcrying 1y ago
    Why are you complaining that a project you do not care about is using 13 dependencies, all of which, to your knowledge, are absolutely essential for the functionality? >There is a project that's 500kb in code with 120 dependencies And therefore some project using 13 dependencies is doing it wrong? What are you on about. Obviously there is an enormous abuse of dependencies in the JS ecosystem, who cares?
    • hu3 1y ago
      Their original complaint was about the project taking 20GB of disk space to compile. Also they did point out that the parser depends on a serialisation library, so you're also mistaken about parent thinking the dependencies are necessary. On another note, this pervasive kind of passive aggressive, hand-wavy, tribalistic, blind defense of certain technologies speak volumes about their audiences.
      • constantcrying 1y ago
        Please actually read the conversation before commenting.