codemonk

Unfortunately this is not the case. A lot of people leave school assuming that scientific discoveries are eternal, unfailable truth that we just know to be true. Few ever understand how we acquired our knowledge and how to lewrn to understand it. Many assume you ‘just have to learn it’. Those your play around with computers or other stuff have an advantage. They know how to gain understanding not just how to learn facts.

Yes please. Passively cooled Framework with a much longer runtime on battery => awesome.

Such a great project. Bringing joy to a friend and reduce e-waste at the same time. Love it. Would give away the SSD from my old Core 2 Duo based laptop (which got replaced by a used Gen4 i7 laptop from my company when they sold the devices to employees for very little money. Now they are giving them to schools for free, which is great). Sending it around half the planet is neither free nor sustainable, though. Would be cheaper to buy a new one. But maybe you find someone to help out. For me, an SSD was a great improvement for that old machine. As stated in another comment, upgrading RAM did not work in that particular case.

Fun fact: The machine might even have more RAM. I also had an laptop with a Core 2 Duo. The mainboard supported up to 4GB of RAM. However, the BIOS only supported 3GB (for whatever reason). Around 200MB are used for the iGPU. That left me with 2.8GB of RAM out of 4GB.

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.

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.

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.

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.

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’.

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.

I prefer to keep tooling for that at a minimum. Therefore I use git only. My approach is taken from here: https://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.