As a dev I’ve been on both sides to be honest. Especially when there is pressure to finish the next task. I think it needs good planning to create enough time for these things.
In the end bad devs will still shut you up about things they are not interested in fixing…
Nice! I started using helix before vim and often I find the helix bindings more logical (like shift for the reverse action e.g. u for undo and U for redo). However often the vim bindings feel quicker (c-i-w vs m-i-w-c). Will definitely give it a go!
Thanks, my works’ codebase feels old now.
I also cannot name him from the top of my head…interesting
sub-40 gang 👊
They don’t call me AbstractJokerAdapterFactoryProxy for nothin’
And the problem is about executing programs in windows. This is not about memory-safety.
A bunch of other languages are affected as well as noted by @colonial@lemmy.world.
Unfortunately as you found out QMK is not officially supported. But there is a port called SonixQMK which supports this board. This firmware also supports OpenRGB, so you can integrate the light even better in your setup.
I didn’t know gleam.io, but knew gleam. So it depends on your bubble I guess…
You mean like Tauri?
False positives happen - especially in the beginning but firmwares like QMK and ZMK have all kinds of smart behaviors that can be adjusted to fit the users needs.
I have - no problem doing this with qwerty also. It put me on a journey to minimal keyboards. What motivated me was eliminating unnecessary keys and reducing hand movement . Needless to say I really like it.
And both are written in rust
Classic PoweShell experience. Try rm -rf - I wonder why they added the aliases in the first place. Only frustrating to type different arguments which are also more verbose. Tastes like the good ol’ embrace-extend-extinguish.
Yes it does, still used when installing from media like DVD
Still too many buttons for artsey!
Those are rookie numbers!
I think https://github.com/KMKfw/kmk_firmware might be what you are looking for: It exposes itself as flash drive in bootloader-mode and the files on there are just regular Python scripts. If you search for “KMK macro pad”, you’ll find a bunch of projects - most of them diy. If you want to start from scratch, Jan Lunge created an awesome tool for setup and keymap adjustments (video https://www.youtube.com/watch?v=RtYJYFMWjNM, repo https://github.com/JanLunge/pog) - with the idea being that after setup you do not need the tool anymore to adjust the keymap.