Hacker News Reader

Comment by high_priest | Hacker News Reader

These are, in majority, ffmpeg abstractions. WHY in tarnation would you need Node.js as a basic dependency?

I love the concept. But seriously, Node.js for an FFMPEG wrapper? Really?

Maybe it was made to scratch an itch and the developer is most comfortable in JS. Why judge someone else who made something and shared it without asking for anything in return?

Why judge someone who sh*t in the middle of a park without asking for anything in return?

This is a bs analogy.

You can just ignore this if you don't care for how it's built. This kind of comment is just gatekeeping and makes people less likely to listen to you.

If you think there's a better way and you want people to get there, give constructive feedback. That's the only valid option.

Given that it’s a wrapper to make ffmpeg more user friendly, I don’t see the problem.

npm has a lot of tools that make creating CLI tools a breeze. For example there’s Listr and the more generic Ink (“React for CLI”)

Here are the node dependencies. Am I ignorant to assume these make CLI interaction more developer friendly?

    "execa": "^4.0.3",
    "glob": "^7.1.6",
    "mkdirp": "^1.0.4",
    "moment": "^2.29.1",
    "nopt": "^5.0.0",
    "npmlog": "^4.1.2",
    "nyc": "^15.1.0",
    "p-all": "^3.0.0",
    "rimraf": "^3.0.2",
    "tape": "^5.0.1",
    "unique-slug": "^2.0.2",
    "which": "^2.0.2"

Sorry for any basterdized formatting. OM

glob is for globbing https://linuxhint.com/bash_globbing_tutorial/

hehehe this comment made me chuckle. Thanks for being kind and sharing. It’s just that’s the most obvious one

Reply on news.ycombinator.com