gaearon

// While I claim this is a drop-in replacement, it is a little bit slower.
// If you have hundreds of links, you might spend a few more milliseconds rendering the page on transitions.

// KNOWN ISSUES WITH THIS APPROACH:

// * This doesn't work great if you animate route changes with <TransitionGroup>
//   because the links are going to get updated immediately during the animation.
// * This might still not update the <Link> correctly for async routes,
//   as explained in https://github.com/reactjs/react-router/issues/470#issuecomment-217010985.

probonopd

Think twice before abandoning X11. Wayland breaks everything!

Wayland breaks everything! It is binary incompatible, provides no clear transition path with 1:1 replacements for everything in X11, and is even philosophically incompatible with X11. Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.

Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.

Feature comparison