‘Throughout this entire ordeal where I'm uttering ridiculous epithets like “git pipe fork … ssh curl wget pip,” I keep reassuring my students that this bullshit is not intellectually interesting in any way… it's all just a necessary upfront tax required to enable them to do the actual interesting research. I've engaged in so much command-line bullshittery over the years that I can confidently assert how uninteresting it all is.‘
http://www.pgbovine.net/command-line-bullshittery.htm
Guess why I'm channeling this today 🤬.
@22 And he didn't even mention npm :)
@wim_v12e I'm going to risk inviting ridicule but in my experience, the JavaScript dev/packaging experience is much better than my experience with C++. Even npm packages packages that wrap big C/C++ libraries (SQLite, LevelDB, libsodium) inevitably just plain work.
I think the "problem" with modern JavaScript ecosystem (gulp, webpack, rollup, browserify, babel) is orthogonal to command-line bullshittery, or at least has enough of a different flavor that I think it's qualitatively different.
@22 I'm glad it works well for you. I shouldn't have picked on npm, that's just the last in a long line of command-line-tools-with-issues , and my actual recent trouble was more with yarn.
