codemonk

@codemonk@programming.dev

• ⁨Comment⁩ on ⁨Let futures be futures⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  I would not call it a bash. Go’s approach naturally comes up in discussions on async Rust. Thus, it makes sense to at least briefly mentioning the trade-offs that approach has.

• ⁨Comment⁩ on ⁨Monaspace - Microsoft presents a new font family for code⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Yeah, I am always happy if a project not only mentions where it shines but also where it does not. But it is common practice not to do so. Same in academic publishing. Everybody is focused on selling oneself, it seems.

• ⁨Comment⁩ on ⁨Monaspace - Microsoft presents a new font family for code⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Maybe ‘failing’ is too strong. What I mean is that in situations like the one I showed, texture healing cannot solve the problem of uneven texture. Not that they claimed it does. It just eases the problem. I like to know the trade-offs. When does it provide an improvement and when not? What tensions does that create?

  From a users point of view, I do not know if it ‘fails’ or not. I totally agree with you. Maybe the I would find to distinct ‘m’ glyphs annoying, maybe not. And example emphasizes the ‘problem’. Maybe, I woukd even notice while coding or writing. To know that, I need to try. I just like to know the trade-offs in advance.

• ⁨Comment⁩ on ⁨Monaspace - Microsoft presents a new font family for code⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Interesting. Thanks for sharing. I started with WYSIWYG and did not like editing with proportional fonts. Things do not align, the cursor jumps around and movements have variable distances. But I much prefer looking at beautifully typesetted proportional font (e.g. with LaTeX). While I think, monospaced font are nice for editing, they are okayish to look at.

  Thanks for the link. I will look into it and maybe try proportional for coding once more. Another idea I really like are almost proportional fonts. Read about these fonts a few month ago. So far I haven’t tried them.

• ⁨Comment⁩ on ⁨Monaspace - Microsoft presents a new font family for code⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Technically, font healing is a neat idea. It fails for text that does not meat its requirements, i.e. two ‘m’ next to each other. Depending on the characters around them, this might create two different ‘m’.

  Image

  This is unavoidable, of course. The only solution are proportional fonts. So font healing is a nice idea. It creates a more consistent spacing at the price of less consistent glyphs. Whether one likes this compromise, is a matter of taste. I personally lean towards consistent glyphs, but I did not try it for an extended period.

• ⁨Comment⁩ on ⁨How do you manage your dotfiles?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I prefer to keep tooling for that at a minimum. Therefore I use git only. My approach is taken from here: www.atlassian.com/git/tutorials/dotfiles The only difference: My git alias is dotfiles not config. I find that to be less confusing. Additionally, I source system-specific configs, where appropriate. These are not stored in dotfiles. There is a small todo section in my readme.