

Can you explain a bit more on how this is a benefit?


Can you explain a bit more on how this is a benefit?


Buddy… Expend some effort ffs


Would it being stupid shock you somehow? It’s also illegal and will be shut down in court, like everything this Captain Dipshit does.


This is for the client display only, and not the iOS API interface as I’m discussing. It’s not very plainly laid out in the docs, but one would assume any queuing of content into the notification system would be stored or cached if not cleared. There doesn’t seem to be a way to have a client of that system to clear it’s own data once it’s in there, just cancel last notification.


Clever. Not much you can do for this except not subscribe your app to the notifications API, or take extra steps to attempt to clear them, but I don’t remember that being an option on iOS. Going to be an interesting fix.


Start a petition and/or get a proposition on your State ballot. For real!


🤣
My gawd. The hoops you jump through. Just take the L and walk on, slugger.


An example:
Application Payload = 100MB AppImage all inclusive image with deps = 175MB Flatpak App Layer = 101MB Flatpak Deps = 75MB
Now say you’re shipping 1000’s of similar applications with the same general dependency chains in bulk operations to things like end-user devices.
Flatpak wins. That’s the point.
This isn’t a discussion about an average Desktop user saving some disk space.


This has been known for awhile, and this was already accepted to be an issue with PH memory handling. Not weird, rare or otherwise, it will get fixed.


My Packard Bell will be so sad


I don’t really get the point of the blog, honestly, because in the first part they are railing against one angle, then reverse and argue FOR it in a sense by saying Flatpak just works. Of course it does. That’s it’s job.
AppImage also just works, but there is a fundamental difference in the delta of what you get as a payload. AppImage has EVERYTHING the image needs to run. Flatpaks only contain the running code and custom dependencies, then it’s manager solves for shared libraries and generics from commonly available layers to download and run to solve for those deps.
Both make sense depending on how you feel you need to tackle the problem.
Where the author kid of goes off the rails is complaining that somehow either camp is somehow responsible for their product being popular enough to survive and be taken up by Valve. In this specific case, Valve is intending to include simple packaging for games and libraries they intend to ship to millions of cross platform devices. Flatpak makes sense from a bandwidth and storage standpoint for end-users.
AppImage does not. No idea why this person is taking issue with that.


Flatpak makes more sense for how Valve will be using it for all their new devices. Simple as that.
They “shit” money into ALL kinds of development that pushed lots of projects forward a decade in maybe a years time, and are doing it again with FEX. Are you taking issue with allmof that, or just this because they have a business use-case?


What a fucking joke. I hope this goes down in flames from the get-go, but I know it’s going to bounce high on the first day, defying all logic.
This company will never make an actual $1 Trillion fucking Dollars.


So about 1/3 of the country, right? You and your idiot compatriots outta do it. See ya.


Objectively fucking hilarious.
This man has been responsible for stomping down the voices who seek to replace him. AOC, Mamdani, Ossof, Platner…keep naming them.
He is no different than Schumer. Fuck both of you.


Or played Metal Gear. WTF.


🤦…here we go again
Somebody’s about to do something fucking horrific again.
TrendNet is far superior and based on Torrence anyway. Netgear and Linksys are junk anyway. Get yourself an open hardware platform, or something that can run OpenWRT. Skip the corporate manufacturers who all kind of suck.