+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
though moving to flatpak just makes sense for most people. as a solo dev i am not at all percent interested in whatever bullshit bikeshedding 20+ linux distros have to get my package accepted.
to paraphrase deming, a slightly different building code in every state does more to damage mass production than a universal tariff
computer rant
@icedquinn
> to paraphrase deming, a slightly different building code in every state does more to damage mass production than a universal tariff
sure, but mass production is also about simplifying things by reducing parts.
i can get why people like the result, but the way it's done is bad and will create harder problems in the future.
it's not limited to computers. it's like this for many things that aren't extremely simple. washing machines! what was wrong with turning the mechanic program knob and pushing the mechanic "on/off" button? worked fine and was repairable, much like software was compiled with relative ease.
i know no one who uses washing machine control apps (which will cease function in 3 years anyway, because the manufacturer turns off the cloud..).
computer rant
@icedquinn it isn't inherently bad, it removes the need to think much about dependencies which apparently most people view as invitation for "just another lib bro". which then turns the whole thing into "runs exclusively on flatpak" because something of the dependency tree will always be missing.
something missing is easy to solve when it's only half a dozen libraries, just package them as well. if it's in the hundreds, things get ugly very fast.
computer rant