vello VS zotero

I'm looking forward to doing careful benchmarking, as this renderer absolutely looks like it will be competitive. It turns out that is really hard to do, if you want meaningful results.

My initial take is that performance will be pretty dependent on hardware, in particular support for pixel local storage[1]. From what I've seen so far, Apple Silicon is the sweet spot, as there is hardware support for binning and sorting to tiles, and then asking for fragment shader execution to be serialized within a tile works well. On other hardware, I expect the cost of serializing those invocations to be much higher.

One reason we haven't done deep benchmarking on the Vello side is that our performance story is far from done. We know one current issue is the use of device atomics for aggregating bounding boxes. We have a prototype implementation [2] that uses monoids for segmented reduction. Additionally, we plan to do f16 math (which should be a major win especially on mobile), as well as using subgroups for various prefix sum steps (subgroups are in the process of landing in WebGPU[3]).

Overall, I'm thrilled to see this released as open source, and that there's so much activity in fast GPU vector graphics rendering. I'd love to see a future in which CPU path rendering is seen as being behind the times, and this moves us closer to that future.

[1]: https://dawn.googlesource.com/dawn/+/refs/heads/main/docs/da...

[2]: https://github.com/linebender/vello/issues/259

[3]: https://github.com/gpuweb/gpuweb/issues/4306

Dioxus is working on this with blitz. It's leveraging wgpu through the linebender group's Vello renderer. Still in early stages.

If you're doing advanced compute work (including lock-free data structures), then it's best effort.

https://github.com/linebender/vello/issues/42 is an issue from when Vello (then piet-gpu) had a single-pass prefix sum algorithm. Looking back, I'm fairly confident that it's a shader translation issue and that it wouldn't work with MoltenVK either, but we stopped investigating when we moved to a more robustly portable approach.

There are a number of up-and-coming Rust-based frameworks in this niche:

- https://github.com/iced-rs/iced (probably the most usable today)

- https://github.com/vizia/vizia

- https://github.com/marc2332/freya

- https://github.com/linebender/xilem (currently very incomplete but exciting because it's from a team with a strong track record)

What is also exciting to me is that the Rust GUI ecosystem is in many cases building itself up with modular libraries. So while we have umpteen competing frameworks they are to a large degree all building and collaborating on the same foundations. For example, we have:

- https://github.com/rust-windowing/winit (cross-platform window creation)

- https://github.com/gfx-rs/wgpu (abstraction on top of vulkan/metal/dx12)

- https://github.com/linebender/vello (a canvas like imperative drawing API on top of wgpu)

- https://github.com/DioxusLabs/taffy (UI layout algorithms)

- https://github.com/pop-os/cosmic-text (text rendering and editing)

- https://github.com/AccessKit/accesskit (cross-platform accessibility APIs)

In many cases there a see https://blessed.rs/crates#section-graphics-subsection-gui for a more complete list of frameworks and foundational libraries)

blessed.rs lists these three crates for 2D drawing: - https://lib.rs/crates/femtovg - https://lib.rs/crates/skia-safe - https://github.com/linebender/vello

Vello (https://github.com/linebender/vello) which uses wgpu to render Edit: just saw you require images. Vello doesn't support those yet

How does this relate to Vello? Both target raw-window-handle for winit compatibility. Vello uses WGPU vs piet-glow using GL.

Finally, maybe vello could help you with ideas. It's not production ready yet, but they have some interesting ideas for 2D rendering using wgpu.

Maybe try Zotero[1]. There are many addons which can do what you need.

[1]https://www.zotero.org/

And next time, you use a real literature management program like zotero (some university libraries offer classes, there is a r/zotero, etc) or jabref to create a proper bibtex file with the references. It is not that difficult, and keeps you sane (esp. if a paper has to be formatted for a different publisher). See e.g. learnlatex.

Zotero | Remote | Full-Time or Part-Time | https://www.zotero.org

Zotero is an open-source project that develops software to help people collect, organize, annotate, cite, and share their research. Our software is recommended by most universities and used by millions of students, scholars, scientists, and researchers worldwide.

We're looking for a JavaScript developer to work on Zotero "translators" — the pieces of code that let people click a button in their browser toolbar on any webpage and save high-quality metadata and files to their Zotero libraries. If you like web scraping, APIs, data formats, and exploring sites in the browser devtools, this would be up your alley. As a core Zotero developer, you'll also have the ability to work across Zotero's vast ecosystem and help shape the future of the project.

This is an open-ended contract role that can scale up and down in hours based on availability and workload.

https://www.zotero.org/jobs

Zotero is your answer, it even auto generates your citations.

https://www.zotero.org/

Apparently there are plugins for Logseq and Obsidian as well.

Zotero - Price: Free Free and open-source reference manager that helps you collect, organize, and cite your research sources.

I use the free and open source Zotero which I think you'd find very calibre-like and manage notes and concept linking with org-roam in emacs.

If you can't hold the urge to know, you can check on the Zotero web library if all of your things are still there

Resources: ZOTERO. Zotero is a free (you can pay to get more storage), open-source citation manager with optional browser plugins. IT WILL FORMAT CITATIONS FOR YOU. (sometimes you have to edit them, but most of the time it can pull metadata and format things correctly on its own). You can sort your references into folders or with tags, read and annotate PDF copies on your computer or in a mobile app, and make notes - which I used to keep track of specific quotations I wanted to use.

You can also use online resources like The Encyclopedia of Archaeological Sciences, that I think is mostly free or the Handbook of Archaeological Sciences which I think is also mostly free. If you can't get a hold of those things you can also email the authors/editors and they might send you a free copy or look them up on Academia.edu and see if they have a free version. Also, if you don't already, use Google Scholar, it's the best resource for finding free articles and topics to read. It's also never too early to start using something like Zotaro, Mendeley, or Endnote to keep track of your readings and help you with citations/references in papers. You can literally download the citation, import it into one of those systems and it automatically formats your referencing.