drakmaniso

4 ms·

1.
by drakmaniso 2y ago
I think the solution to that is to have only a few builtin effects. This is the approach taken by the Verse language: https://dev.epicgames.com/documentation/en-us/uefn/specifier... It's a compromise bet
2.
by drakmaniso 3y ago
That would only work if the new versions were willing to break backward compatibility. The safety (and correctness) of a language is not about what it can do, but what it cannot.
3.
by drakmaniso 3y ago
Is there a public specification somewhere? The only thing I could find is the code in the "material-color-utilities" on github. Looking at the code, it seems the computations are much more involved than OkLab, especially in the HC
4.
by drakmaniso 4y ago
I don't think passing state through functions calls add cognitive load: it just make it visible. Global state has the same cognitive load, except hidden. If a state is passed through dozens of function calls, this may indicate that i
5.
by drakmaniso 5y ago
It's more complicated than that. The study referenced in the book found that snake_case makes variables easier to read, but the whole program harder to parse (my guess is it's because of the visual similarity between the undersc
6.
by drakmaniso 6y ago
In order to know "what changed", you need at the very minimum to maintain a meta-state about your application state. In most retained-mode GUIs, this meta-state is often a copy of a significant portion of your application state, b
7.
by drakmaniso 6y ago
I believe the way it's usually done is to always parse a tuple, then parse the arrow as a binary operator applied to the two surrounding expressions. This potentially produce a syntactically incorrect AST (e.g. if there is an arrow fol