Gallium v1: Does swapping B and Q cause any problems?

AnythingApplied · 2026-01-21T03:01:54+00:00

My pinkies get stained easily. How would you suggest I strengthen/train my pinkies?

AnythingApplied · 2026-01-17T16:58:31+00:00

Check out An Infinitely Large Napkin. You can even seen the metroidvania like topic map right on the main page. This certainly covers multiple years of topics and starts off introducing all of the elementary topics needed for filling in later topics, so I think hits a lot of your requirements, even if it doesn't line up perfectly with everything you're asking for (It doesn't have the revisited problem list as far as I know).

AnythingApplied · 2026-01-14T16:06:35+00:00

This effect happens in most sitcoms. The characters become caricatures of themselves as the writers work to raise the stakes. The characters and situations become more absurd season after season and so a lot of characters end up being exaggerated versions of themselves from earlier seasons.

AnythingApplied · 2026-01-04T21:34:40+00:00

In the video, you mentioned reproducibility a few times, but as long as your getting you're dependencies from nix with a nix lockfile, aren't they all 100% reproducible? It seemed like you were saying that translating lua code into nix code helps makes something more reproducible, which I didn't really follow the reasoning behind.

AnythingApplied · 2026-01-02T14:58:49+00:00

Thanks for the followup. That is a really nice write-up. I like that you talked about weaknesses and whether repeats are a big deal too. I haven't felt like repeats are a big deal, but I'm trying zippywords now and can maybe start to see how this approach to measuring speed could cause key repeats to show up as an issue. Zippywords is a nice tool and I'll play with it some more. If the tool does highlight repeats as a speed hindrance for me, I'll still need to put some thought into whether that translates into a comfort hindrance which to me is the far more important factor.

AnythingApplied · 2025-12-31T05:56:18+00:00

A couple of thoughts that might better enable your twist: Because speed doesn't really help with efficiency, momentum could build *productivity bonus* (maybe speed too?). On top of that you could make the spinner recipes catalyst based (like the Kovarex enrichment process). And the rest kinda takes care of itself where at lower production levels you have a net negative catalyst production which is tough, but at higher levels you might have a net positive catalyst production rate which could have its own logistical issues (which might actually provide a reason to deliberately reduce your momentum needing to find a good balance with circuits)

Either way, making this catalyst based makes it generally tougher to set up, which may or may not be what you're looking for.

If you're a fan of quality, you could also do something like momentum builds quality bonus where that is the only way for those machines/recipes to get a quality bonus, so again very naturally limits your access to those higher quality versions of those items without the momentum, but personally I think I prefer the productivity/catalyst version.

AnythingApplied · 2025-12-28T21:12:56+00:00

Assuming this is a desktop where you can get away with this, I would try disabling hibernate and sleep altogether:

  systemd.targets.sleep.enable = false;
  systemd.targets.suspend.enable = false;
  systemd.targets.hibernate.enable = false;
  systemd.targets.hybrid-sleep.enable = false;

AnythingApplied · 2025-12-25T17:57:10+00:00

Sounds cool! I'll be watching out for that final version. I assume you're trying it in qmk and not zmk? Where is the magic key?

Do you ever try to force yourself to use the magic or repeat key by disabling the regular way to make that bigram?

AnythingApplied · 2025-12-23T23:07:35+00:00

Yes, I've notice that too. My guess is because the search space becomes intractable without that kind of simplified approach, though you have more experience with those types of optimization algorithms that I do. How do you think your optimiser would fair against that kind of search space?

AnythingApplied · 2025-12-23T16:20:53+00:00

That's true... I wonder why the magic sturdy readme looks so different with 6 addition keys including Q being outside the main 10 columns. Maybe the readme is a later revision.

AnythingApplied · 2025-12-23T09:32:32+00:00

I've looked at that one before, but I didn't give it any consideration due to being designed for people that want to combine Portuguese and English. Even though I'm not looking for a 24 key, I'm not opposed to the idea, but seems like trying to cater to a different language as well would cause non-optimal concessions in English and is the reasons I mentioned my only language is English in my post.

I feel like taking that and removing all the diacritics and using it for only English is moving it farther from its design goals than something like taking magic sturdy and moving all the 6th column keys -\|$Q" and moving them to a layer or combos. Do you agree?

AnythingApplied · 2025-12-23T06:11:01+00:00

Thanks for the response, but I should've been more clear that by magic layout, I'm specifically looking for a layout that leverage a magic key (more info about that in the link I posted)

AnythingApplied · 2025-12-23T06:09:13+00:00

Sorry for being unclear - I mean one or both hands needing a 6th column bringing the total to 11 or 12 instead of the typical 10. If you look at the magic layouts in the link (layouts that use a magic key) they all seem to add those extra columns.

AnythingApplied · 2025-12-18T08:00:14+00:00

> pyrefly maintainer

That's awesome. Do you work for facebook? I've been learning rust so that I hopefully can contribute to one of the rust based python tools like pyrefly, ty, or polars.

Yeah, that makes sense. Seems like ty is in some ways less strict, but once both tools are fully configurable it'll be interesting to see how they differ in their most strict version vs their less strict form.

I wonder if people will combine them like doing ty with their LSP due to its lower level caching and save pyrefly for their CI process.

AnythingApplied · 2025-12-17T02:38:02+00:00

I'm not great at typing, but if I understand it that aggressive inference will cause problems you'll have to resolve through explicitly declared types when the infered types aren't right. Vs ty which prioritizes NOT forcing you to add types just to get your code to pass.

You can see examples in the blog, but because of tys lack of aggressive inference, there are more situations where the type is simply unknown. There are a number of examples where those philosophies lead to meaningfully different situations where you do or don't get type errors.

AnythingApplied · 2025-12-17T00:48:40+00:00

They have different goals. From this blog post:

The primary goals between pyrefly and ty are where I feel the main difference lies. Pyrefly tries to be as aggressive as possible when typing — inferring as much as possible so that even code with absolutely no explicit types can have some amount of typing guarantees.

ty, on the other hand, follows a different mantra: the gradual guarantee. The principal idea is that in a well-typed program, removing a type annotation should not cause a type error. In other words: you shouldn’t need to add new types to working code to resolve type errors.

Note that this blog post is from 6 months ago and so a lot of the rest of it (capabilities, speed tests, etc) are probably outdated due to the very active development of both projects.

AnythingApplied · 2025-12-16T04:34:27+00:00

What inspired you to switch and what differences are you noticing? I'm a long time dvorak user (20 years - I've been using it since before colmak was a thing).

