Jump to content

Talk:Snap (software)

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 1992 FARHAAD (talk | contribs) at 04:47, 22 November 2020 (→Criticism). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Criticism

The criticism section is a mere irrelevant opinion of one unknown person. It's not encyclopedic at all and should be removed. 47.62.157.23 (talk) 14:11, 24 October 2018 (UTC)[reply]

The removed material can be found here: https://en.wikipedia.org/w/index.php?title=Snappy_(package_manager)&oldid=864903343#Criticism — Preceding unsigned comment added by 174.240.131.71 (talk) 22:39, 22 January 2019 (UTC)[reply]

The screen recording application has problems due to the snap confinement. the Peek developer sentence is not as reported in wikipedia: 

"Using snap is more time-consuming than Flatpak or AppImage for developers"

but he says in reddit: 

"The current Snap sandboxing does not allow Peek to access any screen recording capability in current Wayland implementations. Screen recording on Wayland still is a difficult topic anyway, but there are some compositor specific solutions available. But Snap does not allow me as an app developer to punch the necessary holes into the sandbox that would allow Peek to utilize those solutions"

and 

"Setting up and maintaining the Snap build system took me way more time then the related work on Flatpak or AppImage. There are still unresolved Snap packaging related issues in Peek I am not willing to spend any more time on debugging"

sentence that was then wrongly reported from OMGUbuntu in the way you can see in wikipedia. this still remain a criticism of one single developer for a single specific application with special authorization/accessibility needs ...so why was it reintroduced as a relevant opinion? why don't you talk also about Visual Studio Code statement : 

“The automatic update is the biggest benefit and we like the way they run seamlessly in the background.”

or GitKraken: 

"We’ve saved a lot of development time. Not only by coming to the Snapcraft Summit to accelerate our progress, but looking forward, the aim is to eliminate the need to target all the different platforms thanks to snaps’ cross platform approach"

or Plex 

"The biggest appeal of Snaps is the simple installation mechanism”"

or JetBrains 

"Snap packages seemed exactly what we need, and we’re happy that now our Ubuntu users can easily install an IDE from a desired channel and forget about updating the builds as the updates come in the background automatically"

or many other but only the peek criticism? --151.20.97.45 (talk) 13:58, 25 May 2019 (UTC)[reply]

I did a big refactor and cleanup of the page. I merged the (properly-sourced) content of the "criticism" and "security issues" the main article. See the entire refactor.
All encyclopedic content on Wikipedia must be written from a neutral point of view (NPOV), which means representing fairly, proportionately, and, as far as possible, without editorial bias, all the significant views that have been published by reliable sources on a topic.
Criticism sections are discouraged because they focus on the negative viewpoint. Wikipedia pages should be written from a neutral point of view. Please stop adding a criticism section! Instead, add properly sourced criticism in the body of the article. A number of tips for when you want to add criticism:
  • Do not give undue weight to the comments and opinions of individuals or of a minority group. Indicate the relative prominence of opposing views. For example "Developer X says that ..."
  • Make sure criticism is properly sourced. reliable source are especially important for controversial things. You should not add original research. If no reliable sources can be found, it should not be on Wikipedia. In other words: it's not enough for something to be a fact; it must also have appeared in a reliable source.
  • Use nonjudgmental language.
Wikipedia is an encyclopedia, not a rant-o-pedia. ;)
Galgalesh (talk) 18:35, 7 August 2020 (UTC)[reply]

Snap is a pretty controversial technology, in particular the way it uses the $HOME directory, as is evident from the very long discussions on a number of bug-tracker discussions, such as the nearly 300 comments on bug 1575053. In the light of the severe criticism, the complete absence of a carefully written “Criticism” section, where contributors have an opportunity to elaborate on the fundamental architectural problems with the snap approach, looks highly biased and is certainly not in line with the practice of other Wikipedia articles about controversial topics. The current article with the criticism section removed looks suspiciously white-washed by someone with commercial interests in the topic. E.g., there is no mention that one of the main problems with snap is that its approach appears to be fundamentally incompatible with e.g. NFS-mounted home directories, and therefore excludes a lot of users in organizations that use such a setup from accessing software that is increasingly only available in snap form. Markus Kuhn (talk) 18:05, 23 October 2020 (UTC)[reply]

no Disagree I am the one who added the "Criticism" section for the first time in 5 April 2018 and re-added it with little improvements in 23 January 2019 when it was removed by IPs/other users, but currently I believe that such section should not be added because as user:Galgalesh said "these are discouraged because they do not present a neutral point of view", also the article of the competing technology (Flatpak) does not have such section while it has some/many problems same as Snap. -- Editor-1 (talk) 04:47, 22 November 2020 (UTC)[reply]

Project name from Snappy to Snap or Snapcraft

Is the project still called Snappy? Or is it now called Snapcraft? I don't see any recent instances of the name "Snappy" being used at forum.snapcraft.io.

Agree. Tech201805 (talk) 07:03, 3 October 2019 (UTC)[reply]
According to this article, "Snapcraft is a tool for developers to package their programs in the Snap format for Snappy." However, from the title of https://snapcraft.io, "Snaps are universal Linux packages" and, from https://snapcraft.io/docs, "snapcraft is the command and the framework used to build your own snaps." I think Snappy is no longer the "right" name for this. BernardoSulzbach (talk) 17:26, 3 October 2019 (UTC)[reply]
Consider it fixed. Afvalbak (talk) 17:09, 3 May 2020 (UTC)[reply]

What's the point of using GNU/Linux, if you install snap?

Snap gives users somewhat quicker access to new versions than the package managers like apt. That seems to be the main point of using it.

On the other hand, the server side isn't Free Software in the FSF sense; it's closed and proprietary. Also, updates are installed automatically without explicit user consent (or even user awareness) - especially annoying when updates introduce new bugs.

GNU/Linux is all about Free (non-proprietary) software, and giving the end-user more control. If these don't matter to some users, one has to wonder why they're using GNU/Linux in the first place.

These are obvious points, but probably inappropriate for the Wikipedia article because I can't find sources acceptable under Wikipedia norms. Can anyone point to a good source for them? If so, please update the Criticisms section. — Preceding unsigned comment added by Longitude2 (talk • contribs) 22:50, 7 July 2020 (UTC)[reply]

If there are no reliable sources which show this is a significant view then it should not be on Wikipedia. Also, please don't re-add a criticism section; these are discouraged because they do not present a neutral point of view.
Galgalesh (talk) 18:41, 7 August 2020 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:Snap_(software)&oldid=989993008"