@kirby I still have my DSi — and Korg DS-10 still works perfectly on it. It also has Super Mario and GTA — so you can entertain yourself while sitting on a toilet :marseyemojismilemouthtighteyes:
@p No, your memory deceives you. Newer PowerPCs are little-endian — and that is the architecture still supported by a lot of distros, unlike BE. 64 PowerPC CPUs could switch endian-ness too: https://en.wikipedia.org/wiki/PowerPC#Endian_modes That G5 just doesn't support it, at least I've never seen it done on real hardware and doing so would be trouble anyway as old Apple's OpenFirmware surely doesn't support that. ppc64le is even supported by the reference Go toolchain, again, unlike BE — which is supported by gccgo though, but there's little use in it as most modules do not support that anyway and you'd have to do a lot of work porting those too. I think I've even succeeded building gccgo for 32-bit PowerPC, which is no longer possible as it looks like some definitions got removed from gcc's source. You can in theory add those back of course, but like I already said — there'd be little use in it as most modules won't work as is anyway.
Unlike Rust BTW! Which works on nearly anything and the kitchen sink, here's the machine this instance runs on. And it's probably a relatively recent version even. I'm not even that sure that RISC-V machines aren't supported — they are probably worse supported than more mainstream architectures and have a similar problem — even more mainstream modules won't work. I have this problem on PowerPC too, e.g. ring is a pretty popular cryptography crate, but it can't even be built as is. IBM made a series of patches so it's possible for ppc64le and with a little effort I could make it build on this 32-bit machine even, but autotests still fail — looks like there are more underlying issues. I originally started these effort with intent to host libreddit — but as Reddit went to shit anyway, I've just given up :marseyshrug:
@kirby Programming projects? Last weekend I realized how to fix the "address already in use error" I'm getting when attempting to use the Gemini server that I run for IPv6 ports. Just from reading about the "ipv6only" flag that was used to describe ports in nginx and how the defaults changed in the recent versions and why. Turns out that on older kernel you had to use a certain flag when opening sockets to make it IPv6 only — that's it, five extra lines of code and it works, now my server is dual stack without the stupid ssh-based port redirect that I had to use before. And yet I have spent half of yesterday to restore my phone to working condition after a bad update that I have installed by accident. To be fair, I didn't do much — most of the parts that made it possible to work were already there, the developer of original project made it open two sockets already, he just didn't use proper flags to make it work on older kernels — like the one that powers the machine where my Gemini server is hosted… And yet, the fact that fixing something that looks relatively advanced takes so little time, but fixing something that seems so trivial — so much, makes me shudder. I fucking hate modern computing and all this complexity :marseyraging:
@kaia See the whole Nibelung Ring cycle when you have the opportunity — it will take you half a week, every evening :marseysmug2: I'm not even sure they stage it in full like that these days — seems like too much trouble and people, even the operagoers are into shorter pieces now.
@ChristopherBRobin I like the way their ears are barely protruding from their heads, any idea why they are like that? Probably gives them some survival advantage, but I can't quite grasp what exactly that is :marseyemojismilemoutheyes:
@bot@theorytoe IRL people aren't much different, I think a lot of people just have wrong expectations for friendship, love and social interaction in general, eventually they get disappointed and this leads to even more cynicism. If people took it easier and didn't expect much, it would be better IMO
@mint Being nice and waiting for someone competent, who doesn't care about any of this shit, to show up and making them fix the mess that is your codebase is a viable strategy, you can't deny that. It starts failing when you start provoking such a person on purpose and make them play your games instead of working on code — that's why lots of these projects go downhill.
@s8n My response was to the general idea of better approach to managing projects that's mentioned in the opening post, I don't give two fucks about GNOME. If you really want to go there, it's impossible to tell what can be considered "going downhill" for a project of this age — I don't think that it has anything in common at all with original GNOME of GTK 1.x days: neither in terms of codebase, nor in terms of people involved — and I'm not even in the loop enough to tell. But if you want my opinion, it's still better than Qt clusterfuck that is KDE — because anything is better than that vomit spit that is Qt. They'd never be able to break GTK to the point when it becomes worse than Qt to me. If Qt was the only framework in existence for creating GUIs, I won't use GUIs at all — I hate it with passion since its Trolltech days :marseyraging: But again, this has nothing to do with managing software projects :marseyshrug: @mint