Re: Fedora/RedHat is moving is a similar direction

Now, if you want to discuss bundles vs packages, then, you should
start another thread.





2015-08-24 20:23 GMT+02:00 Trans <[email protected]>:
>
> Ah, good point. But perhaps that makes sense for a more secure (not to
> mention less error prone) system. When something is too big to bundle,
> then one depends on secured services instead of shared libraries. That
> the idea?

When I said standalone, I didn't mean that every single application
must not need anything, there may be times where they may need other
things (in cases like modular applications or servers), is just a
simplification of the  bundle concept. How it's done it depends on
those behind the project and the capabilites of the bundling system.

>> - They plan to use snapshots, tying them to btrfs, something I don't like,
>> as I find btrfs slow for desktops ( though I think my opensuse has it and I
>> don't find slow at all)
>
> I didn't catch this. And I don't like the sound of it either.

Btrfs is a *new* file system (just like EXT4, the one tipically used
today), which features a lot of promising features (Copy On Write,
Compression...) one of them being snapshots, which are pretty much
like backups, with the advantage that btrfs only keeps differences not
all the files several times. e.g: If I make a snapshot of a folder
which have two files, then I can ask btrfs to make a snapshot out of
that folder, so if I modify one file and add another one I can access
the new folder and thanks to the snapshot the other one as well, the
main difference from a standard copy is that btrfs will only keep the
differences (the differences made to the file, and the new file) while
the a standard copy would just have two copies of everything (ignoring
if is duplicated or if it is not), you can even modify the snapshots
just like any other folder. If you are curious I suggest you to search
info about btrfs.

> > - They want to have a fixed base (what they call runtimes) leading to
> > greater use of disk space and (potientially) of RAM.

> I didn't quite understand what they were talking about with runtimes.
> Are these like Docker images?

(I don't know much about docker so there's a possibility I'm wrong)
Based on what I have read they serve the same purpose on a different
level, images are barebones OSes, and provide a base upon which the
application runs, runtimes are basically the same: a set of libraries
provided by someone (GNOME, KDE ...) which include a set of libraries
which application can base upon them, everything not included by these
runtimes must be incorporated by the application.

> Oh, what did you think of the way they organized data, config and
> cache directories all under a single per-application directory?
Truth be told when I read this I jumped some parts, one of them the
one telling this, so thank you for making me read that. I think it's a
very good idea, though I wonder how will they manage having multiple
versions of the same app with incompatible configs or other things, I
like the ability to have more than directory (by changing the
variables), as this gives (in an automatic and transparent way) a way
of having more than one application profile.

> _______________________________________________
> gobolinux-users mailing list
> [email protected]
> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users


--Sergio