ckardaris

9 ms·

1.
Selling Out(seangoedecke.com)
2 points by ckardaris 4d ago|0 comments
2.
Open source needs to be preserved, not protected(usebottles.com)
3 points by ckardaris 5d ago|1 comments
3.
by ckardaris 18d ago
For example, opting to not enable high-contrast mode is a question of aesthetics. Arguably reading text would become easier for the user, but they prefer to sacrifice a little of the readability in favor of looks.
4.
by ckardaris 18d ago
Sometimes users may prefer to reduce the degree of accessibility of an application in favor of aesthetics.
5.
by ckardaris 19d ago
> ..., so a user can configure F10 to open it if you, app developer, forgot to mark it as main So, basically what you want you want, as a user, is to bind arbitrary application actions to shortcuts and force click events in spite of what
6.
by ckardaris 19d ago
> But a framework can provide user keybinds conditional on that Dialog-As-Win being shown so users could reclaim some of that lost automation. The "conditional" is carrying a lot of weight here. The developer needs to know what
7.
by ckardaris 19d ago
But you can — or should be able to — independently toggle all of those features. For example, the app should work in high-contrast mode with disabled color coding, it should work with touch gestures disabled, etc. A good common framework he
8.
by ckardaris 19d ago
This is where using a common framework pays dividends. For example, on the desktop I can disable animations for all GTK applications.
9.
by ckardaris 19d ago
Maybe not complicated, but unorthodox. A developer who is not familiar with the correct design patterns may, for example, create a dialog using a FrameworkWindow instead of a FrameworkDialog. In that case the framework can not provide any a
10.
by ckardaris 19d ago
That's a good point. Accessibility is the next step that should also not be ignored. Navigating to the elements is one thing, but for the voice assistant to work properly it can be a little trickier.
11.
by ckardaris 19d ago
> What if you have a grid of 30 item, do you press 20 times tab to focus finally the item you want to interact with? If this grid a central component of the application and navigation inside it is very common, I would argue that there sh
12.
by ckardaris 19d ago
Any text-centric action will have a great advantage when done inside a terminal. I would think the equivalent in GUIs would be first-class OCR support on the compositor level. I am not informed about any progress made in that region to be h
13.
by ckardaris 19d ago
You are right. Maybe the wording is a little too absolute. If you gotta ship and later try to slowly address any shortcomings in different areas, this is also a step in the right direction in my opinion. Just don't completely forget ab
14.
by ckardaris 19d ago
In some cases they do. 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 des
15.
by ckardaris 19d ago
This can happen if the applications exposes single keys as shortcuts. If they are "hidden" behind the different modifiers (i.e. Ctrl, Cmd, Alt), then mis-clicks should not be possible or should be more tolerated. The "intuiti
16.
by ckardaris 19d ago
You can always take it to the next level by using an extension like vimium[1]. [1]: https://github.com/philc/vimium/
17.
by ckardaris 19d ago
I agree. I mention this briefly in one of the footnotes. There are some tasks that greatly benefit from the mouse (e.g photo editing tasks where arbitrary region point and click is required). This does not contradict the argument. The rest
18.
by ckardaris 19d ago
You don't really need to remember everything though. Mouse navigation does not need to go away. The keyboard shortcuts should be available if you opt to use them, after which point you will be able to memorize them in short time. The i
19.
by ckardaris 19d ago
Ideally you should have both. Every action should be doable by mouse only and by keyboard only. That way you can cater to all kinds of users.
20.
GUIs should be fully keyboard-driven(ckardaris.com)
1055 points by ckardaris 19d ago|528 comments
21.
Show HN: Klisi – a GTK4/Adwaita callgrind profile viewer and generator(gitlab.com)
1 points by ckardaris 1mo ago|0 comments
22.
Explaining Functional Programming to Non-Programmers (It's Just Excel)(cekrem.github.io)
2 points by ckardaris 3mo ago|0 comments
23.
by ckardaris 7mo ago
I am not on discord, so I don't have skin in the game. But it depends on the community I guess. If everyone stayed on discord then there would be no change. But any kind of change would probably have some kind of effect, even if all pe
24.
by ckardaris 7mo ago
This is a completely different topic though. And not relevant to point being discussed. Analyzing the effectiveness of community building by different groups is a separate issue.
25.
by ckardaris 7mo ago
I don't think the article proposes that a community should not accept new members. On the contrary, it critiques the breaking of communities. Migrants or refugees have to find a new community because their old one was broken for whatev
26.
by ckardaris 7mo ago
The author of the article claims that a mere migration to a new platform does not solve the problem. It just fragments the community. I agree with that. For one or another reason not all people will migrate.
27.
The P in PGP isn't for pain: encrypting emails in the browser(ckardaris.github.io)
2 points by ckardaris 7mo ago|0 comments
28.
by ckardaris 8mo ago
>1. Accept comments via email In case anyone is curious, I (very) recently implemented a similar comment system based on email. I posted a write-up about it[1]. [1]: https://ckardaris.github.io/blog/2026/01&#x2F
29.
My Comments Run on Email(ckardaris.github.io)
2 points by ckardaris 8mo ago|0 comments
30.
by ckardaris 8mo ago
I am very satisfied with KISS launcher[1]. I have been using it for a while now. It's simple and gets out of the way. [1] https://kisslauncher.com/

More ›