Estás usando un navegador desactualizado. Es posible que no muestre este u otros sitios web correctamente. Deberías actualizar o usar un navegador alternativo.
I've personally had the best results using Linux Mint MATE over the Cinnamon version. There's less QOL OOTB and slightly less intuitive GUI tools, but Mint MATE feels more "authentic" than Mint Cinnamon. There's something kinda crap and unrelaxed about how Cinnamon to this day is still categorically incomplete considering how regardless of how the Mint team, Fedora developers, or any other distro maintainers package Cinnamon, you still need to rely on GNOME applications on some measure. MATE is wholly complete unto itself by sheer virtue of forking off GNOME 2.32. Cinnamon was never a hard fork from the get-go; it was a wrapper around GNOME Shell that eventually became independent.
Honestly, if it was up to me and the tools would have held up- I adored KDE 2, and I stuck with them through 3.5, but that's when it all went to shit. I use Cinnamon because I'm old and it's comfortable. Otherwise, I'd probably still be doing wm2 and wishing I had a cut-and-paste service that actually worked between different toolkits.
I don't know what practical future XLibre actually has, but the fact that Red Hat and GNOME are losing their shit over its existence is enough to make me smile.
I don't know what practical future XLibre actually has, but the fact that Red Hat and GNOME are losing their shit over its existence is enough to make me smile.
With how much Xlibre development is outpacing Xorg development (is Xorg still unfucking their repository after ripping out metux's code?) it's clearly becoming a better option over Xorg. Some linux distros have already switched over and there are a few more considering it.
It has a decent number of active contributors and it hasn't lost steam, I think they're in the phase of building a track record of being reliable and stable, the crowning achievement would be getting Linux Mint to consider it.
Fuck Lunduke. He is just a grifter who has been around for ages and is an unflushable turd.
I still remember him claiming Google was censoring his blog back in the late 2000s, but he had a malicious iframe on his site, which means that Google will remove you until you fix your stuff.
I don't know what practical future XLibre actually has, but the fact that Red Hat and GNOME are losing their shit over its existence is enough to make me smile.
And yet it is far more active and stable. There’s 30 regula contributors to Xlibre and what three for Xorg? The clankers say there’s only two active Xorg contributors right now. Xlibre development is outpacing Xorg by a lot.
And Xorg is still depended on by many distros such as the BSDs. You cannot “sunset” unless there is a replacement that can do everything Xorg can and better, and Wayland is not that replacement. It would be like if Linus declared the Linux kernel sunsetted and that everyone should switch to NetBSD or something.
No shit. A project (Xorg in this case) that is in maintenance mode will have fewer resources dedicated to it.
This doesn't change the fact that the only reason Xlibre exists is because it is a protest against Wayland and Xorg being put into maintenance mode.
It is only being adopted by distros and OSes which are either extremely niche or are protestware themselves.
I don't really give a shit whether the graphics work via X or Wayland. I am using Wayland with GNOME 50 currently; a couple of weeks ago I was using Cinnamon with X.
Funny story, also giving away how old I am. In college we had a couple rooms full of dumb terminals. Students would run vi and then not know how to exit. So you'd walk in and most would be full, and someone would say "Oh, that one's locked up". One Escape :q! and you had a terminal. The power switch also did nothing as it didn't disconnect the serial session. I think there was an idle timeout so they would eventually drop the session but it was fairly long.
There were extensive regressions in the codebase caused by the guy who started XLibre. So they rolled back to a well-known good point and started cherry-picking stuff back in that didn't cause those regressions.
I just reminded myself of some of the issues. One of them was Xorg couldn't be built on BSD or Solaris. Another major bug I was experiencing myself. was the desktop geometry not updating when another monitor was plugged in.
There were extensive regressions in the codebase caused by the guy who started XLibre. So they rolled back to a well-known good point and started cherry-picking stuff back in that didn't cause those regressions.
I just reminded myself of some of the issues. One of them was Xorg couldn't be built on BSD or Solaris. Another major bug I was experiencing myself. was the desktop geometry not updating when another monitor was plugged in.
His code worked fine, they chose to have a hissy fit instead of going through the commits one by one. If there ever was an issue with the commits they wouldn’t have merged them. So instead they ripped them out and oh wow 20% of the other commits relied on them so now their branch is completely fucked and they don’t have the manpower to fix it. They only reason it’s not immediately noticeable is that the distribution branch has been out of sync with the master branches for the past five years and has thousands and thousands of fixes not merged.
They don't seem to have proper testing to catch these regressions. Stuff can look ok in code review, get merged and introduce subtle bugs. This happens all the time in software projects.
A guy I worked with forgot to update a Makefile yesterday, and some tests weren't running and code got broken, and I am going to have to fix it tomorrow. He made an honest mistake, and I compounded that mistake when I approved the code and merged it. I literally check MRs line by line.
So instead they ripped them out and oh wow 20% of the other commits relied on them so now their branch is completely fucked and they don’t have the manpower to fix it.
That isn't that they did. They got a new branch from a known good point and reapplied commits via cherry-picks. So your characterisation appears to be incorrect. BTW, you've done this consistently in your replies to me. So I can't take what you are saying seriously.
I have done something similar on legacy codebases myself when someone tried "cleaning it up". So this lines up with my own personal experiences. So what am I supposed to believe? That the "wokesters, DEI and all that other crap are all conspiring against based X gigachad" or that the master branch was broken, like that commit log I linked above says? I'm going to take the latter, as there is actual evidence.
