Canonical bringing Snappy Ubuntu to phone and desktop

grabcocque wrote: post #2

I had a feeling this would happen. Containerisation as a trend has just as much to offer desktop OSes as it does for cloud clusters.

Is this really containerization as we know it, like Docker? To me, Android and alike just have a good separation between processes.

This is, of course, the core of linux containers. But I don't need to deploy a system image to run an Android application.

Re: Canonical bringing Snappy Ubuntu to phone and desktop

#5

Post by edude03 » Wed, Nov 04, 2015, 4:37 PM UTC

Slightly off topic, but I'm really frustrated with the state of software packaging these days. Every solution tries to solve the same problems (reliable dependancy resolution, reliable installation and removal) but they all try and solve it in different incompatible and flawed ways.

Consider the following: I need a reliable way to deploy my app to clients.

The popular options are: 1) Source code + Configuration system (automake for example) 2) Binaries built for popular platforms (debs, rpms, exes) 3) Docker Image

Source code means that the client needs the whole build tool chain, which might be quite + computationally expensive (especially on mobile)

packages have to be built and maintained, and don't fully solve the dependancy issues (IE I might expect Ubuntu 14.04 to have a specific version of libc, but the user might have upgraded it, and I can't install my own incompatible version)

and of course docker, ship my clients a operating system and require them to have and know how to configure the runtime so they can run my 1mb compiled binary. Also doesn't work on embedded devices.

Ideally, in the future most distributions will move to functional package managers, and at least for mobile will have binaries for every possible version of dependencies available, but at the moment that's just a pipe dream and things like snappy don't get us any closer to that

Re: Canonical bringing Snappy Ubuntu to phone and desktop

#6

Post by hasenj » Wed, Nov 04, 2015, 4:45 PM UTC

edude03 wrote: post #5

Slightly off topic, but I'm really frustrated with the state of software packaging these days. Every solution tries to solve the same problems (reliable dependancy resolution, reliable installation and removal) but they all try and solve it in different incompatible and flawed ways. Consider the following: I need a reliable way to deploy my app to clients. The popular options are: 1) Source code + Configuration syste…

I think Docker is meant for dev ops, not for casual users.

Re: Canonical bringing Snappy Ubuntu to phone and desktop

#7

Post by ant6n » Wed, Nov 04, 2015, 4:46 PM UTC

edude03 wrote: post #5

Slightly off topic, but I'm really frustrated with the state of software packaging these days. Every solution tries to solve the same problems (reliable dependancy resolution, reliable installation and removal) but they all try and solve it in different incompatible and flawed ways. Consider the following: I need a reliable way to deploy my app to clients. The popular options are: 1) Source code + Configuration syste…

You mean sort of like npm?

Re: Canonical bringing Snappy Ubuntu to phone and desktop

#8

Post by davexunit » Wed, Nov 04, 2015, 4:47 PM UTC

edude03 wrote: post #5

Slightly off topic, but I'm really frustrated with the state of software packaging these days. Every solution tries to solve the same problems (reliable dependancy resolution, reliable installation and removal) but they all try and solve it in different incompatible and flawed ways. Consider the following: I need a reliable way to deploy my app to clients. The popular options are: 1) Source code + Configuration syste…

I agree that functional package management is the way forward. Having a system that contains the precise details of how to go from source code to binary, in a completely automated fashion, for the entire set of packages all the way down to the bootstrap binaries is a critical foundation to build upon.

Re: Canonical bringing Snappy Ubuntu to phone and desktop

#9

Post by IgorPartola » Wed, Nov 04, 2015, 4:50 PM UTC

ant6n wrote: post #7

edude03 wrote: post #5

Slightly off topic, but I'm really frustrated with the state of software packaging these days. Every solution tries to solve the same problems (reliable dependancy resolution, reliable installation and removal) but they all try and solve it in different incompatible and flawed ways. Consider the following: I need a reliable way to deploy my app to clients. The popular options are: 1) Source code + Configuration syste…

You mean sort of like npm?

I wouldn't use npm as an example of a stellar package manager.

Re: Canonical bringing Snappy Ubuntu to phone and desktop

#10

Post by edude03 » Wed, Nov 04, 2015, 4:54 PM UTC

hasenj wrote: post #6

edude03 wrote: post #5

Slightly off topic, but I'm really frustrated with the state of software packaging these days. Every solution tries to solve the same problems (reliable dependancy resolution, reliable installation and removal) but they all try and solve it in different incompatible and flawed ways. Consider the following: I need a reliable way to deploy my app to clients. The popular options are: 1) Source code + Configuration syste…

I think Docker is meant for dev ops, not for casual users.

It's supposed to be for devops, but in practice developers use docker as a way to solve dependency management on the server more so than to seperate instances of apps from each other. Especially with "microservices" it makes more sense to have docker available on the server and allow each team to upload a image with all the deps already baked in.