On Sat, 2020-06-06 at 02:09 +0200, Kevin Kofler wrote:
> Igor Raits wrote:
> > The change says it will use 50% of user’s RAM size, but not more
> > than
> > 4G.
> But if the machine has only, say, 4 GiB of RAM, then the amount of
> extra RAM
> you get that way might not be sufficient to avoid OOM.
> > On Fri, 2020-06-05 at 08:54 +0200, Kevin Kofler wrote:
> > > Also -1 to adding something to the core system that is written in
> > > a
> > > language
> > > for which we do not even have dynamic linking support. Or even
> > > real
> > > static
> > > linking support, as opposed to packaging libraries as source
> > > code.
> > This is not fair. It is a programming language that is safer than C
> > and
> > is already used by some projects that we ship. rpm-ostree, firefox,
> > librsvg2 and others.
> 1. librsvg2 and firefox are not really core system components. They
> UI-related packages (an image processing library and a web
> which is at least one layer higher.
> 2. rpm-ostree is only a core system component if you use an ostree-
> installation. In the default Fedora system, it is not.
> 3. I think that it is a bad enough precedent that even these packages
> using Rust. We do not have a reasonable way to package software
> in Rust. Packaging libraries as source code is not reasonable in a
> distribution. (And yes, I was opposed to the Go packaging
> guidelines from
> day 1, and the Rust packaging guidelines copy the same broken
> so I am opposed to those as well.) As a result, shipping Rust
> software in
> Fedora is very painful, because everything is essentially
> linked (actually compiled on demand at application compile time
> and then
> statically linked into the application).
Why is it painful? You have all dependencies packaged that follow
semver (not like Go) and it is quite easy to build those packages.
Another example here could be nodejs, even though it does not link
statically it is just PITA to package since ecosystem is just full of
very small libraries that do not really like to cooperate so you need
to have tens of different versions of a lib in a repo. I consider this
much bigger problem than the Rust has in Fedora.
> 4. The Rust toolchain is also inherently foreign on Fedora because it
> is not
> based on GCC (but on LLVM).
That way you can say that mesa is foreign because it uses LLVM. If
there is ever alternative compiler to Rust that is based on GCC and has
feature parity, we can definitely consider trying it out. But the
referene compiler works just well.
> Core system components should be written in C. The higher layers (UI,
> CLI tools, etc.) can use C++ as well. IMHO, any other programming
> is just a pain.
We also have Fedora CoreOS that uses
that are written in Rust as well and
those are core system utilities.
Sure, but Fedora CoreOS is not Fedora. Err, not Fedora, the distro. This is
yet another example of how throwing all of these toys under the Fedora
umbrella can sound confusing.
John M. Harris, Jr.