Login

Recent searches

No recent searches

Search options

Only available when logged in.
social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

486
active users

social.coop: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#snappy

0 posts0 participants0 posts today
Public
EOMasters

SNAP Tutorials #6 - Bulk Processing with GPT
This tutorial, by Marco Peters (yes me 🙂), gives an introduction on bulk processing with the command line on Windows and Unix systems. The provided scripts try to stay very generic to serve multiple processing requirements.

Tutorial: senbox.atlassian.net/wiki/spac
Marco Peters: linkedin.com/in/marco-peters-4

#tutorial#esa_snap#snappy
Public
Hopper The Cocker

#pixel9proxl first impressions
Google switched up the release date, I was going to wait for my 2 year cycle but the rebate and credit offers were too good to ignore - so I came to this device reluctantly. It is #silkysmooth to use and #snappy . We all know the #nexus5 was the OG android hall-of-famer. This is the first device since then that I have this level of joy to use and I wasn't expecting to experience that.

Public
mgorny-nyan (he) :autism:🙀🚂🐧

#Snappy once again broke ABI without changing SOVERSION, and trashed reverse dependencies.

Hey, what did you expect from a project that is "focused on maintaining a build configuration that allows us to test that the project works in a few supported configurations inside #Google"?

bugs.gentoo.org/929199
Citation from github.com/google/snappy?tab=r

bugs.gentoo.org929199 – app-arch/snappy-1.2.0 broke ABI (was: dev-util/kdevelop-24.02.2 undefined reference to `snappy::RawCompress(char const*, unsigned long, char*, unsigned long*)')
#Gentoo#OpenSource
Public *
mgorny-nyan (on) :autism:🙀🚂🐧

Zdaje się, że się starzeję, bo patrzę na łatkę dodającą wsparcie #Brotli na liście bug-tar, i myślę sobie, że powinniśmy bojkotować ten algorytm.

Brotli nie jest w żaden sposób wybitne. Jasne, jest nieco skuteczniejsze niż gzip — toż to osiągnięcie, pobić algorytm z początku lat 90-tych! Dzisiaj natomiast mamy już zstd, które jest po prostu lepsze.

Brotli istnieje jako opcja kompresji HTTP tylko za sprawą #Google. Tak, tego samego złego monopolisty, który zaimplementował DRM w swojej przeglądarce internetowej (żeby chronić reklamodawców!) i zablokował format #JPEGXL.

lists.gnu.org/archive/html/bug

Nie zapominajmy też o #snappy, innym algorytmie kompresji z Google Open Source, prawdopodobnie najbardziej znanym z tego, że autorzy odrzucają łatki wykraczające poza "kilka wspieranych konfiguracji używanych wewnątrz Google" (tłum. własne).

github.com/google/snappy#contr

lists.gnu.org[PATCH] Add support for brotli compression
Public *
mgorny-nyan (he) :autism:🙀🚂🐧

I guess I'm getting old because I'm looking at the brotli support patch to bug-tar, and I honestly think we really should boycott #brotli.

Brotli doesn't really excel at anything. Sure, it apparently fared better than gzip — outperforming a format from early 1990s is a great achievement! However, today we have zstd and it simply is better.

Brotli exists as a HTTP compression variant only because #Google pushed for it. Yes, the same evil monopoly that also implemented DRM in its web browser (to protect ad vendors!) and blocked #JPEGXL.

lists.gnu.org/archive/html/bug

Let's also not forget #snappy, another Google Open Source compressor, probably best known for refusing fixes that go outside "a few supported configurations inside Google".

github.com/google/snappy#contr

lists.gnu.org[PATCH] Add support for brotli compression
Replied in thread
Public
R1 Airport

@Niquarl #Flatpak, #Snappy, and #Appimage are three different types of package formats meant to be the universal standard for #Linux package management (see image). All three are sandboxed in some way.

I don't like #Snaps for two main reasons: the server software needed to distribute them is proprietary, and they're just simply slower than Flatpaks and debs. While #Flatpaks are excepted as a de-facto standard by most of the rest of the Linux community, #Canonical still aggressively pushes Snaps for desktop usage. All of this is summed up in this blog post:

jatan.blog/2020/05/02/ubuntu-s

For this among other reasons, I strongly recommend you to use #Pop_OS instead of #Ubuntu.

XKCD #927 — Standards Situation: There are 14 competing standards. Cueball: 14?! Ridiculous! We need to develop one universal standard that covers everyone's use cases. Ponytail: Yeah! Soon: Situation: There are 15 competing standards.
Public
Mr. Matt :fedora: :linux:

#flatpak and #snappy solve the problem of Linux distros shipping outdated versions of applications. That's one of the reasons I stopped using Debian Stable and am loathe to use Ubuntu LTS.

On the other hand I don't want to use a rolling release due to frequent OS breakage.

ExploreLive feeds
About