tropy VS flexible-vectors

Yeah, I just stumbled upon this project and wanted to share, I'm currently using Obsidian for my personal wiki, but I use Zotero a lot as a paper repo and reader, the organization and metadata tools are great, and extending it to a more powerful note-taking tool seems like a no-brainer.

Now it just needs an EPUB reader to replace Calibre, then it'd just be the perfect all-in-one personal library. For now I'm using this plugin that exports and keeps in sync the calibre library to Zotero:

https://www.mobileread.com/forums/showthread.php?p=3339191

Very grateful that this open source project stays alive, I've seen attempts over the years from startups and other projects to tackle on spaces like pkm, research, paperless office, to then be abandoned yet Zotero keeps getting updates.

There's also Tropy, from the same organization that develops Zotero, for organizing digital assets:

https://tropy.org/

Getting a bit off-topic, but this thing could use some sort of Moodboard designer to visually sort the assets in a canvas, kind of what you can do with Miro, Notion, Mural or locally with Obsidian Canvas/Excalidraw. On that note,

here: https://tropy.org/

I'm personally a big fan of digitizing as you go, since that is ultimately what is going to make the images the most accessible for you and your family. Even if you aren't going to make high resolution scans, a cell phone image of the photo provides a great opportunity to compile notes and related resources in a more accessible digital format. A resource I can highly recommend is called Tropy (https://tropy.org/), a free program created specifically to assist in organizing and arranging photographs and research notes. You can include granular information such as the box and folder the item is located in, transcriptions and captions for the images, and even tag and link related materials (such as tagging by surname, linking census records, and grouping images together like pages of a photo album or front and back of documents).

One idea to store pictures of an analog Zettelkasten: Tropy - it's a side project to Zotero. https://tropy.org/

So if you like an image, save it somewhere together with the prompt. I'm using Lightroom. Tropy is a free option that should be good too.

For private annotation w.r.t. research, Tropy might be a good tool, although it's desktop only: https://tropy.org/

Wonderful language. Only complaint (so far) : SIMD should be named Vector and dispatched to whatever SIMD/vector pipeline the host offers, similar to Flexible Vectors proposal in WASM: https://github.com/WebAssembly/flexible-vectors/blob/main/pr...

Abstract vectorization instructions in wasm will make life a lot easier

https://github.com/WebAssembly/flexible-vectors/blob/main/pr... great proposal!

Mapping to whatever hardware is available as some sort of micro library

I think SIMD was a distraction to our conversation, most code doesn't use it and in the future the length agnostic, flexible vectors; https://github.com/WebAssembly/flexible-vectors/blob/master/... are a better solution. They are a lot like RVV; https://github.com/riscv/riscv-v-spec, research around vector processing is why RISC-V exists in the first place!

I was trying to find the smallest Rust Wasm interpreters I could find, I should have read the source first, I only really use wasmtime, but this one looks very interesting, zero deps, zero unsafe.

16.5kloc of Rust https://github.com/rhysd/wain

The most complete wasm env for small devices is wasm3

20kloc of C https://github.com/wasm3/wasm3

I get what you are saying as to be so small that there isn't a place of bugs to hide.

> “There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.” CAR Hoare

Even a 100 line program can't be guaranteed to be free of bugs. These programs need embedded tests to ensure that the layer below them is functioning as intended. They cannot and should not run open loop. Speaking of 300+ reimplementations, I am sure that RISC-V has already exceeded that. The smallest readable implementation is like 200 lines of code; https://github.com/BrunoLevy/learn-fpga/blob/master/FemtoRV/...

I don't think Wasm suffers from the base extension issue you bring up. It will get larger, but 1.0 has the right algebraic properties to be useful forever. Wasm does require an environment, for archival purposes that environment should be written in Wasm, with api for instantiating more envs passed into the first env. There are two solutions to the Wasm generating and calling Wasm problem. First would be a trampoline, where one returns Wasm from the first Wasm program which is then re-instantiated by the outer env. The other would be to pass in the api to create new Wasm envs over existing memory buffers.

See, https://copy.sh/v86/

MS-DOS, NES or C64 are useful for archival purposes because they are dead, frozen in time along with a large corpus of software. But there is a ton of complexity in implementing those systems with enough fidelity to run software.

Lua, Typed Assembly; https://en.wikipedia.org/wiki/Typed_assembly_language and Sector Lisp; https://github.com/jart/sectorlisp seem to have the right minimalism and compactness for archival purposes. Maybe it is sectorlisp+rv32+wasm.

If there are directions you would like Wasm to go, I really recommend attending the Wasm CG meetings.

https://github.com/WebAssembly/meetings

When it comes to an archival system, I'd like it to be able to run anything from an era, not just specially crafted binaries. I think Wasm meets that goal.

https://gist.github.com/dabeaz/7d8838b54dba5006c58a40fc28da9...

Thanks! Good points, I think in general the fixed-width "packed" SIMD ISAs have the downsides that you mentioned.

But it seems that WebAssembly doesn't have length-agnostic SIMD instructions yet. There is an open proposal to add this though: https://github.com/WebAssembly/flexible-vectors