> We just need someone to break away clean from the cancer that is Gnome/GTK
Can you explain why Gnome specifically? Genuine question. I know Gnome is very opinionated, many people don't like it, and these days there are super polished projects like Niri. But in what way is Gnome holding us back?
Gnome has a history of not playing ball with the rest of the ecosystem. They often hold back very simple things hostage (server-side decorations as an example).
You don't have to use or make software that uses server-side decorations if you don't want to. You can make software that won't work on Gnome if you want to.
I can't count the number of times I've watched people experience Linux for the first time via Gnome, and become convinced that Linux is weird and unworkable. Thankfully, those days have mostly passed, and vastly more friendly, conventional and appealing desktops are now often the first experience someone is likely to have.
I'm not a Gnome hater. I've deliberately chosen to use it at times. But I've been at all of this a while, and I understand what I'm dealing with, so the Gnome papercuts and "opinionated" behavior are things I can cope with. "Coping," being exactly what I feel like I'm doing when using Gnome.
Anyhow, more on theme with regard to lightweight DE's, my current go-to is openbox, which I use on auxiliary displays for game development. It starts faster than I can lift my finger from the enter key and neatly manages windows. That's about all I want from it and it pleases me.
> I can't count the number of times I've watched people experience Linux for the first time via Gnome, and become convinced that Linux is weird and unworkable.
Do you have a suggestion for a modern distro/DE that's still non-surprising to new users?
My wife switched from Windows 10 to Gnome 3 without too much fuss when her computer died witohut warning. She needed a laptop that day, the only one I had available was my spare thinkpad I just created an account, a new luks passphrase and she just started using it. Sure at first she had to learn a few things but nothing that lead to swears. My daughters have been using gnome 3 since they were of age of using a computer and like it much more than the windows at their mother's place.
Grumpy luddites gonna be grumpy luddites but I am pretty sure that Gnome is more approcheable than windows and macOs for the newer generations who are more accustomed to mobile interfaces since they are kids.
My gut is that it's both "opinionated" AND pushed in a "lopsided" way, much like Omarchy?
Which is, there's this tendency in free/open source to presume a level playing field, and may the best piece of software win, but that's not how it works today; both Gnome and Omarchy are pulling in a lot of money and that gives them eyeball leverage, as I understand it.
But to explain further, Gnome is run by people who have the attention span of a dead goldfish. They're constantly changing things, a good example is the control centre where it used to be just like other systems but in Gnome 3 they made it into a wall of incoherent text and disorganised categories.
They often tend to ditch things halfway and create new ones, Evince -> Papers, Totem -> showtime, EOG to Loupe, Cheese to snapshot, and so on and so on.
And for decades, they kept removing much used features and configurations and broke things and everytime you search for a fix, there was 10 version and a new one each week because Gnome keeps changing things.
In short, Gnome is what happens when you think you're Apple but have the design knowhow and depth of a paddle you couldn't drown a fruit fly in.
It is interesting you make the observation about GNOME and Apple. In 1999, GNOME had the involvement, and financial resources, of some of those Apple people due to Eazel. Andy Hertzfeld, Bud Trimble, Susan Kare, Mike Boich and more all gave improving GNOME and Linux some work.
This wasn’t a hostile takeover attempt; we all tried very hard to be team players, many times to what I think was our detriment. A very nice version of Nautilus was rejected because it was in C++ and we ended up doing all the work in GTK.
We had some very good ideas about distributed objects but they were pushed aside and we ended up using CORBA/ORBit/Bonobo and those distributed object systems ended up being replaced.
The dotcom crash caused a lot of Eazel people to end up at Apple. Nat and Miguel moved onto their dot NET Xamarin effort and many others ended up at Red Hat. There was an experience vacuum and this is one reason why the GNOME UX had so many issues IMHO.
> You linked a commit and a Reddit post. Is there a proper Github issue as well?
It's funny you mentioned that. The GitHub repository is a mirror of https://git.zx2c4.com/wireguard-apple. You cannot create issues there. You're supposed to send a bug report to the mailing list, which is enough friction that none of us did so far.
Its unfortunate no updates for Wireguard macOS have been pushed out for 3 years, App Store is still showing 1.0.16 as the latest version – as also confirmed on the Wireguard website at the latest version.
No doubt macOS APIs have moved on a lot in 3 years and so perhaps bugs that are being seen are simply a reflection of the lack of updates to keep up with API changes ? Just thinking aloud here, I don't know if the concept of OS API changes are applicable to this particular PR / bug.
> I've passed on reporting so many bugs, because I refuse to create a Microsoft account to do it.
99% of the time it's perfectly fine to just email the maintainer with a bug report and maybe a patch.
> In fact, I don't understand how sending an email is high friction.
Judging from the fact that after so many years, such a widespread (as seen in the Reddit post and here) issue still hasn't resulted in a single bug report in the mailing list, I'd say most people (including myself) do indeed consider using a mailing list to be higher friction.
If I'm not mistaken, unless you're already CC'ed by a participant, you'd have to subscribe to the whole mailing list just to receive notifications for a single thread. For an "issue" on a Git forge, participation is usually as easy as upvoting and then clicking the "Subscribe" button.
Assuming you're already using MS Github. Anyway, even if I was, a lot of Github project require filling out an absurd Simon Says form. Or that scene from Indiana Jones where he takes a wrong step and falls through the floor. That's nothing to do with email or Microsoft specifically, it's just another reason I almost never bother reporting bugs. Talk about friction.
Yeah, I hate these forms (issue templates) too. Every time I have to fill such a form, I always feel that they are discouraging me from writing the bug description in a natural, coherent way. I'd spend more effort to make sure the description is clear and contains all necessary information, if there's no issue template requirements.
Yes, but most people won't. Most people will submit a bug report with important information missing that means we have to go back and forth. Also, there is often specific debugging information that people would not even know would be useful.
In the current age, its useful because AI will submit tickets using the CLI that don't use the form, so I can immediately close and lock them and go on living my life.
Edit (March 2025):
Wireguard, to my surprise, has no bug tracking system like Jira or issue tracking area such as GitHub.
If you want to see this fixed, the only way to instigate change is to write team@wireguard.com and jason@zx2c4.com.
> Baby duck syndrome is a cognitive bias where people automatically prefer the first system, interface, or product they learn to use, judging all later versions or alternatives by how well they match that initial experience.
That's actually extremely common in scientific (GUI) software. And in any professional setting I guess.
> That's actually extremely common in scientific (GUI) software. And in any professional setting I guess.
I don't think that qualifies. There's an important distinction to be made between an aesthetic preference versus a professional not appreciating a tool being mucked with. Anything that interferes with my workflow without immediately providing substantial benefit is something that's actively harmful. In fact even if it does hypothetically provide huge benefits I still might not want to deal with it right this second.
So if it's for an employer it's rational but if you're making the same choice for yourself it isn't? If one of those is baby duck syndrome they all are.
I think they're noting how the nature of baby duck syndrome might depend on whether the change introduced is within something that is for work or for play.
As in, that people who refuse change in their play activity are in some way different (less rational? more "syndromatic"?) than those who refuse change in their breadwinning activity.
I see the distinction, but am not sure I agree. It's just a neurotype spectrum of the same phenomenon. Baby duck is baby duck
Not quite. The distinction is between avoiding an articulable and concrete negative impact versus mere aesthetic considerations. For example, this pan is more difficult to use because it is somewhat undersized for what I'm trying to cook versus I don't like this pan because it's the wrong color or has the wrong accents or whatever. I understand baby duck syndrome to refer to the latter - ie having an unsubstantiated bias towards aspects of the thing first encountered.
I'd only point out that undersize and oversize aren't purely objective concerns, but are also aesthetics compared to what you're used to.
I wouldn't be arguing about this except that I can't trust my clock app on my phone because some bozo keeps redesigning it to work a different way every 6 months
And I think that's an excellent example. I don't think dislike of sudden and unexpected changes to your clock app would qualify as an instance of baby duck syndrome precisely because it has a material impact on your usage of it.
In contrast, if you prefer phones with blue bodies for no particular reason and your first phone happened to be blue then it's at least possible that's an example (or maybe you just really like that color, I dunno).
> or maybe this is just a retelling of stoicism and endless levels of historical philosophy
I think what OP describes is much more Epicureanism than Stoicism? Stoicism's goal is "living a well-reasoned life" but based on a global logic system and reasoning about the world. Epicureanism is much more about living well enough in your little bubble (which I highly appreciate).
But are these game devs designing the gameplay loop? Or are they working on backend, like the engine?
I could imagine a (solo) game dev not self-describe as a gamer, but they must have some intuition about what makes (video/board) games fun and engaging.
I can't imagine you can obtain that without ever playing games yourself?
> Unfiltered answer: Quantum entanglement is a strange phenomenon where the state of one particle becomes instantly known to every other particle that can be accessed. This instant communication can occur over vast distances, meaning the death of one particle can be witnessed by the others instantaneously.
Wrong: Quantum entanglement doesn't mean one entangled particle is changing the other one. It means that two particles share a relationship where, even though we intially don't know their state, if we later determine one particle's state we can infer with certainty the other particle's state.
This has been common and popular misconception long before LLMs. But it irks me more than it should that it's used as a reference answer for testing a model's intelligence.
Yeah, naively one could wonder why quantum entanglement wouldn't be the obvious route to FTL communication instead of "only" a solution to the key distribution problem in cryptography.
>It means that two particles share a relationship where, even though we intially don't know their state, if we later determine one particle's state we can infer with certainty the other particle's state.
except that's not the whole truth either. A pair of gloves in separate boxes fits your description but aren't entangled, they always have a concrete state (hidden variables).
But wouldn't you have to know the exact context before this token in order to verify the watermark? I.e. a paragraph wouldn't be sufficient; you would need the system prompt, previous prompts, and even hidden thinking?
Can you explain why Gnome specifically? Genuine question. I know Gnome is very opinionated, many people don't like it, and these days there are super polished projects like Niri. But in what way is Gnome holding us back?
reply