A good common framework helps here. Then, it's up to each user to set their settings properly.

I would argue that any sufficiently powerful framework also provides more ways to diverge from the "proper way", so it puts more pressure on the developer to actually study and understand the framework design patterns.

If this grid a central component of the application and navigation inside it is very common, I would argue that there should be a way to quickly move around the cells. The "how" is up to the specific application and the paradigms it promotes. For example, line navigation in vim is possible with "G", but such a shortcut would seem absurd in another application.

For example a GTK app main context menu can be triggered with F10. But this relies on the developer to correctly "tag" said context menu.

In simple cases it is obvious what to do, but in more complicated designs, where you may be able to achieve the same visual output in different ways, it may not be so obvious.

In that case, it is up to the developer as well to read and try to follow the published guidelines.

The "intuitiveness" argument is also related. You cannot rebind well-known shortcuts to different actions and expect the user to not get frustrated.

[1]: https://github.com/philc/vimium/

This does not contradict the argument. The rest of the interface, everything that is known and stable in advance, should be full keyboard-driven.

The intuitive part of my argument also falls under this. By following known conventions as close as possible, we can eliminate the need to remember the most common actions.

Additionally, it is important to present your shortcuts in a shortcut window/dialog in a logical way for when the user needs to remember something.

In any case, an excesive number of keyboard shortcuts can have a negative effect on usability, so this is also important to keep in mind.

Comments URL: https://news.ycombinator.com/item?id=49479837

Points: 734

# Comments: 367

KCacheGrind is amazing, but I was looking for a GTK native alternative.

Recently, I took an interest in Clojure, so I decided to combine the two in one project.

The result of this is Klisi.

Try it out and let me know what you think.

You can read a small write-up about this first release on my blog[1].

[1]: https://ckardaris.com/blog/2026/08/15/klisi.html

Comments URL: https://news.ycombinator.com/item?id=49312354

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48555583

Points: 2

# Comments: 0

I can try to think of a simple scenario. For whatever reason, a user may not be as active in the new platform as they were on discord. This could alter the community dynamics. On a bigger scale this could have visible effects in the actual community.

To be clear, I am not advocating in favor of staying on discord. I just find the concept of community building interesting.

Migrants or refugees have to find a new community because their old one was broken for whatever reason, be it war, financial troubles or something else. So in that case, that first breakage of community should have been prevented and the community preserved.