Where were you when Snappy saved Linux from fragmented package manager hell?

Where were you when Snappy saved Linux from fragmented package manager hell?

docker numale sjw startup agile fgootry

literally the idea i had 2 weeks ago only i had the vision of hardware setup as well. custom tailored distros for your hardware configuration delivered for $$$

>implying we need a standard so lazy programmers can use out of date and insecure libraries rather than updating their software

>install gentoo
>install everything via snaps and flatpak
>post in desktop threads using gentoo with

>fragmented package manager hell
The distros without large repos have ports systems you mong
Also there's this thing calling compiling
>There are mongoloids actually advocating for non-shared libs
Wow, it's windows 95 all fucking over again

>not using Portage
I weep for the lesser distros

Why make it so complex? Why not just put all files part of the package in a tarball and then use a bash script to put the files where they should be?

AppImage >>>>>> Snappy.

Because not every normie can into make install.

>snapcraft
>Wow, it's windows 95 all fucking over again
This but it can come in handy for development.

Thats way too simple and efficient. How would they sell you crap then?

>not every normie can into make install.
Even if they can, shitty dev assume every OS is like theirs bloated with all the dependencies.

>This but it can come in handy for development.
Except it wont
What the fuck is the point of this trash when compiling from source and ports exist?
It takes a total of 2 minutes to package a program in a .deb or .rpm if you need a binary

Various versions of the same package can be used. That's good.

>Wow, it's windows 95 all fucking over again
If if helps GNU+Linux achieve 10% of its market share you should be happy.

I believe there's also some sandboxing involved, at least in Ubuntu. It's not just old installation.

>save Linux from fragmented hell

It's called appimages

snappy is a perfect example for fragmentation and trying to enforce a walled garden on users

This

Snappy isn't going to save linux it's going to destroy it. It's going to let each program bring in separate dependencies. Like windows with 10 versions of dot net because each program needs a different version. Besides the container hype train left the station a few years ago.

Snaps just got their install size reduced by like 80%

Before they were 30-100MiB.
Now they are 2-5MiB.

>inb4 muh flatpaks
They are lgpl.

Snappackages are GPL3

There's also 1000+ snap packages already with only 100+ flatpaks.

Snaps will allow people to package programs for linux!

this is great!

steam/skype/adobe*/autocad/photoshop can be packaged for universal distros

this will make more companies invest in linux and allow a easier transition away from microsofts monopoly

its difficult when people like autocad want to port their program to linux but cant figure out if they should target arch or ubuntu or gentoo

its very difficult for companies to get a foot in the door

no one is saying you should use proprietary software but this would atleast allow the option to distribute it in a secured environment

appimages are MIT licensed though

From this, we can say that appimages > flatpaks > snappackages

That's why chroots are a thing you mong

More like snaps>paks>apps

Appimages aren't sandboxed like the other two.

Interesting how IBM never has problems with this
Just link the binary to a script that runs it like they do with SPSS and the various games from gog

There's multiple reasons for snappacks.

1. multiple architectures 32/64
2. multiple versions of the same package
3. universal distro package
4. sandboxing

I really don't think 2 weeks is enough for the development of this product, 6 months more likely.

Snappy isn't bad but it's not necessary. Even static compilation would do the same job and we've had that since the beginning of time.

gee maybe because they are multi billion dollar corps who spam the globe?

they created the IBM PC standard...
you suggesting that IBM is any way comparable to something like autocad is laughable

yet we still have trouble packaging between distros and we dont have any support for graphical editing software on linux

we cant even get hulu or netflix natively

what if the package needs things outside it

Who cares, it just werx

It won't succeede because it isn't backed by Redhat.

by design it cant use stuff outside because of how its packaged

this means that dependencies are all setup by the person who packages the snap

its pretty nice for end users because they just have to do "apt install snapd" "snapd install package"

so does bsd but it then it gets cukd because they dont use GPL

