News for hackers. Stuff that matters.
Re:The state of JavaScript modules by jessaustin on Monday May 29, 2017 @10:22AM (#14439204)
Yeah it's easy to start coding in python. Eventually one wants to distribute that code, and then the tears begin.
Re:The state of JavaScript modules by omginternets on Monday May 29, 2017 @11:17AM (#14439509)
That was true years ago. It's really not the case anymore. Related reading: https://glyph.twistedmatrix.com/2016/08/python-packaging.htm...

More to the point, even if what you said were true, the tooling is still absurdly complicated in the JS world. Your comment is a mix of of a red herring and whataboutism.

Re:The state of JavaScript modules by jessaustin on Monday May 29, 2017 @06:47PM (#14441928)
Thanks, I read that last year. This seems telling:

There should be tools that help you write and update a setup.py.

In my experience, this was always the hardest part. I started using python in 1999, and I never really had any problems setting up dev environments or doing any of the other things that Glyph discusses at length at that link. As I said above, distribution is the difficulty. The javascript "complications" about which some complain at every opportunity are only possible because distribution is so easy.

If comparing the pros and cons of two languages in response to another such comparison is "whataboutism", then I have no fucking idea what that term means.

Re:The state of JavaScript modules by omginternets on Tuesday May 30, 2017 @04:46AM (#14443775)
>If comparing the pros and cons of two languages in response to another such comparison is "whataboutism", then I have no fucking idea what that term means.

The issue at hand is not whether Python is superior to JS. Rather, we're talking about a specific problem in the JS world -- the apparent need for tooling and its so-called "dependency hell".

Bringing deployment into the conversation is whataboutism.