Where does that come from though? I don't see any flow control or anything else compute-y in the bytecode itself. I know unpickling can run Python code, but i wouldn't say that makes the bytecode itself Turing-complete.
First - the tool in question had not been replaced. Second -discussion based on merits is one thing. Holy war is something totally different.
Personally I do not consider Rust to be a better tool but it does not matter. Each one is free to drink their own poison. I do not get obsessed about screwdrivers and I have used many.
You have written a glib and low effort reply to anything that disagrees with your Rust-maximal worldview. The sheer immaturity of Rust devs is enough to put me off the language.
That's actually a common pattern and to me that's a bit off-putting as well.
I have seen examples where some opinion gets momentum and it's repeated over and over again on the Internet even though the merit is very questionable.
Haven't looked enough into Rust to form an opinion though.
Not sure if this is related, but i'd love to see more scripting languages (mostly Python) offer facilities which let them take over from shell script for more scripts and one-liners.
Think about what it would take to write this in Python right now:
for wmv_file in $(find $1 -name '*.wmv'); do
echo -n "${wmv_file} "
ffmpeg -i $wmv_file ${wmv_file%.wmv}.mpg 2>&1 | grep kb/s: || echo "ERROR $?"
done
With a few handy variables and functions predefined, this could be something like:
for wmv_file in find(argv[1], glob="\*.wmv"):
print(wmv_file, end=" ")
result = do("ffmpeg", "-i", wmv_file, basename(wmv_file, ".wmv") + ".mpg")
if result: print(grep(str(result), "kb/s:"))
else: print("ERROR", result.status)
for wmv in Path(sys.argv[1]).rglob("\*.wmv"):
print(wmv, end=" ")
r = subprocess.run(
["ffmpeg", "-i", wmv, wmv.with_suffix(".mpg")],
stdout=subprocess.PIPE, stderr=subprocess.STDOUT,
)
lines = [l for l in r.stdout.decode().splitlines() if "kb/s:" in l]
print("\n".join(lines) if lines else f"ERROR {r.returncode}")
?
If you go outside stdlib you can use the sh library instead of subprocess.run.
Ruby does a pretty good job, with `system` and backticks. The FileUtils module actually defines some nice helpers like `mv`, `cp` and `ln_s`. So you can do `cp "/tmp/a.txt", filename`. And you can get a list of files matching a glob with `Dir["/tmp/*.txt"]`.
It's probably the sanest adaptation of the point to the metric system. A traditional point is close to a third of a millimetre, but that's too weird.
Since the Q is close to 3/4 of a traditional point, it's also quite easy to convert from traditional multiple-of-three point sizes: 9 pt -> 12 Q, 12 pt -> 16 Q, etc.
Although it's even easier just to call those 3 mm and 4 mm!
If anyone is curious and near South Kensington, there is now a little exhibition on urushi at the V&A [1], which includes a film of a guy who harvests his own sap, processes it into lacquer, and then makes things with it.
That video is not online AFAICT, but there is another one about another artist, which includes some footage of an urushi workshop preparing the stuff, and her using it: https://www.youtube.com/watch?v=xeult7lZtbg
What is going on with Japanese lacquer at the moment? There's this. There's the MSI Prestige 13 AI+ Ukiyo-e Edition [1]. The V&A opened an exhibition on it last weekend [2]. The Times had a puff piece on it a few months ago [3]. Is urushi suddenly cool? If so, why? Did the Urushi Marketing Board decide to have a big push, pull some strings, and now it's everywhere? I'm not complaining at all, just mildly puzzled.
As it happens, i saw the exhibition at the V&A today. It's decent, but small. Has a bunch of artefacts, and then some videos of some of the artists working, which are interesting.
Urushi has been going through a revival in fountain pen and watches (dials) the last five years. There is also more and more amateurs having access to urushi and learning it as a hobby.
https://www.komatsu.com/en-us/products/equipment/room-and-pi...
reply