Blend2D is a CPU-only rendering engine, so I don't think it's a fair comparison to ThorVG. If we're talking about CPU rendering, ThorVG is faster than Skia. (no idea about Blend2d) But at high resolutions, CPU rendering has serious limitations anyway. Blend2D is still more of an experimental project that JIT kills the compatiblity and Vello is not yet production-ready and webgpu only. No point of arguing fast today if it's not usable in real-world scenarios.
How JIT kills compatibility if it's only enabled on x86 and aaarch64? You can compile Blend2D without it and it would just work.
So no, it doesn't kill any compatibility - it only shows a different approach.
BTW GPU-only renderers suck, and many renderers that have GPU and CPU engines suck when GPU is not available or have bugs. Strong CPU rendering performance is just necessary for any kind of library if you want true compatibility across various platforms.
I have seen many many times broken rendering on GPU without any ability to switch to CPU. And the biggest problem is that more exotic HW you run it on, less chance that somebody would be able to fix it (talking about GPUs).
I built https://screenshot2charts.com, a tool that turns screenshots or CSV/JSON into editable charts. It solves the annoying problem of re-creating messy charts for reports and presentations, especially when all you have is a blurry screenshot of either a chart or some numbers.
From my experience, the biggest difference between vibe-coded projects that go somewhere and the ones that don’t isn’t code quality, it’s whether the builder keeps talking to users after the first version. The “vibe” gets you to ship, but iteration discipline is what turns it into something real.
I built this to scratch my own itch – in companies we use different data services that produce charts in different styles, and unifying them for reports or presentations is a pain. Sometimes you have a CSV export, sometimes just a screenshot from a dashboard, and manually recreating everything is tedious.
How it works:
- Paste a screenshot, drop a CSV or JSON, or describe what you want in text
- AI extracts the data and generates an editable chart
- For clean CSVs, it parses locally without hitting the AI
- Customize colors, themes, labels, and data directly in the browser
Customers can use Lume to do one-off mappings along with recurring mappings. As seen in the demo video, you can create a mapping between any source and target schema. So, the workflow of using Lume is the same for both one-off and recurring cases. Was this what you were referring to?
Right, also ETA would be useful. But wanted to keep it simple at first to see how it goes. Also, feel free to just fork it on GitHub and modify any way you'd like ;)
Thanks for the advice, have you used it? Any downsides to using flurry? Their website says they are free, but they must make money somehow? Is my data safe?
I've used flurry, its simple to implement and easy to generate custom events for, probably less than 15mins to basically get started.
It is free, I assume your data is safe. They do other services outside of analytics, such as ad trafficking etc., which I assume is how they make their money.
Thanks for that info,just signed up to flurry this morning. Currently reading up on events and their importance in iOS analytics. Is it worth integrating them at the beginning or should I wait to see what I should track before putting events in?It seems like flurry will give me all the data I need with or without events?
The very basic use of Flurry is the most important and unless you have some very important event you need to track then I wouldn't worry about it to start. One case I needed to use custom events was when I had a big operation that could be canceled out of within the app. I used custom events to track how many people started compared to finished which was helpful.
Open-source vector engine with GPU backends (WebGPU, OpenGL), runs on microcontrollers to browsers. Now a Linux Foundation project.
https://github.com/thorvg/thorvg
(Disclosure: CTO at LottieFiles, we build and maintain ThorVG in-house, with community contributions from individuals and companies like Canva)
reply