codemonk

joined 1 year ago
 

Does anyone have a Feker Alice 80 and modded it? I am asking, because from the pictures it looks like the tenting angle decreases from the middle to the outside of the keeb. Technically, it seems to be a split keeb with two PCB. Judging from the few views on the PCBs I found, these are straight. Anything else would surprised me. Many custom made keebs with strong curvature have small PCBs per key. Even a Microsoft ergonomic keyboard I could look inside, has multiple small PCBs. Still the Feker looks curved to me. So my question is: Is it curved and if yes, how did they do it?

[–] [email protected] 3 points 2 months ago

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.

[–] [email protected] 23 points 3 months ago (3 children)

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

[–] [email protected] 1 points 3 months ago

That is my impression as well.

Just for completeness: According to GNOME Human Interface Guidelines app icons are full-color icons: https://developer.gnome.org/hig/guidelines/ui-icons.html My app should be fine! 😊

[–] [email protected] 2 points 3 months ago (2 children)

Haven't seen it indeed. Afaik, app icons should be fine. In case they are not, I have an idea, what the issue might be. Thank you.

Reading through the bug tracker, the GNOME approach seems to be one I see way to often: "The standard is outdated in our view and does not suit us. Let's just treat it as obsolete and make our own incompatible thing. If this breaks stuff, its not our problem." I prefer those that say: "We need an updated standard." But they seem to be the minority, at least these days.

[–] [email protected] 7 points 3 months ago (4 children)

Still working on my app launcher. Currently working on on user config. Recently I added support for app icons and there freedesktop.org icon themes. Icon themes are more complicated than I expected. Themes can have multiple fallbacks themes which themselves can have multiple fallback themes. Totally makes sense. I just did not think about it too much before implementing it. Allowed me to implement a nice breadth-first search. Most themes have a single fallback theme, so it is not of much use, but hey, I follow the spec. 😅

[–] [email protected] 2 points 4 months ago (1 children)

"Asynchronous programming in Rust" is really good, imho. My colleagues and I read it to get a deeper understanding of async Rust. I was skeptical at first, because it is from Packt, but it turned out to be a decent book. Also enjoyed the recent rustacean station episode with its author.

[–] [email protected] 1 points 5 months ago* (last edited 5 months ago)

Thank you so much! For years I was carrying around the thought: Why do we have to decide between eager and lazy evaluation? Your explanations are so clear and motivate me to finally dig deeper into that topic. So approachable. Thanks!

[–] [email protected] 3 points 5 months ago

At work and for hobby projects. At work I am looking at using Rust for safety-critical systems. As a hobby I am building a dmenu alternative. It is a fun project and I have a menu that satisfied my wishlist.

[–] [email protected] 11 points 6 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.

[–] [email protected] 1 points 9 months 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.

[–] [email protected] 1 points 9 months ago (2 children)

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.

[–] [email protected] 2 points 9 months ago (1 children)

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.

view more: next ›