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?
The whole brogrammer culture of "throw another library onto the fire" is the reason that simple programs require crazy amounts of computing power.
It's not just JavaScript that has dependencies - everything does.
It’s not the concept of dependencies that’s at fault, it’s the number of them proportional to the task.
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.
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.