A good thing is not called rust

Many companies hate the OpenSource movement, especially the GNU utilities and the Linux kernel. Commercial companies buy out OpenSource services and companies. In 2018, control was gained over the OpenSource companies GitHub , RedHat .

However, the most powerful and crushing blow can be dealt by the manipulation of the minds of the end developers.

Barrel of honey

In May 2015, the first stable version of the Rust compiler was released . The development community appreciated the capabilities of the new language and everywhere began to switch to it.

Since August 2016, the Mozilla Foundation began implementing code written in Rust in Firefox and Thunderbird as part of the Oxidation project (translated from English as oxidation).

Since February 2017, Rust has become a mandatory addiction in Firefox and Thunderbird .

A little later, using Rust through the librsvg library became Gnome , Mate ,Gimp , LibreOffice .

In the future, if nothing is done, the number of projects using Rust will become more.

Spoon of poison

Rust - translated from English as rust. Rust is a negative, destructive thing.
Rust destroys metal, not creates it. A strange name for an ideal programming language, do not find tools of creation !?

As you know, the devil is in the details. Let's look at the distinguishing features of the Rust compiler ecosystem .

First of all. The compiler of the next ideal programming language cannot be compiled exclusively by means of the free compilers GCC, LLVM, GO, it is distributed as a blob.

Secondly. In the process of compiler self-assembly and program assembly from the “sources”, data is downloaded from the central repository.

A consequence of the above features, a standalone assembly of Rust by analogy with other programs for GNU / Linux, for example in the conditions of the sovereign Cheburnet, is simply impossible!

What will the impossibility of autonomous compilation lead to?

Failure to autonomously compile Rust will result in you being unable to build the Linux distribution from scratch on your own. As long as the programs for Xorg are affected by Rust, if Rust penetrates deeper then using their latest kernel versions and utilities will simply become impossible.

New versions of programs are not only new bugs and errors, but also fix old ones. Vulnerabilities are very often published publicly in the Common Vulnerabilities and Exposures (CVE) database . Attackers can take advantage of this and cause you material and moral damage.

How to deal with rust?

  1. To sound the alarm.
  2. Do not use Rust-dependent software versions.
  3. Patch and fork programs so that they do not depend on Rust.
  4. Write an alternative implementation of the librsvg library in C ++.

What will be the software of the future, FreeWare or OpenSource, is up to you! The challenge is thrown!

Only registered users can participate in the survey. Please come in.

How do you feel about the gradual "oxidation" of OpenSource?

Also popular now: