problem: low-resolution sourcemaps
interesting wording: "low-res" here
problem: low-resolution sourcemaps
interesting wording: "low-res" here
If you'd like to read more about the game's arguments, click here.
I'm not familiar with this term "arguments" used like this. Isn't this more referring to the motivation for this game?
We really don’t think laws and “imaginary property” have any place
<Masonry> component implementation could be something like this (very drafty)
This overloaded word is also non-jargon for a proper morphism.
notion
I don't feel very comfortable with this choice of wording, perhaps because the dictionary definition includes such wishy-washy definitions as "A belief or opinion." "An impulse or whim."
Why not choose a better word like "property"? Which is what they called it here, for example.
(Even "concept" or "idea", though just as vague, might be better than notion?)
Svelte makes the pit of success larger because it hides all of this from us at compile time.
Those frameworks are used in a similar fashion, but conceptually use quite different approaches (Vue is a more traditional one, a library, and Svelte is a "dissapearing framework").
interesting wording: Svelte is a "disappearing framework".
Investigate deeply.
The Doom Loop in the Financial Sector, and other black holes of risk
anti-fragile development
feel like there needs to be an easy way to style sub-components without their cooperation
runtime-frowning