Yep, one of the new features of the GNOME 3.14-running Fedora 21 is a preview of the next-generation, post-X Window Wayland display manager, and you can choose "GNOME with Wayland" in the login/session manager.
I'm running Wayland right now. I've heard the caveat many times: Not all applications will work in Wayland. But so far, every application I've tried (Firefox, Gedit, Transmission, FileZilla, VLC, Files/Nautilus, Liferea, Yumex, Google Chrome, Geany, even apps in Wine) has run in Wayland with no trouble.
I've been running Fedora 21 for a few days now, spending most of my time in the non-Wayland world of Xfce and GNOME with X, and the system is as solid as ever. And by that I mean pretty damn solid.
The only glitch I've had with Wayland has been in suspend/resume, which is pretty touchy anyway with my hardware. (I've probably written 50 posts about it since I got this laptop.) When running Wayland, the laptop will suspend and then resume, but I'm seemingly "detached" from my session and have to log in again. At this point I'm logged in twice. This doesn't happen in X. If this is the only thing I can find wrong with Wayland, I'll still consider it pretty remarkable.
Just from a "look and feel" perspective, GNOME 3.14 is working better and faster than version 3.10 did in Fedora 20. I'm not saying I'm going to throw Xfce over for it, but the environment is more usable than ever. I moved to the Adiwata Dark theme while still in F20, and everything looks that much better in F21.
As I've said since I began running Fedora 18 on this laptop and upgrading via Fedup to each subsequent release, a system as forward-looking as Fedora shouldn't be anywhere near as stable as it is. It's a tribute to the developers for Fedora and the many upstream projects that go into the distribution.
Today marks only nine days since Fedora 21 went stable, and my system is running like a well-maintained watch.
So if you think of yourself as the adventurous type, someone who likes everything to be pretty new all the time but doesn't really want to deal with a lot of breakage and is curious about Wayland in the real world, give Fedora 21 a try.
Later: You know what got fixed in Fedora 21 that was broken in F20? Mounting of Apple iOS 8 devices.
This paragraph is set off with tabs and has a Markdown-generated link:
This is my Ode site, [which lives here](http://stevenrosenberg.net/blog).
This paragraph uses "blockquote" HTML tagging and an HTML link:
This is my Ode site, which lives here.
This paragraph is set off with tabs and has an HTML-tagged link:
This is my Ode site, <a href="http://stevenrosenberg.net/blog">which lives here</a>.
None of this text uses the "code" tag.
So my question is, how do you call "blockquote" without "code" in Markdown?
So I haven't upgraded my daily-drive Fedora 20 system to Fedora 21, which was released two short days ago.
From what I can see, the RPM Fusion repositories are ready for F21. Google Chrome might break, but a quick removal and reinstall should fix that.
In F21, there will be many changes in the GNOME desktop environment and applications.
But for my go-to desktop environment, Xfce, it's going to be pretty much the same. (Yes, Xfce is moving glacially slow, and I've heard talk of people turning to the GNOME 2-inspired Mate desktop because it's under heavy development.)
My web browsers (Firefox and Chrome) won't fall behind. I get the latest versions from Fedora and Google, respectively.
I'm dabbling in Ruby, and F20 has version 2.0. F21 has 2.1, but at the level I'm at, it doesn't matter.
And now that all the heat is on F21, it's been relatively quiet, update-wise for F20. It's a bit closer to running Debian Stable. After awhile you get a few security patches here and there, but updates are quiet and quick.
Even an old (but still supported) Fedora release gets more updates than a current Debian Stable, but for the moment, I'm enjoying the ritual of staring Yumex and seeing either only a few or, better yet, no updates waiting to be installed.
Sure I'll move to F21. It could be tomorrow (probably not) or next month (you're getting warm). But what's the hurry?
I already use keys for some services, so I'm not completely in the dark, but I sense that between the Keybase web service and local command-line interface, this is something useful.
And sitting atop the Node.js heap is Joyent, the company where Node creator Ryan Dahl was working when he came up with the idea and the code to make it run.
So even though Node.js is an open-source project, its direction is largely guided by the for-profit Joyent. And that doesn’t sit so well with some Node users/developers.
As the io.js project’s “Read Me” text states:
"We intend to release, with increasing regularity, releases which are compatible with the npm ecosystem that has been built to date for node.js."
As InfoWorld previously reported the Node forking threat has been floating around for awhile, and in response Joyent created an advisory board to get more community input into what has become one of the most-used open-source projects in the world of web-delivered application development.
Fighting, infighting, forking and just plain grumbling is nothing new to open-source projects. Friction over the transition from Python 2 to Python 3, the never-ending gestation of Perl 6, everything about Linux distribution Ubuntu and its SABDFL (self-appointed benevolent dictator for life) Mark Shuttleworth since he moved the buttons from right to left, Debian and the now-raging debate over the systemd init system that’s so much more than an init system … and the beat goes on.
Most forks come to nothing. Just like ex-Microsoft CEO Steve Ballmer once said in all his sweat-drenched glory, it usually comes down to “developers, developers developers.”