IRC has a completely separate problem - it hasn't evolved to deal with the modern world. The online/offline model with persistent connection while online is a total anachronism. And you can't send a screenshot through it - even email can do that.
Those are fair critiques to be sure, but also precisely why my circles find utility in it.
Most of my IRC users hate the persistent records of modern chat systems and their persistent “always-online” functional designs. They want to be able to log off on their terms and not have a session follow them around, which IRC respects. For those who want rich rendering for media, they can choose a client that does that rather than have it forced upon them by default in Discord or Slack.
Same deal with sharing images: why shoehorn it into IRC when we have copyparty right there? It’s faster, easier, and entirely ephemeral - just like IRC is configured on the server side.
The point isn’t a “do everything” software or platform so much as a “do what we need so we can go live life doing what we want” setup.
IDK though - this is how Office ended up with its ribbon. They realised Paste was the most common action so they gave it a big button right at the left side, and then cut and copy got smaller buttons next to it. And similarly they reordered all the buttons according to frequency of action.
Result? When you have an intent in mind, it's hard to find the right button! In office 2003, you could click on the "insert" menu and every item there was something that would go into your document. If you're thinking "I want to add a picture" you can click on "insert" and scan through for picture-related items. (Blender does this too). In the 2007 ribbon model it would - well that one would probably be on the default visible ribbon because it's a frequent action - but what if you want to insert a table of contents? Who knows where that button is.
:-)) Yes, Microsoft Office is actually a perfect example for how not to do it and why:
What they do wrong is, how they partition the "state space" in the first place. They employ utterly absurd abstractions that fly in the face of rational usage. Then that "ribbon" nonsense observes the user stumbling though that mess and changes the arrangement on the fly, maximizing the confusion.
In other words, they have never conceptualized what it is their users actually want to do and why. Now they're "stuck" with "what users are habituated to" and each "optimization" makes things even more worse in other places.
To get a "fluid" interface right, you need to know that it makes sense only when there are distinct use cases. You then have to detect (or perhaps better: let the user decide) what use case you're in and shape the interface according to that. Making the user chase buttons certainly isn't the right way.
No, then I didn't make myself clear. That's what a "ribbon" does when it's chasing a confused user.
When you have a good tool, it has a clear purpose, a well-defined domain of applicability it is optimized for. Software tends to be "multi-tool"-like and that poses problems obviously.
When you let the user choose what his purpose is and adapt the interface accordingly, that's not "different every time you use it", it acts as expected for that present use case.
It's maybe like a workbench, where you have multiple tools available in their appropriate and known positions. Each tool has its place and native interface, optimized for the narrow job it does.
Office is like a workbench that gets rearranged randomly and each tool is weird with unclear purpose and scope.
Scrolling down to reach the HTML keyboard, and then back up to see what I typed, is obnoxious. I have a keyboard installed, and it doesn't pop up because something on the page tells my browser it doesn't need to. Was this vibecoded?
What is the resolution of your phone? It is supposed to adapt to any phone so that the keyboard and all the rows fit on the screen. You are the first person I’ve heard from with this issue since we fixed it for some weirder resolutions.
Glad you asked, as the answer is, in my opinion, interesting. Developing a game like this seems pretty simple until you have to make a UI that fits on a phone. If you look at the default keyboard on your phone, you will see the suggestion bar or something similar. When space is limited, that space is crucial, and that extra height is enough for a row in the game.
Another benefit of having our own keyboard is that we can remove language-specific characters that may not be handled well by the game's daily functions.
If someone causes financial loss by posting LLM text and is then found to have removed a watermark. Everything in civil law is implicitly inside a if(someone harmed && they sue you) {} block.
reply