The cost of opinion – Dimitri Glazkov
It appears that I’ve been writing this essay since 2012, never quite finding the right framing. One of my brilliant colleagues asked me this question back then: “How do you evaluate whether a Javas…
It appears that I’ve been writing this essay since 2012, never quite finding the right framing. One of my brilliant colleagues asked me this question back then: “How do you evaluate whether a Javascript framework is good for the Web? You seem to do it intuitively, but I don’t get it. What’s the logic?” And I was stumped . Now, a decade later, here is my best-effort attempt to capture that intuition. I am a bit older now, so I offer this with a bit more humility. The story is also a bit more technical in nature and I apologize to my non-technical readers in advance. I tried to formulate my answ
Explore this link on the map →related reading
- The new wave of Javascript web frameworksfrontendmastery.com
- The Market for Lemons - Infrequently Notedinfrequently.org
- Choose Boring Technologyboringtechnology.club
- Cognitive load is what mattersminds.md
- The Great Gaslighting of the JavaScript Era | The Spicy Webspicyweb.dev
- The cost of convenience — surma.devsurma.dev
- The "Developer Experience" Bait-and-Switch - Infrequently Notedinfrequently.org
- Pace Yourself - Not Boring by Packy McCormicknotboring.co
- pketh.orgpketh.org
- Karri Saarinen on X: "Every feature should earn its place" / Xx.com
- What is "good taste" in software engineering?seangoedecke.com
- Things you forgot (or never knew) because of React - Josh Collinsworth blogjoshcollinsworth.com