I don’t know what dependencies he has but my 3 year old system that is constantly being updated is full of flatpaks and all of the dependencies combined are only around 3GB. People see 1GB of dependencies and lose their mind.
I don’t know what dependencies he has but my 3 year old system that is constantly being updated is full of flatpaks and all of the dependencies combined are only around 3GB. People see 1GB of dependencies and lose their mind.
I change my opinion depending on which app it is. I use KDE, so any KDE app will be installed natively for sure for perfect integration. Stuff like grub costumizer etc all native. Steam, Lutris, GIMP, Discord, chrome, firefox, telegram? Flatpak, all of those. They don’t need perfect integration and I prefer the stability, easy upgrades and ease of uninstall of flatpak. Native is used when OS integration is a must. Flatpak for everything else. Especially since sometimes the distro’s package is months/years old… prefering distro packages for everything should be a thing of the past.
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.
Will the older unsupported widgets get hidden from the “get more…” screens? Please. I don’t want unsupported widgets and extra stuff being shown there and confusing casual users even advanced users and creating more bugs and problems than needed
Well I myself have no patience at all to compile stuff myself, I can say I am half casual half linux nerd. I’m in the middle. Compiling stuff is too much, especially drivers and low level stuff like that. At that point I will just give up on the hardware or the OS/distro. That’s mainly why I still dual boot. I have a SIM Racing setup and even with drivers that exist already and many awesome community made GUI tools (like Overdrive GUI) that get updated almost daily (which is impressive), it still is very hit or miss and most of the times it is either not detected at all or just half working. Even after using linux myself since the Ubuntu 7 and Gnome 2 days, I still dual boot Windows because well… sometimes life is just more peaceful when you can just reboot your pc and have funcional hardware again. I work under linux and play under windows. That’s peace for me. Except nowadays I am staring to play non-Sim Racing stuff on linux too because Proton is amazing. But it still requires a lot of manual labor to make it work. And when I teach linux to other people I always teach the dual boot way and how they can easily jump back to what they are used to. In your case… I think I would just get a different wifi card if possible. If its an embedded one, well… maybe I would just get a new motherboard/device anyway, or just use another OS and call it a day. Sometimes it’s the better way. In your case probably the amount of people that need drivers for hardware like yours is diminishing day by day, so the probability of it ever getting fixed also diminishes. I found out that in the Linux world it’s always better to stay with mainstream hardware as much as possible.
I understand, but seeing this post right after my experience today was the biggest coincidence ever and kinda funny that it worked right away in Linux while in Windows I had to manually go get the drivers for it. Linux used to be bad, but it evolved A LOT in terms of drivers support while windows just kinda stayed the same. I remember facing the same problem of booting a new Windows install and having the wifi option completely gone (no drivers) in Windows 8… many years ago. Windows 11 and the experience is still the same. And it’s a modern Realtek card, not even close to being obscure. This post + this experience today was just a nice internet moment
Funny that my brand new laptop just arrived today and its own wifi card wasn’t recognized in Windows, so I had to use my phone via usb-tethering. It’s a Lenovo Yoga Slim 7 (14APU8) by the way, Ryzen 7th gen, full AMD, OLED etc. It came without any OS (no way I’m paying for Windows lol) and my first Win11 experience on this laptop was “please choose a network to continue” and no networks were displayed at all, because wifi card had no drivers (Realtek btw). Windows setup wouldn’t let me continue without a network, but there was no way to have a network. Funny Win11 moment right there. After some hours configuring everything I then installed my usual dual-boot Fedora and everything worked even in the live-usb. This meme is not valid for Linux anymore. Windows however, now thats a meme.
Having half of the world depend on a corporate proprietary single company is the stupidest thing ever. They will learn nothing with this, sadly