Lariv VS Graphite

Just finished epoch inserts on Lariv, which somehow I managed to implement as a zero-cost abstraction. Currently I'm trying to fix the use-after-free vulnerability I found on the O(1) accesses implementation without sacrificing any performance.

Optimizing lariv, but I don't think there's much to do left. I have some ideas I'll try out, but that's it.

Implementing O(1) get() & remove() speeds on Lariv, a thread-safe vector with lots of quirks.

I just finished my abomination, a linked atomic random insert vector. https://github.com/Alonely0/Lariv

There is also Graphite (https://graphite.rs/) which, unlike Gimp, has a modern architecture and very ambitious goals (Blender for 2D basically).

If you're interested in either computational geometry, layout/packing/constraints, or functional programming language concepts, those are all the math-related concepts that we're currently interacting with for Graphite, a 2D vector graphics editor that's aiming to become the next Blender (but for 2D instead of 3D). If that sounds interesting, I'd love to help get you started if you want to join our Discord and I can explain the math-related work that we need to get done. Cheers!

Not sure which web-based spreadsheet app you're talking about, because there are many that do use these frameworks. Here's a PS/AI clone built with a Svelte frontend: https://graphite.rs

Wanted to contribute to a good Rust-based project last week, started searching and found a good Reddit thread featuring several great projects. Looked at and found Graphite. I liked the concept though I know almost nothing about graphic design.

I'm currently trying to decide on the SD server to deploy with Graphite, both for running locally (with Tauri desktop builds) and for us to host on a server for users.