I, uh, hate that radius calculation. Why does the radius need to be reactive? What do you stand to gain over just setting to like 3 or 4px and moving on with your life?
I'm not sure how this relates to the shared post. I'm just searched the article for "radius" and only found one example where a variable is defined then used later. Were you talking about this ? Or can you clarify what "radius calculation" you hate ?
My guess (hope!) is that this is not 'serious' code, but padding for the sake of a screenshot to demonstrate that it's possible to use each of these different features (not that you should!).
Good riddance, I say. Web dev is infested with layers upon layers of tools that attempt to abstract what is already fairly simple and straightforward to work with. We're beyond the days of needing to build buttons out of small image fragments, and JS is (slowly) becoming more livable in its raw form. I welcome anything that keeps the toolchain as simple as possible.
At my company I start all new projects without a framework. I try to write things in templated backend frameworks with no javascript on the frontend. If I need javascript, I try to use web components, styled with modular css in the shadow dom.
However, this sometimes requires an absurd amount of build tool configuration with webpack in order to get static asset and typescript loading working just perfectly. I end up kind of just writing my own framework instead
I could understand declaring with --foo, but then referencing should be either var(foo) or just --foo, not the combination var(--foo). I don't get why the grammar has to work that way.