

How planes generate lift.
Somewhere between Linux woes, gaming, open source, 3D printing, recreational coding, and occasional ranting.
🇬🇧 / 🇩🇪
How planes generate lift.
My personal order:
Repositories > AUR > Making an own AUR package > Making an own package not in AUR > Flatpak > Using an alternative to that application > consider if I really need it > AppImage
Disabled by default, as of yet.
And another set of features to disable.
Of archeologists don’t know it: “for religious reasons”.
No, sorry, I’m dumb.
There will always be this one asshole of a coworker who happily name-dropping you in a conference call with the project owner.
… after removing them and ignoring them for several years.
After seven years of active development
I wonder where they got this from. The 2.x branch was first released 21 years ago.
Write an ungodly large amount of code-comments - up to a point where you add 20 lines of explanations to a 6 lines long function where two lines are variables assignments.
Source code is for humans to read. The compiler ignores the comments.
Seems like not entirely. But oh well. It looked so good on YouTube. Especially the customizations and alternate UIs.
Currently I’m angrily sticking with Firefox. But once Floorp switches to the current version of Firefox as base I’ll totally try this one. According to what I found, they will switch with the next major release.
Most of your money goes to CEO salary and not towards developing Firefox.
Overall, I don’t think Mozilla is wrong. Without the Google Search deal, Firefox will have less resources to build a competent browser.
The vast majority of the corporations income does not go to Firefox anyways. Their financial reports are publicly available, everyone can read them.
I have zero sympathy for the corporation and I hope they go bankrupt and that the devs forking the browser and develop it as a standalone product independent of the Mozilla-owned Firefox.
I gave up Bash scripting. I explicitly do “shell scripting” now, where “shell” is implied to be a POSIX compliant shell of any type.
it doesn’t really suit my needs.
What are your needs?
Mainly because you cannot manage them properly.
Installing from the repos I have pacman, from the AUR I can use one of the various AUR helpers (most of them can forward repo package updates to pacman, so I really have just one command to update the system and all AUR packages).
When making my own packages I usually also put them in the AUR (plus, it is super easy to do make an own package and put in in the AUR) – and from there an aUR helper takes care about updates. Flatpaks can also be updated very easy by just running one command.
So: All of those have a specific location where they install and allow me to start them easily because they put a script/link somewhere in
$PATH
. All of those can be easily maintained and updated.Last time I checked, AppImages had none of those. Neither could I easily update all of them on my system, nor is there a dedicated location to place them, nor is there an “unified” (i.e. something in
$PATH
) way of starting them. I have to manually check for updates, re-download the whole thing, replace the current AppImage file in an arbitrary location.This is just how I do not want to maintain my programs.