summaryrefslogtreecommitdiff
path: root/published/fedora23review.txt
blob: 24e8b6bdfaf1e2040d2e18cc6b02268f41d45308 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
The Fedora project recently released Fedora 23. The last time Ars looked at Fedora was two releases ago, [Fedora 21](http://arstechnica.com/information-technology/2015/01/fedora-21-review-linuxs-sprawliest-distro-finds-a-new-focus/), which saw Fedora introducing its "Fedora Next" plan. 

Fedora Next's goal was to bring the massive, sprawling entity that is Fedora into some neatly organized categories that would clearly define each of Fedora's aims. Since Next launched, Fedora has been busy doing just that and the results are impressive. 

Fedora Next's structure is like a series of concentric rings where each ring is supported by the one inside it. At the center are the core components of the system, APIs that applications hook into and so on. On the outside are the visible layers that users interact with, what Fedora calls "Environments." It's this last layer that users interact with. For Fedora 23, as with the two releases prior, those Environments consist of Workstation (Desktop), Server, and Cloud. The latter still has the feel of an also-ran, but the Workstation and Server releases see quite a bit of welcome new packages in this release, particularly the GNOME-based Workstation.

## Fedora 23 Workstation

The biggest change in Fedora 23's default Workstation release comes from upstream in the form of GNOME 3.18. But before you get to enjoy what's new in GNOME 3.18, you have to get Fedora installed and to do that you have to make it through Anaconda. 

In the Fedora 21 review I gave Anaconda a hard time, its button-based approach felt clunky compared to similar offerings from other distros. Most of those criticism stand with Fedora 23. For example, it still takes an extra click of the button to create a user account on the desktop when everyone installing Fedora 23 Workstation will need an account -- why not just present a screen to create one?

Two things in Fedora 23 make Anaconda a bit more tolerable though. First, it's better at guessing defaults. For example, it successfully set my timezone and keyboard preferences with no input from me at all. That's one win for the button based approach since there was no need to click those buttons. Provided you stick with single partition, the default disk partitioning setup in Fedora 23 also may not require much input on your part either, which is nice. The second change that makes Anaconda a bit better this time around is a new orange bar across the bottom which helps call your attention to any unfinished business you may have in the installer, for example, creating that user account.

It's a marginal improvement over past releases, but I stand by my last assessment: the best you can say about Fedora's installer is that you only have to use it once. 

### GNOME 3.18

Once you get past Anaconda, Fedora 23 will land you in what might well be one of the nicest, and certainly one of the newest, GNOME desktops around. 

Fedora 23 ships with the just-released GNOME 3.18, which is one of the best GNOME releases to date and features dozens of new features, better Wayland support and a new option to update your firmware through GNOME Software. Regrettably it also, as all GNOME releases seem to, has a few steps backward.

The first thing you'll likely notice when you set up Fedora 23 Workstation is the new Google Drive integration in GNOME 3.18. Google Drive joins Facebook and Microsoft in the GNOME online accounts panel (along with what I like to hope is the more popular option for Linux users, ownCloud). The new Google Drive support makes all your Google documents into first class citizens on the GNOME desktop. 

To set up Drive all you need to do is follow the prompts to sign in to Google and authorize GNOME to access your account. In about 10 seconds you'll have complete access to everything in your Drive within the GNOME Files app (AKA, Nautilus). Your Google Drive account is displayed as a network share in the file browser sidebar. Interacting with your Google Drive documents is no different than local documents. You can set your documents to open in any application you like (by default they'll open in the web editor) and creating new files and folders in Drive is just like it is for ordinary drives. Like the ownCloud integration, Google Drive in GNOME, "just works".

There's still no Google Drive client for Linux, but for GNOME users anyway, GNOME's integration is good enough that you won't miss it. If you're not a Google Drive user there's nothing to see here other than the possibility that now that Drive support is done perhaps the GNOME team can move on to integrating other online sync services.

Support for Drive isn't the only thing new in the Files app, although it is the only thing that's new and good. The other change, while relatively minor, is yet another step backward for usability in GNOME. The file copy dialog has been moved to a tiny icon at the top right of the file browser window. An indicator circle animates large file copy operations and clicking the icon reveals more details and a drop down that looks roughly like the file copy dialog you'd see in most other applications. It works quite well enough *if you know it's there*. If you don't know, well, good luck finding any feedback on what your machine is doing when you drag and drop files. 

