I just say it's basically reddit but it's community built and run instead of owned by a big company. And then if they wanna know more about how it works, I can explain the concept of it being distributed and whatnot
I very much agree with just inviting people to join your instance. Don't overcomplicate it.
Very true, that's valuable feedback to provide. I should probably write a message as well, I'd only briefly noticed it yesterday as I was getting something done, so I didn't really process the change until someone else mentioned they had that frustration
Agreed, that's kind of an unnecessary pain point. Not the end of the world, but hopefully they continue to improve the UX and that unnecessary friction goes away :)
Though I'm not actually able to watch this one through the link, it tells me it's not available on that instance. It'd be kind nice if using share functionality shared the like for the source instance
On one hand, I absolutely support leaving Microsoft behind. On the other hand, I don't know that this form of action is likely to really be felt by Microsoft, and I think the FSFs sort of evangelical approach to sharing what's special and worthwhile about free software often just kinda feeds negative sentiments towards FOSS as a worthwhile cause.
One of my close friends was, for a long time, kinda hostile to the idea of anything open source because her experiences with open source folks always sucked.
I'm just kinda typing out the thoughts this prompted, this isn't necessarily a response specifically or exclusively to the article.
Ghostty is a terminal emulator that differentiates itself by being fast, feature-rich, and native. While there are many excellent terminal emulators available, they all force you to choose between speed, features, or native UIs. Ghostty provides all three.
It seemed like the Godot situation was kinda just people shouting at the clouds and being angry about "woke-ness" brought to a head by an unaffiliated disord mod being unpleasant. I'm kinda suprised that was enough to result in a fork
Yeah, I agree. Like there are a million things to improve on in terms of user facing features, polish, and user experience, it just feels like such an empty, forced addition.
Give me hdr, high refresh rate support, expanded user system configuration options on gnome, better option organization on kde, increased focus on well thought out user experience design, more graphical ways of doing common tasks users might find themselves wanting to do, or any number of small polish and integration improvements, etc. Hell, even linux phone improvements!
It just feels like a lot of work for something that really isn't actually really valuable. Especially in a space where we have to triage and prioritize because we don't have the same resources.
Are these like... Really things people want...? These seem either superfluous, or like they should just be standalone apps dedicated to this sort of functionality if people want them.
These are niche in their actual usefulness to a point of essentially being irrelevant. Of all the user experience polish, nice-to-have-features, and general system integration that this space needs, these kinda feel like proactive wastes of time...
I do think changes should be more carefully weighed than they sometimes are
I definitely don't think that's why. The biggest (but not only) reason we don't handle UI in this same way is that if changes happen the computer isn't capable of relearning how to do things in that moment, and people 100% are. We should provide affordances, communicate how things can still be accomplished effectively, and more carefully weigh the cost of making changes, AND ALSO people are capable of learning how to do a thing again when presented with changes
I'd also add, my perspective as a more-design-than-technical person is there's way more material benefit to making those changes with people than with APIs. If the api provides the needed functionality, a computer can access that functionality. But people aren't robots, they have to learn, rather than be taught to interact with the interface that we give them, and making it more organized, more visually clear, creating better affordances, etc, has much greater immediate benefit than I'd assume refactoring or updating an api in some way
(I also think there may be an interesting conversation to be had about whether UIs are better conceptualized as being akin to tools, or storefronts. Both are interactive, but some interfaces are obviously tools one masters (creative/productive software), and other interfaces are more like places we visit that we might reasonably expect to change sinage, reorganize, optimize how things work, etc (which would be true of many websites) or any mix of the two!)
Very much agree with this, I think people really overcomplicate it.
"It's like reddit, but community build and community run."
And they you can just invite them to your instance