61–70 of 187 posts
Earlier quoted context omitted.
> Color and terminal graphics are the work of the devil. Or you know, it's 2016, and it's npm who does it badly.
I don't even want color and terminal graphics done goodly. I code with two monochrome terminals on the screen using vim and the command line.
The funky progress bar is about the coolest thing with npm. They could let it take a minute if they wanted too and i would keep watching it with amazement.
Your statement captures my feeling of node.js developers quite well.
Earlier quoted context omitted.
https://www.youtube.com/watch?v=elWIVKWhWTk
I see that with iTerm 2, but using Terminal gives me a very different experience. Here's a side-by-side: https://youtu.be/odoVfHHBYVM Until recently, I had no clue iTerm was doing something weird. I just figured npm install was just ugly and incomprehensible.
Earlier quoted context omitted.
Please refrain from adding unhelpful comments to the issue.
It is tremendously unfortunate that that needs to be said at all.
* Nontechnical: I would like to express my eagerness that the bug be fixed or request its priority be increased, but don't have any additional technical information to add
* Technical: I have useful technical information to add, beyond what is already in the bug
Then "Nontechnical" type comments would be hidden from the developers by default (unless they specifically ask to see them), but their count could be used as a bug prioritisation mechanism (effectively leaving a "Nontechnical" type comment would be counted the same as a vote)
Earlier quoted context omitted.
Here are details from the docs: https://docs.npmjs.com/how-npm-works/npm3-nondet
> You can reliably get the same dependency tree by removing your node_modules directory and running npm install whenever you make a change to your package.json. https://docs.npmjs.com/how-npm-works/npm3-nondet
Earlier quoted context omitted.
It is tremendously unfortunate that that needs to be said at all.
I guess it's GitHub's Eternal September. I'm all for more people having access to development tools, but GitHub really has to step up the tools available for managing issues/comments.
Earlier quoted context omitted.
That's exactly my experience. Once I wrote some naive PE solution in nodejs and added some logging at each step. After few minutes and far from a solution I stopped it and disabled logging. I got the solution within seconds. The diff was few orders of magnitude, which was pretty surprising for me.
Sometimes writing to the terminal can be the slowest part because it's unbuffered by default in an interactive prompt, so even just redirecting stdout to /dev/null (or even a file) can be faster. Had that happen some ten years ago, so my explanation could be out of date or misremembered but the effect was real.
On the other hand if you didn't do this, then interactive terminal programs would be entirely unusable.
Earlier quoted context omitted.
Awesome tool, but wish the url was a bit easier to spell/remember!
I'm not sure "IED" is the best acronym to go for, either: https://en.wikipedia.org/wiki/Improvised_explosive_device
https://github.com/alexanderGugel/ied/pull/45#issuecomment-1...
> Thanks, but I'm not going to rename this project anytime soon.