Federico's Blog

I have started a little experiment in porting bits of the widely-used bzip2/bzlib to Rust.

Traditionally, GObject implementations in C are mutable: you instantiate a GObject and then change its state via method calls.

After the librsvg team finished the rustification of librsvg's main library, I wanted to start porting the high-level test suite to Rust.

One of the pain points in trying to make the Meson build system work with Rust and Cargo is Cargo's use of build scripts, i.e. the build.rs that many Rust programs use for doing things before the main build.

Authors by lines of code, each year: Authors by percentage of lines of code, each year: Which lines of code remain each year?

The other day I wrote about how most of librsvg's library code is in Rust now.

Since a few days ago, librsvg's library implementation is almost 100% Rust code.

Dos mesitas de noche: Parte 1: Preparar las piezas Parte 2: Marcar las patas Parte 3: Los cajones En la parte 1 preparé la madera para todas las piezas principales de las mesitas de noche / burós.

Dos mesitas de noche: Parte 1: Preparar las piezas Parte 2: Marcar las patas Parte 3: Los cajones Hace unos años hice una mesita de noche para mi esposa.

Al igual que hice con mi blog principal hace un par de años, acabo de mover La Viruta Rebelde al motor de Pelican.

Last night, the linux.org DNS was hijacked and redirected to a page that doxed her.

I just realized that I forgot to publish my presentation from this year's GUADEC.

While in the middle of converting librsvg's code that processes XML from C to Rust, I went into a digression that has to do with the way librsvg decides which files are allowed to be referenced from within an SVG.

A couple of weeks ago we had the fourth GNOME+Rust hackfest, this time in Thessaloniki, Greece.

Lately, I have been converting the code in librsvg that handles XML from C to Rust.

I want to write a braindump on the stuff that I remember from gdk-pixbuf's history.

The bug that caused two brown-paper-bag released in librsvg — because it was leaking all the SVG nodes — has been interesting.

Over in this issue we are discussing how to add debug logging for librsvg.

I am incredibly happy because of three big things that are going on in librsvg right now: Paolo Borelli finished porting all the CSS properties to Rust.

Our graphics stack that deals with images has evolved a lot over the years.

The last code I wrote during the hackfest was the start of code generation for GObject interfaces.

Hacking on gnome-class continues apace!

I'm in Madrid since Monday, at the third GNOME+Rust hackfest!

I have started porting the code in librsvg that parses SVG's CSS properties from C to Rust.

Gitlab has a fairly conventional Continuous Integration system: you push some commits, the CI pipelines build the code and presumably run the test suite, and later you can know if this succeeded of failed.

I would like to mentor people for librsvg and gnome-class this Summer, both for Outreachy and Summer of Code.

Cairo needs help.

Today I ported gnome-class from version 0.11 of the syn crate to version 0.12. syn is a somewhat esoteric crate that you use to parse Rust code... from a stream of tokens... from within the implementation of a procedural macro.

Jordan Petridis has been kicking ass by overhauling librsvg's continous integration (CI) pipeline.

I have started an RFC to integrate rsvg-rs into librsvg. rsvg-rs is the Rust binding to librsvg.

Librsvg feels like it is reaching a tipping point, where suddenly it seems like it would be easier to just port some major parts from C to Rust than to just add accessors for them.

As a library writer, it feels a bit strange, but refreshing, to write a program that actually has a main() function.

Librsvg 2.42.0 came out with a rather major performance regression compared to 2.40.20: SVGs with many transform attributes would slow it down.

Would you like to help fix a couple of bugs in librsvg, in preparation for the 2.42.1 release?

One nice thing about gitlab.gnome.org is that we can now have Continuous Integration (CI) enabled for projects there.

I'm loving gitlab.gnome.org.

Today I released librsvg 2.40.20.

Librsvg now lives in GNOME's Gitlab instance.

Porting of librsvg to Rust goes on.

Recently on the Greater than Code podcast there was an episode called "Code Hospitality", by Nadia Odunayo.

Last weekend I was in Berlin for the second Rust+GNOME Hackfest, kindly hosted at the Kinvolk office.

Here is a little Emacs Lisp snippet that I've started using.

(First part of the series, with index to all the articles) Now let's get on and see how glib-rs handles boxed types.

The initial articles about librsvg's conversion to Rust are in my old blog, so they may be a bit hard to find from this new blog.

Before continuing with the glib-rs architecture, let's take a detour and look at GObject Introspection.

Today I released librsvg 2.41.1, and it's a big release!

(First part of the series, with index to all the articles) In the first part, we saw how glib-rs provides the FromGlib and ToGlib traits to let Rust code convert from/to Glib's simple types, like to convert from a Glib gboolean to a Rust bool and vice-ver…

How Glib-rs works, part 1: Type conversions How Glib-rs works, part 2: Transferring lists and arrays How Glib-rs works, part 3: Boxed types During the GNOME+Rust hackfest in Mexico City, Niko Matsakis started the implementation of gnome-class, a procedural

Rust tries to follow the "make illegal states unrepresentable" mantra in several ways.

During GUADEC this year I gave a presentation called Replacing C library code with Rust: what I learned with librsvg.