>lets bring the cancer of program distribution on windows to linux
No, thanks. I don't want 9999 different versions of the same library.

Even the great operating system Solus is supporting them.

1.chroot
2.chroot
3.make install is universal
4.jails/chroot
so why does yooka layle (shit game btw) just werk on both my debian and arch boxes?

you can have a certain version of wine packages specificially for a specific program version

every program update can break wine support

every wine update can break program support

this can solve that by pre packaged libraries with programs while also protecting you from WINE exploits in a sandbox

these dont require multiple version libraries in your normal package manager they are all isolated to each snap pack

doesnt work for small projects
doesnt work for inexperienced users

doesnt work if i want to use a precompiled program like nightly firefox from the redhat repo on debian wheezy

Terrible meme. They are the wobbly windows / desktop cubes of 2017.

>Snappy saved Linux from fragmented package manager hell?
What do you mean? Snappy, flatpak, appimage, docker.

How is that any different from what we have with traditional (good) pkg managers?

QEMU/KVM can run individual binaries
>inexperienced user
>needed a development tool
ok
If you're writing a program and you dont know what a chroot is you need to stop writing that program

so the solution to fixing fragmented package manager hell is to introduce yet another package manager? Are you OK?

But this time you package the whole runtime along with your package. The runtime is shared, but enjoy having a whole lot of library versions installed for no gain.

And we all know who backs redhat.

Snaps require a specific framework to run.

>Appimages aren't sandboxed like the other two.
What is firejail?

simplifies it for normal users to install programs more easily

I'm not surprised a linux autist is upset about it. Please move over to BSD and never touch linux again

> fragmented package manager hell
What's this?

autists please go

Every distro should be allowed to access the AUR.

So instead of using Portage, literally the most flexible package manager (dependencies, slots, USE flags, individually compiled or binary packages, sandboxing, unit tests, safe uninstalls, creating cross-compiled binary packages, compiler optimizations, prefixing), they create yet another one and it installs appimages. Literally install Gentoo, you mongoloids.

...

Lets have 20 copies of the same libs and same base programs for every snap we install.

In the future every program will be statically linked with all resources embedded. No more libraries, manual pages, /usr/shared. Just place program on the desktop and double-click it ;).

cool, now I have to wait for every program to decompress before I can run it

you're either dumb or can't read. he wrote that he HAD the idea 2 weeks ago.

>rob pike is unhappy with splits and claims we learned nothing
>literally invents C 2.0 with most its flaws + some new ones while not really solving any of the problems because muh UNIX way

thats not even true.

have u even ran a snappack before?

Firstly, it's not C replacement
>solving shitty error handling in C
>concurrency with software threads
>staticly linked wm removing architecture differences
>garbage collection with focus on low latency
>modules
>small compiler and toolchain
>polymorphism
Please tell me how it solves no problems

So they can get printer drivers that don't work?

>DEC Unix
It's called Ultrix, you bitch.

>>solving shitty error handling in C
It doesn't, it basically copied it. Now instead of checking a single return value, you have to check TWO values.

Exceptions have been around for ages, and yet these UNIX dinosaurs reinvented C-style return values.

>>concurrency with software threads
Whoop de doo. Every modern language has this, even fucking sepples and C11.

>>staticly linked wm removing architecture differences
You mean runtime, and this is no different than statically linking a minimalist libc.

>>garbage collection with focus on low latency
In other words, no garbage collection and RAII instead. C++ has had this for ages, and various extensions to C have them.

error patterns in C:
>return integer instead of void
>reserve half of integer range for 1 or 2 error values (the worst one)
>return NULL pointer
>modify global variable (errno)
>optionally add argument to assing error string to
>(plus every idiot implements their own panic function because they just can't use err() from stdlib)

error pattern in Go:
>return multiple values, last of them being interface Error
>has packed error string
>if nil ok
you don't have to check any second value, dunno what you mean by that