"Rust does not have a stable ABI"
https://people.gnome.org/~federico/blog/rust-stable-abi.html [people.gnome.org]
2020-08-17 04:28
site: people.gnome.org
"Rust does not have a stable ABI"
https://people.gnome.org/~federico/blog/rust-stable-abi.html [people.gnome.org]
2020-08-17 04:28
GNOME Usability Study Report
https://people.gnome.org/~calum/usability/ut1_report/report_main.html [people.gnome.org]
2019-02-18 20:22
Sun’s GNOME usability staff in Menlo Park, California, conducted a baseline usability study of the GNOME desktop during the week of March 13-16, 2001. We recruited a dozen adult participants, each with several years of experience using computers in their work - but specifically not with backgrounds in computer science, software development or programming - to use GNOME 1.2.2 on Linux with Nautilus installed.
Kinda old, but still relevant in many ways.
source: L
Patterns of Refactoring C to Rust: The case of librsvg
https://people.gnome.org/~federico/blog/docs/fmq-refactoring-c-to-rust.pdf [people.gnome.org]
2018-12-05 20:48
A year has passed, and now we have a team of people working on the Rustification of librsvg. I want to show you how we are doing it, and some common code patterns that have emerged.
source: L
How glib-rs works, part 3: Boxed types
https://people.gnome.org/~federico/blog/how-glib-rs-works-part-3.html [people.gnome.org]
2017-09-14 00:12
But for external resources, we must tell Rust how to manage them. Again: in the case where the Rust side owns the reference to the external boxed data, we have a ForeignOwned and Drop it by free()ing it; in the case where the Rust side is just borrowing the data temporarily, we have a ForeignBorrowed and don’t touch it when we are done.
source: L
Porting a few C functions to Rust
https://people.gnome.org/~federico/news-2016-10.html#28 [people.gnome.org]
2016-11-03 06:35
Compiler enforced sanity.