computer rant

Sensitive content

in reply to +bonifartius π’‚Όπ’„„

computer rant

electron has been a real problem wrt. wayland, or something.

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

in reply to Q.U.I.N.N.

re: computer rant

@verita84 i have personally dealt with trying to do such a thing with some music software on void / alpine.

such issues i've run in to are things like
- we don't like how that project wrote their build scripts, please rewrite upstreams build scripts to appease us
- someone else is already working on that package (hasn't updated in months, no updates on approvals or rejection)
- we don't like the way you marked that CPU as a non-supported target, please change it to a case statement. update: unrelated maintainer doesn't like that you approved the case statement, please rewrite the script to use an if/else*
- no sorry that requires .NET which we will never approve because we don't approve of the bootstrap requirements of the C# compiler

* this is the issue where i started referring to all upstreams as bikeshedders because their change requirements were literally pointless

in reply to +bonifartius π’‚Όπ’„„

computer rant
@+bonifartius π’‚Όπ’„„ Why? Because developers are lazy and don't want to have to compile and link for each platform just to save you convenience and memory. So flatpaks and snaps get around this by bundling libraries, then what version the system has on it natively becomes irrelevant, but this approach wastes your disk space, creates additional dependencies that can break your system, and defeats the purpose of linux shared libraries wasting memory.
⇧