Show newer

Gtk-rs had a release!!!!! gtk-rs.org/blog/2019/02/21/new

This means I can now merge the all-the-gobject-crap-in-rust branch to librsvg.

This paper on a malloc() replacement that DOES COMPACTION even on C/C++ is making the rounds: arxiv.org/pdf/1902.04738.pdf

Scarily beautiful.

@federicomena Cairo only has two, and if C had generics it would only be one. What's the reason in librsvg? :)

"In retrospect, it’s unsurprising that a lot of New Atheism devolved into reactionary, antifeminist, and even white supremacist thought, because it was never really about the things it claimed to be about. The dominant affect of New Atheism wasn’t humility, or reflexivity, or curiosity, all the things one truly needs to improve intellectually. It was smugness."

The Magical Thinking of Guys Who Love Logic: theoutline.com/post/7083/the-m

@mathieu @federicomena That's for someone to do who cares and knows about IBus though, not me :)

Same thing goes for GTK. I'd be happy to help but this is something for people to do who actually know about the library in question and use it.

@mathieu @federicomena Ask on IRC if you don't understand anything :)

I don't have updating the gir PR on my list, that's for someone else to take up. It won't be possible to use that for most parts of GStreamer anyway as its APIs are a bit special (and can be mapped to nicer Rust than gobject-introspection can possibly express).

@mathieu @federicomena No it's not yet. A PR for an older version is available here github.com/gtk-rs/gir/pull/604 but needs to be updated.

@federicomena 1/2 is probably build system stuff then, that issupposesd to work :) see my gobject-example-rs repo. And you wouldn't be able to call it from your C code otherwise either. Must be the final linking.

3 if you mark the function pub then it is exported. Plus no_mangle so you can actually know the name too

4 panics as we discussed :) those guards we do in C are landmines

@federicomena I was wondering why you have all the C functions still but they only directly call the Rust function and nothing else. Build system related reasons?

@federicomena Oh I see, `rsvg_sax_error_cb` is the culprit. Annoying!

@federicomena Which one is that? What is it good for?

You might be able to handle it with doc.rust-lang.org/std/ffi/stru (nightly-only), but this sucks.

TL;DR of the blog post I'm writing - if part of the Unix philosophy is communicating via environment variables and stringly-typed stdin/stdout, it's a pretty shitty philosophy.

I guess the way of thinking about crashes/bugs has changed.

It used to be, garbage in, garbage out. "Sure, it crashed because you gave it a corrupted file; don't do that".

Then it was about making software robust. "Let's try not to crash with corrupted files".

Then it was about making software secure. "Files may actually be malicious, from the internet".

People these days basically make it a sport of finding vulnerabilities based on random memory safety bugs.

My god, seriously, if you have anything for maps, go see these public-domain equal-earth ones:

Physical: equal-earth.com/physical/
Political: equal-earth.com/

Printable at over 1 meter wide at 300 DPI.

These are by Tom Patterson, a highly, highly skilled cartographer. #gis

Show older
Toot.Cat

On the internet, everyone knows you're a cat — and that's totally okay.