Take that person's post, comparing it to cooking.

Sometimes you use a ~~Library~~ pre-made sauce or spice blend as part of a recipe, so you don't need to waste time remaking something that is commonly used.

Every so often, a company will tweak the recipe for the things you are using, but it still basically tastes the same. Sometimes they just decide that now it's salty instead of sweet, so it would complete ruin the dish you would like to make.

The recipe you are using assumes you live in Australia where the new version of the sauce/spice blend is more common, but where you live still only sells the old version.

So now you can either wait for the store to sell the new sauce/spice blend, import it from Australia, or try to make it yourself. But you might have another recipe that still needs/uses the old sauce/spice blend. Needing to have both can lead to issues where you use the wrong one, ruining the food you are trying to make.

This is where ~~snaps, flatpaks, and appimages~~ those dish-in-a-box kits come into play. They'll have the correct version of the spices/sauces you want, so it doesn't really matter which version you have in your kitchen.

Snaps branded dish-in-a-box kits are developed by Canonical, and they can be kinda weird. You need to check ~~for updates~~ if you need to re-buy them manually, and you can only get them from the "Snaps Store". Other dish-in-a-box kits allow you to get them from whichever store you want, and will automatically re-order when needed.

And that’s the main issue folks have taken with snaps. If you ~~have 50+ programs~~ are making a meal with 50+ dishes, and you need to constantly check if you need to rebuy them one by one, it gets old quickly.

Also, Snaps takes up a lot of room, and generally just kinda suck compared to installing things normally or through flatpack.