• 0 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: July 21st, 2023

help-circle





  • Same app in native format: 2MB. As a flatpak: 15MB. As an appimage: 350MB.

    Appimages are awesome, rock solid, and I have a few on my system, but flatpak never gave me any problem and integrates better with my KDE, and is smaller. Both have their advantages tho. I’m fine with using both. If you are a developer, make a flatpak or an appimage i dont really care just make your software available for linux. Both are fine, choose the one that fits your specific app the most.

    But I also think appimages deserve the same attention and great integration with the OS as flatpaks. Stuff like that AppImageLauncher functionalities should just be integrated inside the DE itself.

    But we need an universal package format for linux asap. Flatpak is on the front in this race, and I’m fine with it. Appimages second, for sure.




  • Picture this: you buy a car. You buy a new set of wheels/rims and a new radio system with Android and whatever. You also put some new carpets on the floor of the car. Now you need to take it for a simple routine maintenance and checkup at the car brand official shop. After a few hours you go back there to pick you car up and it has the stock wheels, stock radio, stock carpets and everything and you ask where the hell is your stuff and ALL of them on the shop look at you confused like if they never seen any different accessory on that car before other than the stock ones, or don’t know what you are talking about. All they know is that the car is now “according to spec”.

    This is what it feels like after updating Windows with Linux in dual-boot on the same drive.