Few ago days we share here on the blog the news about the discussion that was taking place internally among the Fedora developers, in which they commented on the change from editor vi to nano.
And it is that implementing the default use of nano instead of vi is due to the desire to make the distribution more accessible for beginners by providing an editor that can be used by any user who has no special knowledge of the working methods in the Vi editor.
At the same time, it is planned to continue with the delivery of the vim-minimal package in the basic distribution package (the direct call to vi will remain) and provide the ability to change the default editor to vi or vim at the user's request. Fedora does not currently set the $ EDITOR environment variable, and by default in commands like "git commit" it is called vi.
And well after a lot of talk, the developers accepted the change and it will be applied to the next version of Fedora, which is version 33.
In addition to this, the change from EXT4 to Btrfs was also discussed on the other hand in which the Fedora Engineering Steering Committee (FESCo), which is responsible for the technical development of the Fedora distribution, approved a proposal to use the default Btrfs file system on desktop and portable editions of Fedora.
In addition to this committee also approved changing the layout to use the default nano text editor instead of vi.
With these decisions made as of Fedora 33 the Ext4 file system will be changed to Btrfs by default. This is not a major revolution or an irreversible step, but sunor a change in the default installation settings system, which in principle will not affect people who upgrade from previous Fedora or those who do not want Btrfs. Since they simply stick with your preferred file system.
The reasoning for the change to Btrfs, is that this will add new capabilities and also better address space saving situations non-standard for users.
Btrfs has some features that are useful nowadays such as copy-on-write snapshots, transparent file system level data compression, optimization for SSD, native RAID support, already indicates better space management, a more sophisticated checksum system, I / O isolation via cgroups2, support for online partition reduction and simplification, and easier field configuration.
Using the built-in Btrfs partition manager it will solve the problems of running out of free disk space when mounting the / and / home directories separately.
Besides that they argue that another great advantage is la ability to resize partitions online, including downsizing, even in terms of possible systemd-homed integration.
Finally, Btrfs simplifies the management and operation of complex storage systems and adds efficient replication, incremental backups with Btrfs send / Btrfs receive etc.
As for other changes that are still on the table and that is still arguing, is the subject of discontinuing support for booting using classic BIOS and leave the option to install only on systems that support UEFI.
This, was put on the table, since it is observed that the systems based on the Intel platform have been shipped from UEFI since 2005, and by 2020 Intel planned to stop supporting BIOS on client systems and data center platforms.
The discussion about rejecting BIOS support in Fedora too is due to the simplification of the implementation of selective display technology from the boot menu, in which the menu is hidden by default and is shown only after a crash or activation of the option in GNOME.
For UEFI, the necessary functionality is already available in sd-boot, but when using the BIOS it requires patches for GRUB2.