At least solver seems faster (if not better) in later versions? p.s. My try at 'flag in the wind' in Blender from around 2022:
https://0x0.st/s/aJ6DNj2pEHzRdBiscEIsbQ/KCsK.mp4
I do remember it took me all day to get somehow realistic motion.
Initial creator of autojump here: just use zoxide. I passed autojump mainternship to someone else a few years ago but it has now been abandoned. Rust is superior to python for this application anyway.
Switched as well, with "alias j='z'" seems to be 1:1 replacement so far. Also did 'zoxide import --from=autojump ".local/share/autojump/autojump.txt" --merge'.
I don't use autojump, but glancing over its readme it's missing nushell integration that zoxide provides.
It being a native binary instead of Python-based might also help it execute more instantaneously. Most Python-based CLI helpers that I tried add a slight but noticeable delay to simple commands, whereas zoxide is so quick it's easy to forget you even invoked a helper in the first place.
I was using autojump for years (on debian) until I lost my jump history several times in the past few months. Turns out it's a known race condition bug fixed in a newer version:
Cryptic, overly complicated syntax. for loops, if statements, etc.. are all done better in other languages.
No package manager, build, or dependency features. This means it is ugly and gross to import functions from other programming languages.
Zero data structure support, so any data manipulation is horrible.
No test support, so you can't mock and test business logic.
No debugger support.
It's just a bad, cryptic, confusing language that is hard to maintain.
Remember: it's not that you CAN'T do these things, it's that they work better in other languages, like Node or Python. And shelling out in Python or node works great and is very easy. And Python comes built into most systems these days.
It is hard to justify writing shell scrips anymore. It's like writing perl or cobol. We have better tools now, the world has moved on.
Is there a version of this that would support my custom presets for AVC/HEVC mp4 encoding with video filters like deinterlace/resize and similar (and/or audio filters like ebu R128)? (p.s. Also my usual input type is cinefrom/mov, which this one is not happy with for some reason)
Pagefind uses an index that is created ahead of time and stored as numerous files on a static site. It then downloads just the part of the index needed to complete the search. This means that you can search vastly more data than could be loaded onto a browser.
I think Pagefind is focused on the whole experience of searching pages, like with default UI widgets, easy page indexing, and handling larger sites. fuse.js seems to be a fuzzy-filter function on JS data, not handling the site integration.
Some do, mostly when the problem they are trying to solve is somewhere in my blog past. I've learned over the years not to advertise the blog/page, due to weird questions I get, for example: Q: How costly is this? (A: it's free, minus my time), Q: Why is it so ugly? (A: When you write your perfect jekyll skin, I will use it, you know it's about my future self searching for the info, not about beauty), Q: Why? (A: I always find something interesting to read in my blog, unlike your corporate page). p.s. The long-tail effect has been predicted at least 20 years ago, so I understand that views will be low or none: https://en.wikipedia.org/wiki/Long_tail
Two domain focused examples:
Blender material node: I could imagine certain material nodes to be highly annoying to script (or even represented differently than nodes), even something relatively simple like this
https://i.imgur.com/kETcJYE.png (nodes),
https://i.imgur.com/eddAhcv.png (final render)
Fusion comp node: On the other hand, this seems like a lot of blocks for this simple image:
https://i.imgur.com/ftfHngt.png
(Cool thing about Fusion is that any node can be copy/pasted to notepad as text and vise-versa)
Note: I'am neither Blender nor Fusion expert.
