differential-dataflow VS femtovg

Some recent solutions to this problem include Differential Dataflow and Materialize. It would be neat if postgres adopted something similar for live-updating materialized views.

https://github.com/timelydataflow/differential-dataflow

https://materialize.com/

I'm looking for this but can't find it, how does this project compare to differential dataflow?

As a sibling commenter mentioned, it's built on timely dataflow (which is lower-level), but that already has differential dataflow[0] built on top of it by the same authors.

How do they differ?

[0]: https://github.com/TimelyDataflow/differential-dataflow

hi! sujay from convex here. I remember reading about your "reverse query engine" when we were getting started last year and really liking that framing of the broadcast problem here.

as james mentions, we entirely re-run the javascript function whenever we detect any of its inputs change. incrementality at this layer would be very difficult, since we're dealing with a general purpose programming language. also, since we fully sandbox and determinize these javascript "queries," the majority of the cost is in accessing the database.

eventually, I'd like to explore "reverse query execution" on the boundary between javascript and the underlying data using an approach like differential dataflow [1]. the materialize folks [2] have made a lot of progress applying it for OLAP and readyset [3] is using similar techniques for OLTP.

[1] https://github.com/TimelyDataflow/differential-dataflow

[2] https://materialize.com/

[3] https://readyset.io/

differential dataflow which is used to power materialize db

It's partially inspired by Linq, so the similarity you see is expected.

It's not really arbitrary structures so much, though you're mostly free in what record type you use in a relation (structs and tagged enums are typical, though).

The incremental part is that you can feed it changes to the input (additions/retractions of facts) and get changes to the outputs back with low latency (you can alternatively just use it to keep an index up-to-date, where you can quickly look up based on a key (like a materialized view in SQL)).

This [0] section in the readme of the underlying incremental dataflow framework may help get the concept across, but feel free to follow up if you're still not seeing the incrementality.

[0]: https://github.com/TimelyDataflow/differential-dataflow#an-e...

Femtovg (https://github.com/femtovg/femtovg) which uses OpenGL to render

Congrats! I don't want to diminish the accomplishment, but have you seen femtovg? It seems like it's probably well-aligned with your needs.

I'm currently using femtovg for vector graphics in my games, and I would like to get into bevy by porting one of my game prototypes using it to bevy.

I use femtovg It's a simple vector graphics engine having all the important features you probably want from a 2D rendering engine: simple shapes, images, text

https://github.com/femtovg/femtovg/pull/5

Before Power10 was done, IBM actually asked us Raptor users about proposals for useful machine code instructions to add to it. I replied that I’d like to have hardware UTF-8 de-/encoding but they wanted a more detailed proposal and I never got around to write it. I’m not even sure that this would be worthwhile, but I see UTF-8 de-/encoding everywhere in the code I write and would like it to approach memory read/write speeds.

I was very disappointed to learn that they had gone more proprietary with Power10 so I would not have been able to use those instructions anyway. What a pity!

In my actual code, I'm using a library called femtovg that is a Rust port of a C library for 2D rendering. But In the blog post I kept the example simple to keep it relevant for people who might want to use Web Workers + WASM for other things; didn't want to get hung up on femtovg for someone who had never heard of it. As you say, if you all you need to do is basic 2D manipulations of a canvas that are supported by the native API, then you likely don't need WASM.

You guys should also check out the femtovg project, a 2D rendering API that sixty fps relies on.

https://github.com/femtovg/femtovg

It's a decent starting point for trying to build your own toolkit.

I have recently added a wgpu backend but for now it lives in my fork https://github.com/adamnemecek/femtovg

run the demo with `cargo run --example wgpu_demo --release`.

Also join the femtovg discord https://discord.gg/V69VdVu

I'm involved with the femtovg project. We are definitely looking for contributors. Join the discord channel.

It's not a GUI framework but I'm involved with this project called femtovg, it's a Rust nanovg port. I've recently added a wgpu backend. Run the demo with cargo run --example wgpu_demo --release. Some people have been using it for their own UIs, e.g. tuix. I think that you should consider rolling your own GUI toolkit, it's not that bad and you'll appreciate the control.