For example, if you're backing up say your photo folder with many gigabytes of data to an external drive you might accidentally copy it 3, perhaps even 4, times before you realized that, despite the totally absence of feedback, something is in fact happening. Don't ask me how I know this, just know that you will not suffer the same because now you know -- look for the tiny icon. At least GNOME is getting closer to its goal of making the command line look downright discoverable. 

This release will also send you hunting for your network drives since those no longer appear in the sidebar by default, to, in the words of GNOME's announcement, "reduce clutter". Instead those drives now require an extra click on the new "Other Locations" menu item which will reveal all that unsightly clutter should you actually need to access those cluttered drives.

There is one other actual improvement of note in the UI of GNOME 3.18, which is that you can now search by typing in open and save dialogs. One step forward, two back.

Most of the other big changes in Fedora 23 and GNOME 3.18 are less visible, though more welcome.

Fedora has long been an early adopter of Wayland and Fedora 23 is no different, offering considerably more support than any other distro to date. In fact the Wayland support is getting close enough to feature complete that it appears Fedora 24 may boot to Wayland by default. By and large you won't notice much difference should you try out Wayland in Fedora 23 (just logout of your current session and select Wayland from the menu that drops down from the gear icon at the lower right side of the login dialog). The lack of noticeable difference is a good thing since you really shouldn't need to know what your display manager is up to, but there are some new features available if you need them.

The most notable thing Wayland can do right now is run DPI-independent monitors. That is, if you have a normal resolution display and something more like a 4K display, Wayland can handle that scenario. Not having a high-res monitor I haven't been able to test this one, but the GNOME forums are full of success reports. Other new Wayland-specific features include trackpad support for gestures like pinch-to-zoom, twirling to rotate and four-finger swipes to switch workspaces. All of these gestures were previously available if you've got a touch screen, but they're now available to supported trackpads under Wayland. That said, I wasn't able to get them working in Fedora 23. 

Fedora 23 does support GNOME 3.18's new "automatic brightness" support, which taps your laptop's integrated light sensor to automatically dim and brighten the screen based on the lighting around you. It saves fiddling with the brightness buttons and can help cut down on power use since it will dim without you having to remember anything. However, if you're really trying to eke the last bit out of your battery you'll probably want to disable automatic screen brightness in the power settings, since it tends to err on the brighter side. Most of the time though this feature works well.

There are quite a few notable updates for GNOME's stock applications, as well as two brand new applications -- Calendar and GNOME To Do. Possibly the best part though is that GNOME Software now supports firmware updates via fwupd. That means you don't need any proprietary tools or original install DVDs just to update your firmware, provided of course that the firmware you need is available via the <a href="https://http://www.fwupd.org/">Linux Vendor Firmware Service</a>.

As a side note, Ubuntu users, take a good look at GNOME software, it's in your future. Canonical has decided to abandon its homegrown software center in favor of GNOME software for Ubuntu 16.04. First Upstart gave way to systemd, then Unity 8 moved to Qt, then the scrollbars went to stock GNOME and now the Ubuntu Software Center is abandoned in favor of GNOME Software... makes you wonder about Mir.

GNOME 3.18 adds two new default apps to the ever-increasing GNOME app suite, Calendar and GNOME To Do. The lack of a good GUI calendar app for Linux has always been puzzling. There's Evolution of course, but until now there hasn't really been a nice simple stand alone Calendar app. GNOME Calendar is that app. Or rather, it's close to being that app. If you stick with the integrated GNOME online accounts -- Google Calendar, ownCloud, etc -- Calendar works as expected. Regrettably I have not been able to get it working with any of my CalDav servers, including my primary calendar which resides on Fastmail's CalDav servers.

The other newcomer is GNOME To Do (not to be confused with the older, independent application launcher, GNOME-Do), which is, as the name suggests, a to do list manager. GNOME To Do is still a "technical preview" in GNOME 3.18, but it has most of what you'd want in a task manager application. You can enter new tasks, group them, add colors and priorities, and attach notes to them. Tasks also integrate and sync with, for example, Gmail's Tasks. It was perfectly stable in my testing (including syncing with Gmail), but bear in mind that it is still a preview release -- you might not want to trust your entire life schedule to it just yet.

