News for hackers. Stuff that matters.

acgkmopvvgvmgv

Re:Make. It. Simple. Linux Desktop Usability on Thursday June 17, 2021 @02:35PM (#27542882)
>if no one shows up to fix them after years

>volunteers to work on them

This discussion happens literally every week on reddit and other places. Same arguments and same conclusions from both "sides", not worth having it, nothing is gained.

>GNOME's wayland implementation won't affect users of other desktops.

Affects developers, and GTK itself when used. Or not if you don't think they are issues of course.

Re:Make. It. Simple. Linux Desktop Usability on Thursday June 17, 2021 @01:47PM (#27542324)
Not interested in discussing merits and validity here but some bugs I have are US-age-of-consent-old. Some could be called features or are just UX changes or bad integration with WMs and KDE.

Well, outside my personal opinion that GTK applications became worse in UX and looks (by nature just by following their abstract HIG or peer pressure to be a "GNOME app"). The most common issue is the terrible filepicker (alien UX, no large thumbnails) that at least now you can use Portals when it's supported. Same could be said about other components like color chooser, modal dialogs, fonts that are barely readable even after KDE patches. Integration issues with Flatpak I only have with GTK applications like fonts and dbus. Some issues with Wayland, SDL, that I can't remember, maybe it was SSD, lack of window controls, abandoning system tray, I don't keep track of things that make my day worse now I just find an alternative until they come back to haunt me.

Re:Make. It. Simple. Linux Desktop Usability on Thursday June 17, 2021 @01:14PM (#27541961)
Isn't XFCE doomed to have many of the issues inherited by GTK 3 and now 4? Do they fork things or just accept their fate? Even more so with Wayland in mind.
Re:Make. It. Simple. Linux Desktop Usability on Thursday June 17, 2021 @01:10PM (#27541927)
Yes there are a good amount of people who genuinely enjoy GNOME but what that GNOME is I don't really know. Ubuntu is heavily customized. Pop!_OS too and they are even going to release their own version of it, maybe like a fork I don't know the details. Fedora patches GNOME and their applications. When I see comments from their own developers more often than not they are using extensions, patches and tweaks outside the settings app. How many people would manage to tolerate actual vanilla GNOME I have no idea.

Their UX research is like Lucky Strike paying someone to find the health benefits of tobacco. They will ask the right questions. I remember two posts about UX testing, one a developer asked like a few random people they knew before making heavy changes. The second one looked promising from a scientific point of view and made me genuinely interested but a couple of paragraphs in and you could already see that it was full of shit.

Repo owners can do whatever they want because they can't afford to lose a single maintainer so leaders just quietly accept that and move on. Source: GNOMErs comments on reddit.

So lots of politics, not a lot of money to be made in the desktop, people are spread too thin. You don't have to deliver a good product when there's no big expectations or your job is on the line.

Is this comment too harsh? I don't know. Red Hat (right they don't own GNOME) is great and did/does so much for Linux/desktop, but many people like me who abandoned GNOME and GTK after v3 have to deal with their bullshit on a daily basis because they control a lot of unrelated stuff. So it's really hard not to be.

Re:NixOS 21.05 on Wednesday June 02, 2021 @01:19PM (#27371372)
Nix and similar projects are all going to be eaten alive by immutable distributions, Flatpak and new projects - that might work just like Nix but get the user experience right, and make packaging and maintenance easier. And no I'm not saying they do the exact same thing, have all the same features or target the same type of users.

For the developer tools side I like what Shopify did but I would never recommend that to my employer. Too many moving parts and not enough people using it that I would feel safe about it.

Pretty sure 99% of regular people would be happy if there was a desktop with GNOME 2 feature parity but with a good Wayland compositor and probably some modern features that would come from that (multimonitor, VRR, ...).

I just can't understand how anyone could defend GNOME 3. Their own staff have to use extensions (that break every update), even Fedora (!!!) has to patch GNOME packages now.

They kept fighting that their workflow is superior and now they are going to change it all over next release. They keep butchering their toolkit, I can only use Qt applications now. Hell I'll take even Electron over GTK.

For me the Linux desktop with a WM is the perfect balance of exposing the internals and UX. It could be better but that's true to every OS, at least here I have my freedom. I'm keeping my eye on KDE, seems like they rewrote their less than ideal compositor (legacy X11 is a burden) and maybe in a year I could be using that.

I've once heard someone say that GNOME is Microsoft's favorite DE. You can guess why.

I was talking about XWayland and the other problems Wayland devs have mentioned like Pipewire, poor performance, current and future issues FLOSS developers can't fix on their own without being able to patch and only NVIDIA can fix them. A big waste of time for that extra path (even if initially sent by them) that I wish they didn't had to maintain and triage bugs.

The experience with glitches and problems that the user above just describe to you and I see every day on social media. And the blame went to Wayland. I don't claim to know how it works deep down I can only comment about the smell and it's not pleasant.

They promised many things years ago and we are still in the same situation. I will be the first to congratulate NVIDIA if they fix this issue and change their practices. I'm sure they have legit grievances with Linux developers but their behavior is awful if you're a user or want the desktop to succeed.

I wouldn't do that. Only move to Wayland when there is a real path for what you want and need. And it does it without hacks.

About porting I would look at what MATE is doing or at the code of Wayland shells, protocols or things like Waybar at GitHub. You don't have to write an entire compositor if you don't want to. Even better get in touch with the people who know what they are talking about, I think they have a wayland IRC channel.

Maybe I have reading comprehension problems but this article sounds so conflicting and presumptuous. Is it a sales pitch or not? If it is, even when it says it isn't, I would start by looking at Arcan's bus factor, and what refactoring and architectural changes were necessary along the years.

Having no expertise in this field I have no patience for people who write in this style but never got involved in the process. But if they did then I would be more interested in reading why their proposal was better and what can be done now in the living code. Also IIUC protocols are exactly that, places to experiment and learn from mistakes until they get stable and anyone can propose them.

There are many developers who could write a good technical solution but it's the ones who can deal with the ugly politics that make a real difference. There's a phrase about that there but as always if you don't send code your opinion won't do any good.

It came a long way, it's very impressive what they managed to do in a short period of time. Not only Valve but the community in general even if they weren't directly involved with the gaming part.

Manage your expectations, I would treat it like a console, you won't be able to play 100% of "PC" games but you will have a very large selection of games including AAA. And in comparison by raw numbers Linux have many more games than regular consoles, not to mention all the emulators you can use.

Performance wise Source engine games run better than on Windows for me and a few Proton (Wine) games runs better too, but that's not the rule as there is a small penalty from the "translation" layers. Vulkan games run very well.

If you try to run all games even the ones that Valve didn't approved to run with Proton ("1-click in the UI and it just works") you will have to tinker and do nerd stuff like using different versions or compiling from source. Don't blame the platform if you go that route without proper knowledge and patience. Also in the same line of thinking don't try to use Wayland yet, specially if you have a NVIDIA card because there's no support from them, and I hope they do something about that but I wouldn't hold my breath.

>Wayland won't be production ready in a long time.

With NVIDIA it will never be production ready because NVIDIA doesn't support the Linux standards for Wayland and they don't allow developers to write/use good open drivers and all functionality. Even with X11 and their closed drivers it's a bad experience with glitches in the desktop, but at least the games run.

Re:The X.Org Server Is Abandonware? on Sunday October 25, 2020 @01:11PM (#24887862)
Nice ignore the part where they realized Mir was useless. They even went on an edit spree in their wiki page.

If Mir was so good and superior they would just keep developing it. Isn't that obvious? If the company who already spent all this dev time aka money on Mir doesn't believe in it, why would anybody else? They were even eating their own dog food and had some major industry pull at their disposal. The answer is they fucked it up.

Re:The X.Org Server Is Abandonware? on Sunday October 25, 2020 @12:56PM (#24887721)
Canonical announced Mir out of nowhere in an attempt to gain control just like they are trying now with Snap. After the announcement of Mir their developers went to IRC and made abundantly clear they had no idea how Wayland works and that Mir was useless. Where is Mir now? Using Wayland.

People who were in the fence about supporting Wayland were now even more convinced they should ignore it. That's one of the reasons a decade later you still have this much FUD.

A good lesson for the anti-FLOSS crowd so heavily present in this website.

I'll be the first to admit Linux desktops are full of flaws (although there are other options), just like every other OS but they could be fixed given enough money or maybe you could be the one that write that code.

But an OS that is not FLOSS will always work against their users and restrict their freedom. It's also a big joke that they have so many ads talking about privacy, when they are just as bad as their rivals. I do understand that not everyone has a choice because specialized software that they need for professional use could be available only in other platforms and that's unfortunately.

I don't expect an utopic world where everything is FLOSS but the OS is too important to be closed. It will only get worse with time.

The worse Chromium gets the better. It will take decades to reverse the damage that HN and many web developers did by pushing a single browser engine instead of fighting back.

Next, Microsoft needs to get on top again and show Google how it's done. OG monopolism.

Finally some blood!

Re:Why is there only one Snap Store? on Thursday August 13, 2020 @03:27PM (#24147330)
It's not for nothing that Snap is considered dangerous by SUSE and is not officially supported. They even fail basic upstream responsibilities.

https://blog.linuxmint.com/?p=3906

> A year later, in the Ubuntu 20.04 package base, the Chromium package is indeed empty and acting, without your consent, as a backdoor by connecting your computer to the Ubuntu Store. Applications in this store cannot be patched, or pinned. You can’t audit them, hold them, modify them or even point snap to a different store. You’ve as much empowerment with this as if you were using proprietary software, i.e. none. This is in effect similar to a commercial proprietary solution, but with two major differences: It runs as root, and it installs itself without asking you.

> First, I’m happy to confirm that Linux Mint 20, like previous Mint releases will not ship with any snaps or snapd installed.