It's especially true when you want to parse some json/xml/whatever. Just describe your datastuctures with regular struct and enum, add serde and done! It's like magic!
robinm
joined 2 years ago
Would encoding images in oklch before compressing them using jppeg or whatever is used for video compression helps to have much better dark while still keeping current compression ratio?
I highly agree with point 5. Having good datastructure is so important and helps so much.
This new OKLCH color space looks really nice to use. It's surprising that it's really human readable, I wouldn't have guessed that you could do it for random colors.
I'm a bit surprised. Why does OKLAB gradiant looks better than OKLCH?
I can totally understand the iterating speed due to higher cognitive load of a statically typed language, and non instant compilation.
However I am very surprised about your refactoring experience. For me Rust is at least in a league of its own. In python/js I am terrified that I could break some unknown parts of my code whenever I touch anything. In C++ I fear that I just broke an invariants and made something UB. In all those languages, I expect regressions when I'm refactoring. But in Rust, even for large scale architecture changes if it compiles I'm quite certain that it's going to be easy to validate and often works the first try. What point points do you enconter that make your experience sub-optimal ?
I need to re-try it. I really like like lsp/dsp are first class cityzen, including the keybindings, and that there is better text objects than in vanilla neovim. Last time I tried it there was a few things that where not that easy to set-up (I forget what), but I should definitively take the time to learn it.
I just wish that neovim/kakoune/helix had a marketplace just like vscode. It make the discovery and installation so much easier when everyone use the same tools.
I didn't know about CACHEDIR.TAG, that's good to know. And yes, Rust tooling is stellar.
Nice! I'm waiting for #362 to be implemented before migrating away from messagEase, but it's really cool to see that this project is very alive!
I definitively love llogic comments when he(she?) has no submitions for the quote of the week!
That was a fantastic read. I'm both impressed by the stellar performance of C, and the stellar safety of Rust while keeping nealy best in class performances.
I do understant why old unicode versions re-used “i” and “I” for turkish lowercase dotted i and turkish uppercase dotless I, but I don't understand why more recent version have not introduce two new characters that looks exactly the same but who don't require locale-dependant knowlege to do something as basic as “to lowercase”.
step 1: learn to comment everything. This will helps code reviewer to catch errors because your code doesn’t match the comments
step 2: write your code in a way that makes comments useless and stop writting them
step 3: write your code just like you did in step 2, but documents all the things that you didn’t do, or why the code is more complicated than the naive approach. If your arguments are weak you are not in step 3, but in step 1.