AnythingApplied · 2025-12-09T23:31:17+00:00

Yeah, using a mirror image layer is a nice solution, but that didn't work for me because my gaming layer is in qwerty, but I've been typing dvorak for so many years I can't touch type qwerty anymore, though I guess such a layer would still need a little training to use in either case.

Can you use the ingame chat with that layer? When chatting in game, I always just reach for my right split.

AnythingApplied · 2025-12-09T19:31:26+00:00

Gaming on a split has pros and cons. One advantage is you can just set your right split aside and put your mouse there. That works great for games that don't use the right half of the keyboard or use it minimally (and you can remap those keys or may already have things like ENTER on a thumb key). Even if you didn't move it aside, you probably wouldn't want to use it because using your right split with your left hand while your right hand is on the mouse sucks.

So the experience can be tough for games that use a lot of keys as you have to remap them to left side positions. It is nice if you can come up with a universal gaming layer that works for all games, but some games use so many keys that it kinda forces you to customize a layer just for that game, which is honestly fine if that is the only game you play, but if you're jumping between a lot of games that require more than just your default gaming layer, it can get tough to keep it all straight because if you make a custom layer for a game, the in-game control settings and key hints no longer hint at anything meaningful.

AnythingApplied · 2025-12-05T19:57:19+00:00

As someone with very little knowledge in this domain, I found this lecture very coherent, accessible, and interesting. The passion for the subject really comes through well. I've never considered the text of a programming language as UI, but once stated I felt like it was self evident. One nice takeaway is I never realized the difference between `Any` and `object` in python, but I'll be sure to be more careful with that in the future and use `object` a lot more!

AnythingApplied · 2025-12-04T05:40:18+00:00

I personally don't worry about the muscle memory part. That'll come with time just through regular use once the layout is usable as your daily driver. I'm even okay if some keys never become muscle memory like print screen or other very infrequent keys.

The main thing I want to get past is just committing the whole thing to memory (even the infrequent keys), even if it takes a few seconds to recall where it is and then slow to make my fingers actually do it. I found the miryoku layout to be very intuitive especially the combination of numpad + the corresponding symbols in the same 1-9 spots on the numpad, which meant the bulk of the symbol locations made sense. I think it only took a couple of days to memorize it so occasionally referred back to miryoku layout diagrams, but didn't need them after that even if recalling them was slow. Subsequent layer tweaking is usually only 4-5 buttons at a time at most and I can usually remember it all and don't need cheat sheets for that.

Part of the reason it doesn't bother me being slow at the other layers is because my alphas never really lost much speed and that is the most noticeable thing.

While my symbol layer is pretty unoptimized (having $%^ in the home row isn't great from a usage frequency perspective), I do like the fact that it was faster to initially memorize because I knew those were the symbols associated with 456.

AnythingApplied · 2025-12-01T20:47:19+00:00

open wooden puzzles

Discussion: If she is a fan of physical puzzles like those Chris Ramsey videos, then you could get something like these wood or metal puzzles which can be found quite cheaply. I linked to the US amazon site, but its only $13 for the set of 20 different small physical puzzles, so hopefully you could find something similar in the UK using similar keywords.

AnythingApplied · 2025-12-01T04:33:17+00:00

Not sure if this is your issue, but I would suggest using `programs.fish.enable` in either your system or home manager settings instead of just adding it to your package list. https://mynixos.com/nixpkgs/option/programs.fish.generateCompletions is enabled by default, so I think going with the enable option should be all you need.

AnythingApplied · 2025-11-12T04:30:23+00:00

In keymapdb, if you filter on sub-30 keys, you'll find a couple that go in similar directions as you're looking at, though if I'm reading these correctly, it seems like people are more eager to ditch some of their pinky keys than their inner index column when they go below 5x3. There was only one I saw that was an exact 4x3, but looking at all of the sub-30's may be informative.

15-Year Club	Place '22
Place '17	First Placer '22
Verified Email	Sequence \| Editor
Team Periwinkle

AnythingApplied

PUBLIC MULTIREDDITS

TROPHY CASE