Also neither of your examples do any text shaping on the GPU. Lyon doesn’t do text and Webrender (which depends on freetype) does regular old glyph cache built in CPU texture rendering. Neither involve GPU shaping.
Still trying to understand what earth-shattering, "leverage" levering feature this brings compared to Skia.
> Memory model of Rust is undefined[2]. It might be anything Rust does to accomodate C++ bindings, but I don't think they really settled on one.
> I'd like to add - people have been doing large scale parallel software development for years in C++, in spite of C++.
Do you not see at least some level of contradiction to these statements?
This is probably the more relevant explanation:
https://doc.rust-lang.org/nomicon/atomics.html.
"At very least, we can benefit from existing tooling and research around the C/C++ memory model."
> Sorry, font rendering. I thought font shaping is part of it. Pathfinder and Lyon were libs.
They don't do GPU font rendering either.
Pathfinder isn't widely used -- see my original post about "spinning wheels".
GPU font rendering hasn't demonstrated much real world value for GUIs. Where it does get used a bit is games - an industry that is overwhelmingly C++ for the foreseeable future.
> No? They are discussing Simd and generic interactions.
I was responding to this: "I'd like to add - people have been doing large scale parallel software development for years in C++, in spite of C++."
Regardless, Rust still depends entirely on the years of research and development in C++ for a memory model which is a core underpinning of parallel programming.
Ofc. Servo was shut down before anything could happen with it. Making production-ready GPU font rendering is hard.
It's not spinning wheels anymore than OSS life cycle is spinning wheels (author needs functionality X author makes a useful lib for X -> it becomes popular -> amount of work increases -> due to pressure/changes in life author abandons lib -> another author has needs functionality X -> ...)
> I was responding to this: "I'd like to add - people have been doing large scale parallel software development for years in C++, in spite of C++.
Saying Rust has issues doesn't negate C++ having massive issues but also a bigger mindshare.
https://www.reddit.com/r/rust/comments/vwdxim/announcing_lyo...
https://www.reddit.com/r/rust/comments/vwdxim/announcing_lyo...
Also neither of your examples do any text shaping on the GPU. Lyon doesn’t do text and Webrender (which depends on freetype) does regular old glyph cache built in CPU texture rendering. Neither involve GPU shaping.
https://github.com/servo/webrender/blob/master/wr_glyph_rast...
Still trying to understand what earth-shattering, "leverage" levering feature this brings compared to Skia.
> Memory model of Rust is undefined[2]. It might be anything Rust does to accomodate C++ bindings, but I don't think they really settled on one.
> I'd like to add - people have been doing large scale parallel software development for years in C++, in spite of C++.
Do you not see at least some level of contradiction to these statements?
This is probably the more relevant explanation: https://doc.rust-lang.org/nomicon/atomics.html. "At very least, we can benefit from existing tooling and research around the C/C++ memory model."
Perhaps respect your elders a bit more?