|
|
|
|
|
by KenanSulayman
2118 days ago
|
|
1. Valid point. 2. ? 3. Chrome (or more specifically CEF -- Chromium Embedded Framework, the one used by Spotify et al.) is significantly more heavy than UL. Memory use is massive. Google doesn't care about API stability and ABI breakage is so common you'll have to keep up with all API changes (the ones published and documented anyway...) to get anything done. Good luck embedding Servo! 4. ARM support is coming. --- > the others are 'community maintained'. Whatever that means. I maintain the Rust binding to Ultralight [0] via the CAPI to provide an ergonomic way for people to work with it. Adam is busy improving Ultralight itself, so I find it worthwhile to maintain it. That's what it means. [0] https://github.com/psychonautwiki/rust-ul |
|
You know, it doesn't really seem that hard to embed Servo in a Rust application [0]. It's a pretty interesting read.
Anyone know how stable Servo is for this kind of thing? It's not uninteresting as a cross-platform GUI solution or as more lightweight alternative to CEF (assuming it is more lightweight, I haven't done the science on it or anything). Given that you have total control over everything it renders, it's not massively important if it's not 100% HTML compliant or whatever.
Interesting space to watch for the future. Hopefully the Mozilla layoffs don't doom Servo.
[0]: https://github.com/paulrouget/servo-embedding-example