• 0 Posts
  • 20 Comments
Joined 2 years ago
cake
Cake day: June 28th, 2023

help-circle





  • For most of human history, salt has corresponded to this definition. Have you ever wondered why it’s called a salary?

    It’s very nice when your wallet is barely keeping afloat and you’re left without money because salt gone form wallet… Or do you mean super cheap rock salt?

    Well, to be left without money because I got caught in the rain is not still a pleasure.

    Tungsten is also one of the rarest minerals on Earth, despite its relative cheapness.

    Good… At a time when gold was still a currency, tungsten was not yet able to be smelted. In addition, when heated, tungsten is reactively oxidized, unlike gold.



  • The value of gold, silver and platinum is determined by two factors: there is little of it in nature and you cannot take more at will and it does not oxidize, which ensures good storage.

    I really don’t know about you, but in my country you can’t take gold out of the bank. You buy gold from a bank and it stays in the bank longer without the possibility of taking it out. What a joke. Guess what happens to the bank and the gold in it when the economy collapses.

    And now look at Bitcoin. there is a little of it, you can’t increase it at will, and it’s convenient to store. Does it remind you of anything? And it’s always with you.



  • Bitcoin is a pyramid scheme because it only keeps its value as long as people are constantly buying it. If no one wants to buy it, the value of any amount of bitcoin is zero. This is why people who have bitcoin are trying to convince anyone else to keep buying.

    any currency is initially a bank’s promissory notes, and then a promise to exchange the paper for some kind of labor. As a person who has experienced at least one default in his life and whose entire toilet is covered with USSR money, I can say that in this regard, no currency is different from bitcoin.




  • runtime have versions too. If one runtime version use only one flatpack than exactly same as just static linking binary. Flatpack have just docker layeredfs and firejail in base.

    id: org.gnome.Dictionary runtime: org.gnome.Platform runtime-version: '45' <- here sdk: org.gnome.Sdk command: gnome-dictionary


  • They don’t have to! Flat pack doesn’t remove all other ways to install software. But for 95% of use cases, it will do just fine.

    Tell this to canonical, they even firefox put in the snap. You know that when choosing “quickly compile something for a flatpack” and “support 10+ distributions”, the developers will choose a flatpack. Which in general looks fine, until you realize that everything is just scored on the mainline of libraries and molded on anything. The most striking example of this is Linphone. just try to compile it…



  • nitrolife@rekabu.rutoLinux@lemmy.mlFan of Flatpaks ...or Not?
    link
    fedilink
    arrow-up
    6
    arrow-down
    2
    ·
    edit-2
    1 month ago

    this is a system for work tasks. Of course, I understand what the developers are going for. that is Android. And it’s really nice to read the Internet on android. But try to do something more complicated than that and you’ll realize that it’s hell. However, I don’t mind if such distributions appear. Why not? I just don’t understand people who voluntarily limit their abilities. And why you don’t just install Android 64?

    The flatpack approach automatically remove everything low-level from the equation. Do you want to write directly to the graphics card buffer? Read the input? Do I set the fan rotation parameters directly in the /proc? All these applications will never work in flat pack.

    On the other hand, flatpack is superfluous and for convenience. You can simply build an executable file without dependencies and configure firejail for it yourself… That’s all. Or run the file from another user. That is so popular exactly bacause RedHat pushed them. Literaly like Canonical pushed snap.


  • nitrolife@rekabu.rutoLinux@lemmy.mlFan of Flatpaks ...or Not?
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    1 month ago

    However, the extent of the damage is limited by flatpak and whatever permissions you have set, and, if I understand it correctly, you cannot attack one flatpak through the other unless they share access to some files.

    there is a problem here that permissions are also set by the packages developers. User in most cases click accept all and alll done.

    On an unrelated note: apparently, there is finally some Russian Lemmy instance? That’s a welcome change.

    Well… Appeared 2 years ago. It’s just that practically no one needs it. =)


  • nitrolife@rekabu.rutoLinux@lemmy.mlFan of Flatpaks ...or Not?
    link
    fedilink
    arrow-up
    13
    arrow-down
    2
    ·
    1 month ago

    Times are changing, and memory constraints for most programs are generally not relevant anymore.

    But there are gaps in the libraries that, unlike distributions with dependencies, can no longer be managed. And all the security of your system depends on a small flatpack access control, which 99% of users do not understand at all and, with any problems simply opens access to the entire home directory.


  • It’s not the 80s, and I can save a few megabytes to keep my system running smoothly and well-managed.

    And then it turns out that you have 18 libssl libraries in diffirent fpatpacks, and half of them contain a critical vulnerability that any website on the Internet can use to hack your PC. How much do you trust the limitations of flatpack apps? are you sure that a random hacker won’t hack your OBS web plugin and encrypt your entire fpatpack partition (which some “very smart” distributions even stuff office into, and your work files will be hidden there). People have come up with external dependencies for a reason.


  • nitrolife@rekabu.rutoLinux@lemmy.mlFan of Flatpaks ...or Not?
    link
    fedilink
    arrow-up
    23
    arrow-down
    4
    ·
    edit-2
    1 month ago

    I’ve been working on Linux for 15 years now and I perfectly remember the origin of many concepts. If you look at it through time, what would it be like:

    1. We can build applications with external dependencies or a single binary, what should we choose?
    2. The community is abandoning a single binary due to the increased weight of applications and memory consumption and libraries problems
    3. Dependency hell is coming …
    4. Snap, flatpack, appimage and other strange solutions are inventing something, which are essentially a single binary, but with an overlay (if the developer has hands from the right place, which is often not the case)
    5. Someone on lemmy says that he literally doesn’t care if the application is built in a single binary, consumes extra memory and have libraries problems. Just close all permissions for that application…

    Well, all I can say about this is just assemble a single binary for all applications, stop doing nonsense with a flatpack/snap/etc.

    UPD: or if you really want to break all the conventions, just use nixos. You don’t need snap/flatpack/etc.