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?
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?
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 ?
IIRC the orbit of Mercure doesn’t work with Newton Model, and astronomers were predicted the discovery of Vulcain a small planet between Mercure and the Sun. So a new model had to be invented since Vulcain couldn’t be found.
vim can have IDE-like capabilities thanks to lsp and tree-sitter. That’s a real game changer and is quite easy to set-up with something like kickstart.nvim.