This doesn’t seem programming-related. Am I missing something?

When I was researching keyboards recently, I stumbled over a pro gamer (I believe) YouTuber who was quite vocal about pretty much all gear marketed as “gaming gear” is overpriced marketing bullshit. Apparently, they tested dozens of keyboards, mice, and headsets over the years. It certainly matched my impression of reading tests about products previously.

“Gamer” chairs are racecar chairs meant to keep you from sliding sideways, not being fit for long sitting sessions on a PC. Prefer a good or decent office chair. “Gamer” headsets are worse and more expensive than other headsets. Keyboards and mice are mostly marketing. etc.

Regarding input, they made a point about physical human limitations and state like sleep and caffeine intake having much more of an effect than the hardware you use.

2022 update

So this article is quite old. There are keyboard switches now that activate as soon as you activate the key, and that can recognize lift and press without passing a trigger point. If you want that kind of edge, those are the top performers right now. I’d be more interested in the technology and maybe playful capabilities than the performance they add.

I’m always way too thorough when researching products before buying…

I thought I remembered a standardized metadata file format you can place on your website, but I can’t find it.

GitHub defines FUNDING

Brave webbrowser attempted something like that with Brave Rewards, but through ads, and basically collected for themselves until the websites actually signed up for Brave Rewards.

I remember Flattr.

Claims that it can, but no evidence or anecdotal examples of how it worked in practice.

“Yeah, I can do that task. I’m very experienced in struggling to implement stuff like that.”

Is it available in the free tier?

I don’t think they mention maintenance burden specifically. Using a framework with packages means you have to track upgrades, do upgrades, check release notes, breaking changes, support and end of life cycles, license changes, etc. It’s a have maintenance burden if you keep it live, even if you don’t intend to make any changes.

Vanilla doesn’t have this problem. Server-side has it too, but in a slightly different flavor.

The heavier and integrated the framework, and the more additional packages you include, the heavier the burden.

Why does nothing link to the content/MS page in question? Not this article, nor the Bluesky post or replies.

I would have liked to see and verify the context, and explore the git history which should lead to some context that may give some context to what the author asks at the end: How did it come to be, with what ideas or goals, or justification, etc.

The Bluesky replies mention(/claim) that the image has been replaced, now seemingly copying a graph from Atlassian docs.

I totally get that. Technical and implementation exploration doesn’t necessarily correlate with publishability. :)

It is impossible for me to remember all my passwords. Maybe I have more accounts than other people. I remember the most important ones, amongst them a very long password manager DB password that is annoying to enter, especially on mobile.

First time I set up keepass I forgot the password. I still have the DB file without access. But the second time, I was more serious and committed to it, and made sure to remember and use the password. 😅

I find itch.io to be a great resource not just for games as a “finished product” but for prototypes as well. The regular gamejams contribute to this - a platform of many prototypes. They don’t need the polish and coherence you’d want to invest and publish on Steam.

Have you considered publishing your prototypes?

Even as only a player, some prototypes make for very interesting playful exploration, even if it’s short. For a technological, creative, and inspiration they can be a treasure trove as well.

Thanks for the suggestion. As a first step, I set it up in Nushell with a ctrl+t shortcut:

$env.config.keybindings = (
    $env.config.keybindings | append {
        name: fzf_file_picker
        modifier: control
        keycode: char_t
        mode: [emacs, vi_insert, vi_normal]
        event: {
            send: ExecuteHostCommand
            cmd: "commandline edit --insert (fzf | str trim)"
        }
    }
)

Maybe I will look into more. :) I’ve known about fzf but I guess never gotten around to fully evaluating and integrating it.

Nushell supports fuzzy completions, globbing, and “menus” (TUI) natively. Still, the TUI aspect and possibly other forms of integrations seem like they could be worthwhile or useful as extensions.

To what end? What would you expect version numbers to do? How would you specify or use them, which what consequences?

Grouping changes into releases with explicit numbering instead of a living standard with generic @supports checks?

I guess it would make some things easier and more obvious.

Please make them incompatible so that I have to upgrade.

For software to be perfect, can not be improved no matter what, you’d have to define a very specific and narrow scope and evaluate against that.

Environments change, text and data encoding and content changes, forms and protocol of input and output changes, opportunities and wishes to integrate or extend change.

pwd seems simple enough. cd I would already say no, with opportunities to remember folders, support globbing, fuzzy matching, history, virtual filesystems. Many of those depend on the environment you’re in. Typically, shells handle globbing. There’s alternative cd tools that do fuzzy matching and history, and virtual filesystems are usually abstracted away. But things change. And I would certainly like an interactive and fuzzy cd.

Now, if you define it’s scope, you can say: “All that other stuff is out of scope. It’s perfect within it’s defined target scope.” But I don’t know if that’s what you’re looking for? It certainly doesn’t mean it can’t be improved no matter what.

The original one? Because there’s numerous extensions to it. I wouldn’t be confident it won’t evolve further.

Do you exclude inventory management from that “will never change” so that that’s only about software?

I imagine there will be new products to be listed.

…that supports Unicode? Which encodings? Or only ASCII? Unicode continues to change.

I wouldn’t be very confident that it won’t change or offer reasonable opportunities for improvement.

Your sentence abruptly ends in a backtick - did you mean to include something more? Maybe “wc”?

!gamedev@programming.dev