I should also note that while Fedora mentions both new GNOME apps in its release notes, in the case of the live CD I used to install Fedora 23, neither were installed by default. They're both in the repos though and thanks to GNOME's helpful ability to search for apps not installed yet they're easy enough to install on your own.

The last big update of note in Fedora 23's GNOME desktop is support for what might be the biggest change coming soon in the GNOME world: the <a href="https://wiki.gnome.org/Projects/SandboxedApps">Xdg project</a>. Xdg is a new effort designed to help developers build and distribute Linux applications. Ultimately Xdg wants to be a kind of one-package-to-rule-them-all, that developers can use to package apps across distros. Xdg will also add some much stricter application sandboxing. 

In Fedora 23 Xdg is not much more than an outline. None of the apps that ship in Fedora's repos are packaged this way yet, but Xdg does indeed look to be part of the GNOME roadmap, which likely means Fedora will be an early adopter as Xdg expands.

## Kernel

Like the recently released [Ubuntu 15.10](arstechnica.com/information-technology/2015/11/ubuntu-15-10-review-wily-werewolf-leaves-scary-experimentation-for-next-year/), Fedora 23 ships with Linux Kernel 4.2. The biggest news in 4.2 is support for recent Radeon GPUs and  Intel's new Broxton chips, though let's face it Fedora running on mobile chips is about as likely as this being the year of the Linux desktop. 

On the more useful side there are some new encryption options for ext4 disks and the new live kernel patching features. The encryption features should make using [whole disk encryption a bit faster](https://lwn.net/Articles/639427/).

Other under the hood changes in Fedora 23 include some improvements for Fedora's new DNF package manager, which replaced Yum a few releases ago (Yum is aliased to DNF now). With this release DNF takes over from `fedup`, becoming the new way to perform system upgrade. Aside from the welcome unification of purpose -- that Fedora had to build a separate tool for system upgrades says something about Yum -- DNF's new upgrade support hooks into systemd's support for offline updates and allows you to easily roll back updates if necessary.

## Server

Fedora 23 Server includes everything found in the Workstation release (minus the desktop itself) and layers in some great tools for sysadmins, most notably Cockpit. Cockpit is Fedora's effort to bring the tools of the sysadmin into an interface anyone can use. Want to deploy a Docker container? Search for what you want, click install, done.

Cockpit also feels a bit like a covert effort to build a more secure web since it makes deploying secure servers something that anyone with a bit of Linux experience can figure out. Cockpit is really just a graphical interface layered on top of all the, let's face it, often inscrutable tools, sysadmins already use. Cockpit adds a welcome layer of abstraction and while it isn't a substitute for experience, it can point you in the right direction. 

Fedora 23 Server beefs up Cockpit security with support for SSH key authentication and the ability to configure user accounts with authorized keys. 

In this release Fedora rolekit gains the ability to deploy [Server Roles as containerized applications](https://fedoraproject.org/wiki/Changes/Containerized_Server_Roles). This allows better isolation of roles from the rest of the system and paves the way for roles to migrate into cloud-based systems like Fedora's Project Atomic.

## Conclusion

Fedora 23 is such a strong release it highlights what feels like Fedora's Achilles heel -- there's no Long Term Support release. 

If you want an LTS release in the Red Hat world it's RHEL you're after (or CentOS and other derivatives). Fedora is a bleeding edge and as such Fedora 23 will, as always, be supported for 12 months after which you'll need upgrade.

The good news is that DNF's new upgrade tools with transactional updates and rollbacks temper the missing LTS release a bit. After all, if updating is simple and you can roll back if something goes wrong then there's less risk to updating. Still, what if you do need to rollback because something went wrong? What if that something isn't something you can quickly fix?

The lack of an LTS release isn't likely to stop desktop users, but it does make Fedora feel like a riskier bet on the server. In the end though, that's probably how Red Hat likes things, if you want stable RHEL is there, if you want the latest and greatest, Fedora 23 delivers.