4 ms·

Agreed. Why reinvent a wheel that's there for the using, when you could be working on the aspects of your project that make it your project?

• reaperducer 8y ago
  Because the scope of a project should include usability, speed, resource thrift, maintainability, and security. The whole brogrammer culture of "throw another library onto the fire" is the reason that simple programs require crazy amounts of computing power.
  • andrewstuart 8y ago
    Unless you are doing assembly language programming at a clean screen then you are building software that sits on the shoulders of other software. It's not just JavaScript that has dependencies - everything does.
    • snazz 8y ago
      You make a very valid point, but compared to other programming languages and cultures, the JavaScript ecosystem encourages mammoth projects with many more dependencies than they need. It’s not the concept of dependencies that’s at fault, it’s the number of them proportional to the task.
    • PavlovsCat 8y ago
      > Unless you are doing assembly language programming at a clean screen then you are building software that sits on the shoulders of other software. Yet, we don't just eat dirt off the street because even when we eat the usual food, there's always some dirt in it.
    • pdimitar 8y ago
      Really bad analogy. Most runtime libraries (or OS libraries for that matter) of other programming languages are of high quality and don't introduce 20 seconds of non-interactivity on a gigabit connection and 4-core CPU with 32GB RAM. A ton of websites out there do the latter. I don't need to do assembly language programming because the tools I have (that are built on top of it) are actually good. Unlike those in JS land.