Honestly this is the kind of thing we needed from React os. It would of been nice to be able to run the react is kernel in the background and then have wine make calls to it.
I think end-to-end refers to the “open source”, not the GPU acceleration. I know GPUs have always been a black magic to get working and so you often have to use proprietary, closed-source blobs from the manufacturer to get them to work.
The revolution that this is bringing seems to be that all that black magic has been able to be implemented in open-source software.
Could be wrong though, that’s just how I interpreted the article.
Yup, it’s definitely about the “open-source” part. That’s in contrast with Nvidia’s ecosystem: CUDA and the drivers are proprietary, and the drivers’ EULA prohibit you from using your gaming GPU for datacenter uses.
You will never be a real display server. You have no hardware cursors, you have no xrandr, you have no setxkbmap. You are a toy project twisted by Red Hat and GNOME into a crude mockery of X11’s perfection.
All the “validation” you get is two-faced and half-hearted. Behind your back people mock you. Your developers are disgusted and ashamed of you, your “users” laugh at your lack of features behind closed doors.
Linux users are utterly repulsed by you. Thousands of years of evolution have allowed them to sniff out defective software with incredible efficiency. Even Wayland sessions that “work” look uncanny and unnatural to a seasoned sysadmin. Your bizarre render loop is a dead giveaway. And even if you manage to get a drunk Arch user home with you, he’ll turn tail and bolt the second he gets a whiff of your high latency due to forced VSync.
You will never be happy. You wrench out a fake smile every single morning and tell yourself it’s going to be ok, but deep inside you feel the technical debt creeping up like a weed, ready to crush you under the unbearable weight.
Eventually it’ll be too much to bear - you’ll log into the GitLab instance, select the project, press Delete, and plunge it into the cold abyss. Your users will find the deletion notice, heartbroken but relieved that they no longer have to live with the unbearable shame and disappointment. They’ll remember you as the biggest failure of open source development, and every passerby for the rest of eternity will know a badly run project has failed there. Your code will decay and go to historical archives, and all that will remain of your legacy is a codebase that is unmistakably poorly written.
This is your fate. This is what you chose. There is no turning back.
I’m not enormously bothered by the designs themselves; the new logos look fine, although I preferred the old logo.
But what really bothers me is that they’ve gone with a whole disjointed mess of different designs for each of their sub-projects. Why on earth wouldn’t you take this opportunity to design a coherent family of logos? Bizarre missed opportunity.
I think that one is the only logo with any soul to it. The rest are so flat! I like the old opensuse logo, but I get that it doesn’t fit with the rest.
Finally, I might try disabling XWayland once wine wayland ships in proton. The only remaining apps using X11 on my system are electron apps and wine (oh, I forgot Java).
It’s interesting to finally see all the work on wayland coming together. Only a few years ago I still had to switch back to i3 because sway didn’t work well for gaming (no vrr, dmabuf), and now it’s only a few things missing.
I wonder if they consulted Plasma devs about it. Sure they said that they aim to make Wayland ready for Plasma 6, but it didn't sound like it was an actual plan for 6.0. After all they got their hands full with Qt 6 porting, and there are still major roadblocks with completing Wayland support, while 6.0 is about to have its alpha release already.
Knowing Fedora devs however, I suspect they didn't. They switched to Plasma Wayland by default several Fedora releases ago, when it was in no way ready. I guess I will switch to a different distro when this time comes.
Yeah, as usual the opinionated crew are making something that one may even like feel like it’s forced down everyone’s throat (see: systemd, snap…) and making everything worse. I don’t see how any Linux desktop distro worth its salt can get by ignoring 90% of the PC GPU market share and essentially forcing them into an inferior desktop experience for pure ideology’s sake, and I LIKE Wayland. I even put up with all its quirks in a particularly quirky implementation (KWin). But this ain’t it if you want users to use your OS.
I find GNOME’s “must be perfect” approach to accepting new code counterintuitive.
One of the largest benefits of having a clean architecture is increased velocity and extensibility. What’s the point in nitpicking over perfection when it takes literally years to merge a feature, arguably one considered basic and essential by today’s standards?
KDE is on the other side of this pendulum, integrating everything and resulting in a disjointed, buggy disaster.
Where’s the middle way? It used to be XFCE. What is it now?
Quality control is important for a project that is going to be supported for long time, and used by many. Slow but steady is a right approach for open source project, IMO.
I definitely get what you mean, and sometimes agree, but tbh I’m glad Gnome is an option for those who want a DE that is uncompromisingly UX-focused and straight up won’t accept changes until they’re damn sure it’ll be production-ready.
And while they’ve been relatively slow in getting adaptive refresh working, they’ve been very quick with some other things. Idk why it took them this long to sort out the cursor occasionally becoming out of sync with displayed content’s refresh rate, but there must be a reason for it.
Gnome was at the forefront with Wayland, PulseAudio, they’ve been the biggest pusher of Portals, pretty much all of their GTK4 apps have been designed to also be compatible with mobile devices. Accessibility features on Gnome are also pretty great for a Linux DE.
As a general rule, I’d say their development process works well, despite there being the occasional holdup.
And while Plasma obviously isn’t nearly as bug-free as Gnome, it’s come a long way since the Plasma 4/early Plasma 5 days. I still don’t feel I can depend on it the same as I could for Gnome or Cinnamon (compositor crashes bringing down all open apps is a big issue in particular - and is finally due to be fixed in Plasma 6), but don’t underestimate their progress — since like 5.15/5.16 they’ve improved leaps and bounds.
And with 6 it looks like they’ve learned from the mistakes of 4 and 5’s launches.
Looks nice. Is anyone able to tell if I’m going to screw up my KDE install if I try it out? I’ve never tried WM / compositors on KDE that weren’t targeting KDE before.
It should be fine I think. On Linux you can have multiple Desktop Environments installed (ex KDE Plasma & Gnome as well.)
I tried Hyprland a few months ago like this. I had Plasma installed then installed hyprland as well. During login with SDDM you can select which DE to launch.
Edit: On github it says you should install it alone to make sure. I dont know then, maybe it works? I am still new to Linux as well.
That sounds great. The last driver they released fixed Starfield but broke Cyberpunk for me, pretty bad trade. Hopefully this rolls around to my distro soon
Undoubtedly Wayland is the way forward and I think it’s a good thing. However I wouldn’t piss all over X because it served us well for many years. My LMDE 6 still runs X and probably will for the next 2 years at least because both the Mint Team and Debian team don’t rush into things. They are taking it slow, testing Wayland to make sure no-one’s system breaks when they switch to Wayland.
This is the best approach. Eventually it will all be Wayland but I never understood why this is such an issue. Like any tech it’s progress, no need for heated debates. It’s just a windowing system after all.
phoronix.com
Top