+bonifartius 𒂼𒄄
computer rant
WHY are "modern" messengers always something that requires some container shit like flatpack or snap? why is everyone fine with this? or is it just the same crowd as with wayland?
completely shit way to develop software. this isn't "fine", there's a word for it, "shit". it's shitware. it's not even fine for a prototype.
last protocol that was remotely sane in this regard is XMPP. it had clients you could build on a normal system.
can't be video playback. that's a handful of libraries. not 300 very specific verisons only compiling with an old gcc version. except for the one exotic library that requires clang or something and 4 different scripting languages on top of the NEW and MODERN build system that is the same shit as the myriad of build systems before.
why not just TRANSFER the BYTES and then EMBED a mplayer window? DOESN'T THAT WORK WITH WAYLAND?
literally throwing away decades of good ideas about how software should be developed for ideas made of pure shit.
computer rant
computer rant
@nanook i don't ask anyone to compile for my platform. compiling is what distributions do. i ask to not make this extra hard to do so out of laziness.
"works on my machine" used to be a joke made about shitware, now people think it's good practice.
i can compile stuff from the 90s with a few patches, i don't expect i'll be able to use flatpaks in five years. flatpak will be replaced with the next reinvented wheel by then.
