Blend2D Reaches Beta As High Performance 2D Vector Graphics Engine

[Weasel]

I was just gonna say the opposite, too bad they wasted their time by not implementing it in a modern language like Rust.

You got it backwards, it would've been a pure waste of time if it were written in Rust.

Just like every other Rust project.

[Marc Driftmeyer]

One could have posted this straight from the web site to get an actual complete view of the library.

Blend2D is written in C++ but it provides both C and C++ APIs. Public functionality is provided through C interface so that each feature of the library is accessible to both C and C++ users. The C API makes it possible to use Blend2D from many programming languages which are able to interface with C (either natively or through FFI). The primary goal of the C++ API is to make the library easy-to-use in C++ projects without the need of managing resources manually. It is built on top of the C API and turns all objects requiring initialization and finalization into smart objects that handle it in their constructors and destructors.

[dkasak]

Good news, I heard Cairo is a major bottleneck for Inkscape. Hopefully they can use this.

Hahahahaha! Yeah yeah, I'm sure you 'heard' this ... um .... 'somewhere'. What 'major bottlenecks' do you experience in Inkscape? Do you know what's involved in rewriting a complex app to use a different graphics engine?

[Nout]

Similar interesting project: https://github.com/pcwalton/pathfinder/tree/pf3

Also it's in rust.

[rene]

No, no, horrible thing, rust everything. All the things!

I hope you know what you wish for: https://www.youtube.com/watch?v=zNipdcUh7ZE

[rene]

If it's true that it's limited to x86 and no plans to fix it asap then it can't compete with the likes of Cairo and won't ever be adopted by Qt or whatnot.

yeah well, that is what you get when you implement your own Just-in-Time compiler, …

[JonathanM]

If it's true that it's limited to x86 and no plans to fix it asap then it can't compete with the likes of Cairo and won't ever be adopted by Qt or whatnot.

A quick look at the FAQ:

Isn't Blend2D Architecture Specific?

The only architecture specific code in Blend2D is the pipeline generator which will be ported to more architectures in the future. We also plan to make it optional so that Blend2D is able to be used on platforms that do not allow JIT compilation. Software-based 2D renderers will always take advantage of architecture-specific optimizations such as SIMD to accelerate pixel and vector operations.

[cl333r]

Cross-platform but limited to x86 which might limit competition with other libs

If it's true that it's limited to x86 and no plans to fix it asap then it can't compete with the likes of Cairo and won't ever be adopted by Qt or whatnot.

[cl333r]

Good thing it's not written in Rust.

If it was we wouldn't have this issue:

Blend2D has now reached beta but there still is a lot to be worked on including multi-threaded rendering, async rendering

I wouldn't write an app in Rust but if it had to be multi-threaded from the ground up I'd certainly try doing it in Rust as it does an amazing job (like no other systems language) at telling you you're doing something wrong with your threads and data.

[ldesnogu]

Phoronix: Blend2D Reaches Beta As High Performance 2D Vector Graphics Engine

Blend2D is a a cross-platform C++ vector graphics library aiming to compete with the likes of Cairo...

Cross-platform but limited to x86 which might limit competition with other libs