Re:How We Designed the Librem 5 Dev Kit with Free Software
by onli on Thursday January 10, 2019 @12:38PM
(#18875928)
That seems to work just fine under X...
[ Parent
| on HN ]
Re:How We Designed the Librem 5 Dev Kit with Free Software
by jniedrauer on Thursday January 10, 2019 @12:45PM
(#18876012)
Wayland definitely seems like the way forward. But we're in a weird in-between state where it's not fully supported by the ecosystem yet.
Etc.
Re:How We Designed the Librem 5 Dev Kit with Free Software
by chmln on Thursday January 10, 2019 @12:57PM
(#18876150)
Wayland is not the default on most Linux distributions for a reason and likely won't be for a while. Surprised to see it picked as a foundation as it is not mature at all, despite the protocol being around for a decade now.
Re:How We Designed the Librem 5 Dev Kit with Free Software
by jniedrauer on Thursday January 10, 2019 @01:19PM
(#18876388)
Wayland is the default on Fedora. I've been using it exclusively for around 2 years now. Every time I go back to X, I'm reminded of why I use Wayland full time.
The sooner adoption happens, the sooner the edge cases will be worked out.
Re:How We Designed the Librem 5 Dev Kit with Free Software
by chmln on Thursday January 10, 2019 @02:59PM
(#18877479)
> Every time I go back to X, I'm reminded of why I use Wayland full time.
Why's that? Genuinely curious as I always have the exact opposite experience.
I've found both gnome wayland and sway matching neither x11's features nor performance
Re:How We Designed the Librem 5 Dev Kit with Free Software
by jniedrauer on Thursday January 10, 2019 @04:05PM
(#18878155)
The main reason for me is HiDPI support. Scaling works extremely well in wayland, and I can set scaling per-display. HiDPI support on X is an afterthought at best.
Re:How We Designed the Librem 5 Dev Kit with Free Software
by ndnxhs on Thursday January 10, 2019 @07:27PM
(#18879941)
Does fractional scailing work yet. I have 1080p on a small laptop and the text is too small to read but 2x is huge. Currently I just have large text enabled in accessibility mode.
Re:How We Designed the Librem 5 Dev Kit with Free Software
by jniedrauer on Thursday January 10, 2019 @08:56PM
(#18880382)
It does, yes. Quite well. I have one of my displays at 1.5x scale.
Re:How We Designed the Librem 5 Dev Kit with Free Software
by rhodysurf on Thursday January 10, 2019 @04:44PM
(#18878560)
Its so much smoother for me as long as I dont use an NVIDIA laptop
Re:How We Designed the Librem 5 Dev Kit with Free Software
by AsyncAwait on Thursday January 10, 2019 @03:12PM
(#18877609)
At least on my AMD box, Wayland is considerably smoother than X.
Re:How We Designed the Librem 5 Dev Kit with Free Software
by gh02t on Friday January 11, 2019 @01:33AM
(#18881451)
It makes more sense when you remember that they are building the whole software stack, or at least have a lot of control over it. A lot of Wayland's issues are with backwards compatibility, but Librem doesn't have to deal with that as much, plus they have a defined set of hardware so driver support issues are much less of a problem.
Re:How We Designed the Librem 5 Dev Kit with Free Software
by _emacsomancer_ on Friday January 11, 2019 @01:01AM
(#18881341)
My only device actually running Wayland is my AsteroidOS watch.
Re:How We Designed the Librem 5 Dev Kit with Free Software
by abrowne on Thursday January 10, 2019 @12:59PM
(#18876177)
"The Librem 5 will be using native Wayland applications exclusively"
Re:How We Designed the Librem 5 Dev Kit with Free Software
by floatboth on Thursday January 10, 2019 @01:42PM
(#18876601)
If "DP-1 turns into DP-2", that's certainly a problem way below the X/Wayland layer.
Re:How We Designed the Librem 5 Dev Kit with Free Software
by onli on Thursday January 10, 2019 @03:39PM
(#18877866)
It sounds like an udev issue. But re-connecting displays works for me with USB-C. And Wayland has still very strange bugs, for example, on my workstation the login (powered by Wayland under Ubuntu) freezes upon selecting the user and again when entering a password until you move the mouse long enough in circles [0]. So somehow the user input treatment (and, secondary, rendering) is linked to the mouse input. If wayland can manage that, it can mess up on the xrandr layer equivalent and change the display enumeration.
[0]: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/177856..., I reported the bug