Max (Lyrenhex) @lyrenhex@mastodon.lol

Apparently never did an actual #introduction so hi!

I write code (preferably Rust), play #VideoGames (RPGs, Soulsborne, and Destiny, mostly) and enjoy music. I also stream on #Twitch semi-consistently.

Also have a not-as-useful interest in Classical Latin, Ancient Greek, and etymology.

Most posts will likely relate to tech, gaming, or uni (those ones might get ranty, but I cw those!).

(See bio for most up-to-date info going forward. Cheers!)

Sun cream will forever be the bane of my existence.

When can we destroy the sun? I see no downsides. /j

Aaaaaaghhh why must my AC have kicked the bucket now of all times??

Couldn't it at least have waited till it wasn't summer?

I will never understand why it's easier to add a song to playlists on YouTube than YouTube Music...

Why must everyone else be taller than me? 😭

Have to keep adjusting seats cause my feet don't touch the floor lmfao.

lmao

https://crates.io/crates/panic-soundcloud

As some final notes:

- I'm curious as to why '+crt-static' triggers a segfault on RasPiOS-64, which was not present on -32? May look into this and do a longer write-up later. :)

- RasPiOS-32/64 = Raspberry Pi OS (32-bit) or (64-bit) respectively.

In any case, this does not affect the published build on crates.io, and the GitHub source has been fixed. Cheers!

(* might also be because I increased the drive space available, for full correctness...)

Think I've worked it out, so background: on RasPiOS-32, the Pi was unable to build the serenity library itself (out-of-memory), so I had to build the exe via cross-compilation on Desktop and scp it over.

Which meant it needed statically-linking, because different versions of some core system libraries, so `+crt-static` was added to the build flags. This appears to cause the issue.

In any case, RasPiOS-64* allows the Pi to build it natively anyway.

nevermind... That *did* make it so it doesn't instantly segfault, but it *eventually* segfaults instead.

Which makes... absolutely no sense to me. (Stack overflows are panics, no?)

Gonna stop actively posting about this issue till I get *somewhere* with it; something's bugged somewhere though...

ahahah, turns out I needed to `cargo update`. whoops.

*insert maniacal laughter as I lose my mind here*

probably a weird quirk of when I copied the workspace back over from the armv7l config.

presumably a library bug (in which case it's either Serenity or async_trait)?

... huh.

ThreadReviver ran fine on armv7l with no issues, but after recompiling for aarch64 and running on RasPiOS-64, suddenly now segfaults.

which is weird, since it's written in Rust and has no unsafe code of its own.

fun.

Anyway, if there's anything I've learned:

Hobby projects that don't serve a real purpose and probably aren't done the best are still a good learning experience. You can't get better at writing code if you don't write code ;)

Huh, sometimes you think "oh hey, computers are fast enough now that it's fine!" and that's true until the rendering engine you built for fun is limited to 15fps due to the sheer number of heap memory accesses per frame.

(This is my conclusion after looking at a project from about 4 years ago again. Neat, though, even if it does perform awfully.)

Flight Sim updates continue to be the worst experience.

It takes *forever*, and doesn't even seem to progress in the background. Aghhh.

Just told a Google Home to shut up and it started playing "Still Alive" from Portal.

... Not concerning at all...

small elaboration: the in-person exam wasn't harder *because* it was in-person (though certainly more stressful); it simply had slightly harder questions, for some reason.

(ie, the 24-hour exam had binary trees, the in-person exam had trees with arbitrary number of leaves - which is, naturally, a slightly more difficult problem)

Anyway, if anyone following me is picking their unis and wants to go into CompSci (which is great! do, it's fun imo!):

Do not pick York for CompSci. It apparently *was* great, but for the past two years it's just sucked.

Icing on the cake is they desperately want to go back to in-person exams (despite wanting to keep online teaching & insisting 24-hour exams aren't easier)...

But I don't see the fucking point? Because yeah, 24-hour exams aren't much easier (based on the one module that did go back to in-person so far, which was *slightly* harder in person for some reason) but they're less fucking stressful for everyone.

AGH.