I play exclusively on kde wayland and I am really happy with it, I don’t have to mess with anything and everything works. The only thing that comes to mind is that Steam isn’t wayland native so you have to set an environment variable to set scaling on hidpi screens. Other than that everything works really fine!
It’s because Canonical has a vested interest in pushing the solution that they spent money developing.
As much as I appreciate everything that Canonical has done for Linux, this is the problem with trusting for-profit companies in the open source realm. Profit is their motivator. They don’t care that flatpak has better performance than snap, they just know they spent money developing snap, so they have to force it onto their users, despite it being the inferior tech.
I can’t believe how many people fundamentally misunderstand the spirit behind the GPL.
It helps to consider “the software” as a single snapshot in time, with the GPL’s intention that the consumer may make their own fixes, rebuild, and redistribute. Check.
Remember: “Free as in freedom, not free as in beer.” Selling open source software has always been explicitly allowed, as long as you make the source available to those who receive it. Check.
What the GPL does NOT provide is guaranteed access to maintenance and future versions of said software. Again, it applies to a snapshot, as delivered.
In a nutshell, the customer receives open source everything they FOR A PARTICULAR VERSION.
I see no problem — either in spirit or letter — in Redhat’s approach here.
This is debatable. The GPL allow redistribution of a given version of the software without additional restriction. If the user receives that copy knowing in advance that redistribution will lead to retaliatory actions this can be treated as an additional restriction.
Ok, yes as far as I understand they are not breaking the GPL, but it’s still a d**k move as it leaves downsteam projects/distros in a mess of a situation. While technically allowed, I’m with Jeff on this one.
You may not impose any further restrictions on the recipients’ exercise of the rights granted herein.
Red Hat are arguing that they are free to punish customers from exercising their rights under the GPL, and that punishment does not constitute a “restriction”, even though its done specifically to discourage people from exercising those rights. Whether Red Hat have found a loophole is something for the courts to decide, but it’s clearly against the intention and spirit of the GPL.
The GPL requires that you do not put additional limits on a user’s rights to redistribute.
Saying “you have the right, but we’ll cut ties” isn’t really in keeping with the spirit of that.
I suspect, if it ever ended up in court, they’d agree yhat there’s no guarantee of access to future versions, but that doesn’t mean that it isn’t a shitty and cynical take that flies against what FOSS has traditionally stood for.
We can agree to disagree. “The Software” was delivered, source included. And you as end consumer are free to redistribute and maintain as you wish.
However, I cannot see any contract law judgement that would force continuation of a subscription model on the vendor (in perpetuity!) if they do not wish to remain under contract.
Arch is a bad distro for newbies. Go find an ISO for Kubuntu and install that. The install wizard is idiot-proof. I use KDE-based distros like Kubuntu even though I’m a fairly advanced user so don’t view it as some kind of failure. There’s no virtue in using more complicated stuff. Get comfortable with the easier distros first.
I am a fairly long time emacs user, used it as my primary editor and note taking app for around six years. I have a config large enough to warrant its own git repo separate from my normal dotfiles.
Before emacs I used vim for several years.
After really getting into Rust, I decided about three months ago to just take a look at helix and see what it was about… and I haven’t opened emacs or vim again since.
LSP and tree-sitter cover like 90% of what my old config was doing out of the box, and the kakoune inspired key bindings just felt so natural. I feel at home without the overhead of configuration paralysis.
Don’t get me wrong, helix has plenty of room to grow, but I’m excited to grow with it.
I sometimes play around with Helix and I almost always have a good time, but there are too many vim features that I have integrated in my workflow that there isn’t any good equivalent to in Helix. I use ex commands, the quickfix list, snippets, the fugitive plugin and just little custom commands and mappings that I’ve accumulated. I don’t see myself switching to any editor full time that doesn’t have a replacement for most of these features, but Helix is very nice and fun to use occasionally.
I’ve been in your shoes a few months ago. I tried a few distros in VMs and ended up using OpenSUSE Tumbleweed. It comes with different GUIs and I decided for KDE. As a beginner TW helped me with the built in snapshots mechanism. So before I did anything, I took a snapshot, did it, and if I fucked up, I could easily rollback and try again. Since TW is a rolling release, I now make a snapshot before and after the system update So I always have some stable Rollback snapshots. Gives me so much safety to fiddle around and learn more about Linux. Been loving it so far.
Make heavy use of ChatGPT. I’ve been chatting about Linux with it for months now.
All colours are and should be under the full control of the user, as it always has been so. So called “accent colours” removed critical functionality from Windows as well as breaking the UI since windows 8.
As a software tester of 10 years and a CS Degree holder, I certainly would have never passed software that didn’t meet these usability tests.
I’m colourblind. I must have full and unhindered colour modification options, the GUI will look the way I decide based on what I want and how my eyes perceive it. This especially means I must have full control over titlebar colours and any other colours that used to differ based on window focus.
At work in Win 10 I have chosen an “accent colour” which seems to me a massive limitation, having had used superior GUI’s since Win 3.1 where the user is able to chose and adjust anything from the colour of title bars when focused or unfocused to the font used on numerous UI elements and widgets.
The problem is simple. Windows 10 grants (I say that in a sarcastic way) the user have the option to chose a so called “accent colour”. This however fails to do two things. Firstly it forces the design choices of the development team onto every user, something that is clearly wrong for Linux as history shows it was a plus over windows. Secondly, the accent colour fails to address several UI modal changes, completely obliterating them yet the modal elements remain part of the UI!!!
How in windows 10 can I tell if a window has focus or not? In Win 3.1 to 7 and anything running on Linux it was easy: the title bar colour was different. But since Win 8 that was dropped, windows still have focus and modal dialogs but you, the user, can not determine which has what and when.
Now, like I said I’m colour blind which means maybe there is a difference but I can’t see it. So what do I do? Well I randomly start typing commands into the wrong powershell window, or I want to control the browser using the keyboard only to discover that Outlook has focus and has started doing things in response to me banging keys. I have two monitors at work and focus moves between them and windows gives me no indication what has focus at all. Nothing I can see, out of the corner of my eye that is.
Thing is there is just one difference, the focused window might have a bold titlebar text or not. Note I bolded that. But I can’t see this difference without pixel peeping.
Every day I have to put up with this in the windows world and it annoys the hell out of me because the essential functionality was always there and has been removed because someone tossed a coin*. Maybe GNOME won’t fall into the trap of preventing full customisation of the UI, I hope so, user accessibility needs require it. I moved away from GNOME when they moved away from the desktop metaphor as I thought the alternative was terrible, and it still is, so this won’t affect me but it will affect loads of new colourblind users from the start.
The user has the last say and should be able to override anything.
HCI (Human Computer Interaction) rules exist for a good reason, stop chucking them away and make them options if needed.
And finally, take it from an actual colourblind computer users and electronics geek. Colour blindness accessibility filters DO NOT WORK. They simply don’t because everyone has a different kind/degree/combination of colour blindness. Normal visioned people are easy to demonstrate to as all we have to do is apply such a filter in reverse and they are like “Whoa what the hell” yet they fail to see (pun intended) that it’s a simulation that barely represents our individual colour ranges. Windows 10 has a colourblind mode, does nothing. Android has one, which has me try and sort colours to determine my specific adjustments, works better but still barely is used by myself.
The only fix is to give the user full control over all colours because then they, they can adjust the UI for the way they see the universe.
Here is an example from the linked blog. See this GUI. Which window has focus? The one on top? Well if GNOME prevents windows from always remaining above others regardless of focus, yes that would be the case. But if GNOME does allow focus to windows beneath others, well, which has focus? I cant tell.
I had intended on uploading images but that seems to not be working with this post/lemmy instance at the moment. Basically if you look at the blog there are examples. First of all the “pink” example, well that shades of grey to my eyes as pink rarely is a colour I can notice, most pinks are grey. Further down are examples of a stop clock application. Looking at the image I see most of the clocks digits are disabled, thats what grey means, disabled elements. However it turns out that they may be pink? Only the seconds are enabled, this is highly confusing as why would anyone be allowed to think a clock has digits disabled? It makes no sense and has me figure out the answer, which is bad UI design from the start. All the digits should be the same colour. It’s basic HCI rules there.
Further down you see the screenshots of the entire desktop with a window above another. In none of those examples can I tell which has focus. I can not assume its the one on top, plenty of UI’s have “keep on top” functionality, if I’m coming from something else why would I assume GNOME to be different?
Accent colours are bad. They force users to use static themes and UI choices made by other people, that is bad UI design, really bad. Windows 10 is lambasted for it often. If you are going to do it, do it right. The “accent” feature should be part of a simple customisation mode, but it all gets overridden by the advanced tickbox.
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.