Notices by Federico Mena Quintero (federicomena@mastodon.social)

Remember xbiff to get mail notifications?

Debugging an Rc<T> reference leak in #rustlang - https://people.gnome.org/~federico/blog/debugging-reference-leak-in-rust.html

Hoooooly shit, SVG 2 became Candidate Recommendation *yesterday* ‽

https://www.w3.org/TR/SVG/

New bar tape day! #MastoBikes

I decided to splurge a little while in Vancouver and got the Brooks microfiber tape. It's very nice; doesn't break when I stretch it to tension it around the bars. It's nice and thick.

Now I regret not twining the ends of my old bar tape; the raw electrical tape became really gunky and started to slide around from the sweat.

What if "do one thing and do it well" is because you can't write bigger, reliable programs in C anyway.

Boost if your first PC had a Turbo button.

We are hiring at the #gnome Foundation! https://www.gnome.org/foundation/careers/

Is there someone who could help @gnome with the #paypal API? Something is wrong with our donations page and we need help diagnosing it.

One of the local utilities is... Suse?

"#rustlang error handling is flawless", he said.

*gets a crash because he overwrote an error Result with an Ok, thus invalidating assumptions elsewhere*

It's, uh, comforting to know that we programmers will always find ways to fuck things up. The machines won't win!

Once again, rr (the debugger with backwards execution) saves my ass - https://rr-project.org/

"When did this field change?" No problem, set a watchpoint, and reverse-execute. Done, bug found.

There's an ongoing investigation of a memory leak in gnome-shell - https://gitlab.gnome.org/GNOME/gnome-shell/issues/64

And some people are making a little hurricane in a glass of water about it. GNOME doesn't give a FUCK about users; look at this PIECE OF SHIT which LEAKS MEMORY ALL THE TIME.

Memory leaks are just bugs. You can go and fix them. You can help developers investigate them. You can sit quietly if you can't help. Do not pile on developers who are already busy looking at this.

Helping Cairo - https://people.gnome.org/~federico/blog/helping-cairo.html

Librsvg 2.40.20 is out!

This is the last release I'll make in the 2.40.x series (the C-only version). It is deprecated effectively immediately: I want to avoid having unreleased commits in the 2.40 branch.

Except for (security) emergencies, people are strongly encouraged to switch to 2.41.x immediately. It is API and ABI compatible, so it is a drop-in replacement for 2.40.x.

Sometimes I boggle that to programmers, each other's computer is unusable. Different shell, or different editor, or different hotkeys for everything.

Then I remember how frustrating it is to try to cook in someone else's kitchen. Different layout, different utensils.

TFW you changed 20 files, finally the tests pass, and now you must decide how to make small commits to make sense of this mess.

Woah, PeerTube works!

So @Annalee wrote https://thebias.com/2017/10/31/disability-representation-and-the-x-men/ about how X-Men could better portray their disabilities, and it's really, really good.

Patched a bike tube, and missed a second, super-tiny hole. Patched it again. Grrrrr.

Privilege escalation in sudo because we still parse shit out of /proc: http://www.openwall.com/lists/oss-security/2017/05/30/16