I'd definitely incorporate it into my projects if it were ported Go, Rust, or any reasonable redistributable form, and continued to use a BSD license.
Way clearer than cryptic sed and awk one-liners! Big kudos to you for making this and sharing it with the world!
Python apps which are more than a single script are a non-starter for me. It's a big pain to get everyone on my 120+ person dev team to install it properly, they're all over the place with regard to environments. "Oops, I'm on Python 3.4", or python 2.6, or "I use this other python path"; it's inevitably a headache.
> if it were ported Go, Rust, or any reasonable redistributable form
I still consider Perl being, from the portability standpoint, the best language to pre-process a single text line that should be translated to a Perl one-liner which is then executed.
I wish I could disagree, but your point is true. Hopefully soon the python 2 vs 3 disease will be mostly cured, but right now anyone not currently using python3 is unlikely to use bsed given that the value is convenience and simplicity--a value nullified by any install frustrations.
One can have “experience” with something, and not “know” it.
Could just as easy say: “I have experience in scenarios where I must use python or run its scripts in an evironment, and it has been a headache, but I can’t say I dislike the language because I haven’t needed to explicitly create programswith it.”
Sure. But the way yoklov wrote it, I thought he meant that Python is objectively bad for this use case, which you cant know without knowing the language.
Python apps which are more than a single script are a non-starter for me. It's a big pain to get everyone on my 120+ person dev team to install it properly, they're all over the place with regard to environments. "Oops, I'm on Python 3.4", or python 2.6, or "I use this other python path"; it's inevitably a headache.