Sergey Bugaev @bugaevc@mastodon.technology

I kinda wish #objc / #Swift had a garbage collector in debug mode, not the usual kind for freeing memory (Apple already tried that...) — but one that would detect memory lost to strong reference cycles.

Kind of like Valgrind, but with more insight into the language ("this view controller instance is kept alive because you've implicitly captured a strong reference to self in this block, which is strongly referenced by this view model, which is stored in a property of the same view controller").

So here's something pretty cool I wrote ≈ 2 years ago.

A toy toolkit in C, using #Wayland + Cairo, inspired by #GTK 3. No GObject or overly fancy OOP, no pervasive boxing either.

It can do windowing (with CSD, resizing and proper cursors), boxes (widgets that multiplex several child widgets), buttons (render a border, emit a callback when clicked) and labels (render text). Widgets can define their sizing constraints (min width, min height) & it's propagated through the tree.

Not much else.

Joel Spolsky on C: "I'm a big fan of C — but I think nobody should ever code anything in C. It's simply not possible to use C safely."

Matches my feeling about C exactly.

(Translated from German by Google, so the exact words may differ.)

Attended another local #Rust meetup, this time together with @YaLTeR, and my fsck-sda1-ing God, if there's something that brings real joy to my life, it's these meetups. And no, I'm not overreacting.

Thanks everyone! 😀😀

So here's a thing

Rather than porting their code from #Python 2 to Python 3, #Facebook could just spend the time rewriting it in #Rust 😉

#py3 #rustlang #RiiR #enrastigu

Me & @YaLTeR at our bachelor's graduation ceremony

I have *no idea* how specifying build script dependencies inside that very build script works (in order for this build script to have any effect, you need to run it, and to run it you'd need the dependencies to already be in the class path, but it can't know the list of dependencies until it evaluates the script...). And that's just one of the things that makes me feel like I'm not in control.

Gradle build scans sound interesting, but I don't get it, am I supposed to upload my local scan data to their servers in order to view it? How about no?

Overall, I'm glad Gradle is *the* build system to use for Android these days (with it being the default in the Android studio, Google and Gradle working together on the Android Gradle plugin optimization and so on).

With all of its dark spots, it runs circles around xcodebuild, anyway.

Spent the day fighting #Gradle.

You know, it's actually a pretty nice tool, and you can get very fast builds of you know what you're doing (I think I can even get my toy Android app to build in seconds, rather than tens of minutes, after a one-line change? but we'll have to wait until I get home).

But God is it user-hostile! I don't think I've had this much trouble even with CMake we use in Darling (thankfully I have zero experience with autotools).