galgalesh

13 ms·

91.
by galgalesh 6y ago
Isn't this longer than the average life expectancy of that time? I wonder what kind of incentives they had for such long-term projects.
92.
by galgalesh 6y ago
I'm sorry you feel this is disingenuous. I really tried to explain why there is only one Snap Store from a neutral point of view. Let me know if you have any tips to make it more genuine. You are right that this has nothing to do with
93.
by galgalesh 6y ago
Linux Mint put in an apt rule to avoid it installing as a dependency of other apps. This decision was triggered by Canonical's announcement to stop maintaining the Chromium deb package. Linux Mint was pissed they had to either switch t
94.
by galgalesh 6y ago
Hm, maybe you're right. So in that case: > hold them Users have many ways to hold snaps temporarily. If they want to hold snaps indefinitely, then they should install them using he `--dangerous` flag. That won't give them any u
95.
by galgalesh 6y ago
> Not only that, but this is the biggest omission of the truth: Making your own server is no longer possible because of assertions. All Snaps are now digitally signed by Canonical, so you actually need to have the end-user install a fork
96.
by galgalesh 6y ago
The Yaru developers even publish their theme on Flathub so Flatpaks look good on Ubuntu.
97.
by galgalesh 6y ago
The fault isn't SquashFS itself but the compression they use. They use an old compression algorithm by default to support older kernels. They are working on optionally enabling quicker compression on distros that support it though. See
98.
by galgalesh 6y ago
The security issues SUSE raised were actually fixed, but the Snap developers did not respond quickly enough with the info that the issues were fixed. > I'd like to point out that the reason for the closure was not a failure at addre
99.
by galgalesh 6y ago
Canonical has defended their product in many places. This article contains a lot of the same info, for example: https://www.techrepublic.com/article/why-canonical-views-the...
100.
by galgalesh 6y ago
Nix is really cool! You can actually use Nix to build Snap packages! Not sure if that's actually used a lot though. One of the advantages of Snap over Nix is that snap has security builtin. Snap is built to support a store where anyone
101.
by galgalesh 6y ago
Author here. I'm happy to address any issues in the article. Let me know if there are any issues.
102.
by galgalesh 6y ago
Author here. Read the post.
103.
by galgalesh 6y ago
Provide a recent version of Arduino on debian-based systems ;) They're mainly useful for applications which either release too fast or too slow compared to regular distributions. The apps contain their own dependencies. Another advanta
104.
by galgalesh 6y ago
`snap revert app-name` is a lifesaver..
105.
by galgalesh 6y ago
Actually, even for desktop Snaps have some advantages. First of all, the fact that you can put a system service in a snap: The OpenPrinting project is working on creating a snap which contains the entire Linux printing stack. This is so use
106.
by galgalesh 6y ago
Snaps can contain _any_ piece of Linux software, from kernels to the printing stack, to PulseAudio and finally desktop applications. Flatpak only focuses on Desktop Apps. For more information, see : https://merlijn.sebrechts.be&#x
107.
by galgalesh 6y ago
> Applications in this store cannot be patched, or pinned. You can’t audit them, hold them, modify them or even point snap to a different store. This is not entirely correct. Distributions can use a "brand store" to have comple
108.
by galgalesh 6y ago
> For instance, kustomize as snap doesn't let you read anything outside that is not in the snap fs. Not even in --classic mode. Classic snaps have complete access to the host filesystem. It is up to the publisher, however, to reques
109.
by galgalesh 6y ago
(author here) I'm not sure what you are referring to exactly, where do you think I say that? These are the reasons I talk about in the blog: * users can easily discover new applications, * developers can easily publish their apps, * an
110.
by galgalesh 6y ago
I don't think open sourcing the store would significantly cut their sales. Running a world-wide package distribution network in itself is an incredible cost which many companies are willing to pay for. CentOS did not cut into the sales
111.
by galgalesh 6y ago
> Launchpad is also objectively more complex and hard to use than alternatives, and subjectively I'd say it's ugly and looks dated Launchpad is _really_ old though. When it was open sourced, there were very few alternatives and
112.
by galgalesh 6y ago
€60.000/yr seems reasonable. This is the average salary in the Netherlands (home of the blender foundation).
113.
Copyleft and LGPL in Snaps and Flatpaks(merlijn.sebrechts.be)
1 points by galgalesh 6y ago|0 comments
114.
by galgalesh 6y ago
Mattermost actually has threads, but their UI is a little bit more clunky than Slack. All the messages show up in the "main thread" like nornal but once you click on one of the threaded messages, you only see the messages of that
115.
by galgalesh 6y ago
This comment adds no value to the discussion; it's "Ubuntu bad, Canonical bad" stretched over 4 paragraphs. Yes, it's clear that you don't like them. HN discussion are expected to be more substantial than this.
116.
by galgalesh 6y ago
In case this eases your worries: the approval process for permissions is formalised and does not depend on how mature or well-known the app is. In addition: users always have the option to override permissions. The approval process is for a
117.
by galgalesh 6y ago
Did you mean devmode instead of beta? Just wanted to easy one worry of you: the age, popularity and maturity of your application has no influence on whether or not these permission requests are granted. The approval process is formally defi
118.
by galgalesh 6y ago
The snap store support is a small part of what is announced here. The team developed a GTK+ based host for flutter, which works regardless of the packaging method you use. The end of the blog post talks about modifications to the snapcraft
119.
by galgalesh 6y ago
Yeah, it would be useful to have a metadata field "packaging repository" or something. Snaps built from GitHub with snapcraft.io include a manifest and the build recipe in the `meta` folder in the root of the snap. This includes a
120.
by galgalesh 6y ago
> The fact that you have to post on a forum and argue with people why you need permission X for your snap package was enough for me to abort publishing on this platform. I should ask permissions from the users not from the platform publi

More ›