Top all-time · #6112
Justin Fagnani
Personal blog · justinfagnani.comprogrammingweb
Justin Fagnani's personal blog at justinfagnani.com covers programming and web. Since 2015, 13 different Hacker News readers have linked it 18 times, most often ““Real” Mixins with JavaScript Classes”. No feed was found, so read it on the site itself.
Too few sampled comments (9) to say how often HN recommends it.?
Why HN links it
HN links Justin Fagnani's posts on JavaScript mixins, native DOM templating, and XSLT templating demand. Most comments cite them as references; two point readers to them as useful.
Summarised by Claude from a sample of 9 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Programming and things
Most-linked posts?
- “Real” Mixins with JavaScript Classes7 people · 9 mentions · first linked 2015-12-29
- What should a native DOM templating API look like?2 people · 3 mentions · first linked 2025-07-01
- The time is right for a DOM templating API2 people · 2 mentions · first linked 2025-06-26
What Hacker News says?
Of course, you'd need to use super appropriately, but I wonder if anyone's taken a stab at porting React mixins to ES2105 mixins: http://justinfagnani.com/2015/12/21/real-mixins-with-javascr...
Comment linking /2015/12/21/real-mixins-with-javascript-classes/
on “React v15.5.0”Submitted The time is right for a DOM templating API as a story · 218 points
HN discussionSerious question: would it be worth the effort to treat XSLT as a compilation target for a friendlier language, either extant or new? There's clearly value in XSLT's near-universal support as a web-native system. It provides templating out of the box without invoking JavaScript, and there's demand for that[1]. But it still lacks decent in-browser debugging which JS has in spades. [1] https://justinfagnani.com/2025/0…
Comment linking /2025/06/26/the-time-is-right-for-a-dom-templating-api/
on “XSLT – Native, zero-config build system for the Web”Submitted What should a native DOM templating API look like? as a story · 69 points
HN discussionCheck out this: http://justinfagnani.com/2015/12/21/real-mixins-with-javascr... Might provide you with some functionality you're looking for. Since TypeScript is an es6 superset, I'm assuming this will work in that context.
Comment linking /2015/12/21/real-mixins-with-javascript-classes/
on “Announcing TypeScript 2.0 Beta”Submitted “Real” Mixins with JavaScript Classes as a story · 6 points
HN discussionLit has always been designed partially as a prototype for where web component standards could go in the future. That's a big reason Lit is fairly conservative and un-opinionated. It doesn't try to undo or paper-over any of the DOM APIs, but add to them instead. There is a proposal in TC39 for native signals, which I think would make a huge dent towards library-less reactivity. I'm also working on a proposal for nati…
Comment linking /2025/06/30/what-should-a-dom-templating-api-look-like/
on “Lit: a library for building fast, lightweight web components”Submitted Real Mixins with JavaScript Classes as a story · 3 points
HN discussionI wrote a couple of blog posts on why we should add native templating to the DOM so we'd need fewer libraries. The time is right for a DOM templating API: https://justinfagnani.com/2025/06/26/the-time-is-right-for-a... What should a native DOM templating API look like?: https://justinfagnani.com/2025/06/30/what-should-a-dom-templ...
Comment linking /2025/06/30/what-should-a-dom-templating-api-look-like/
on “<template>: The Content Template element”Submitted Stop Using CustomEvent as a story · 1 points
HN discussionI feel like languages are playing around different paints if coat mostly, and not trying to build more meaningful programming experiences. I'd love to see a language whose pitch is that they have very next level stdlibs builtin. Effect for example is basically a mini stdlibs unto itself. It would be amazing to see such a principled deliberate craft applied to a language. Scope, layers etc etc etc etc: make visible,…
Comment linking /2026/09/09/zena-a-new-wasm-first-programming-language/
on “A few good ideas in programming languages”Submitted “Real” Mixins with JavaScript Classes as a story · 1 points
HN discussionRecently I've been advocating a move to distributing uncompiled ES6 packages, and shipping ES6 to browsers that support it and compiling using a single simple preset (ES2015 except modules). There are several big reasons: 1) ES5 "classes" cannot extend ES6 classes (it's not possible to emulate a super() call in ES5), so: 1a) All the extendable built-ins are basically ES6 classes. If you want to extend Array, Map, Se…
Comment linking /2015/12/21/real-mixins-with-javascript-classes/
on “Ask HN: If you targetting ES6 by default, how did you rationalize that choice?”Submitted Real Mixins with JavaScript Classes as a story · 1 points
HN discussion> That said, the magic with having a big options hash in the `@kea({})` call itself is that then you can easily disconnect the logic from your components as your application grows. Here's more information about this: https://kea.js.org/guide/connected Interesting. I still think these are better modeled (and read) as part of the class declaration. You can do the same thing with mixins: Transforming that example: impo…
Comment linking /2015/12/21/real-mixins-with-javascript-classes/
on “Show HN: Kea – The power of Redux with the simplicity of MobX”The point the OP was making that the class keyword was a mistake, not that inheritance was a mistake. This is an entirely different topic. Furthermore, Javascript classes make writing mixins AKA composition a breeze, compared to before: http://justinfagnani.com/2015/12/21/real-mixins-with-javascr... This link is an excellent rebuttal to Eric Elliot article and how he achieve composition through copying by the way. S…
Comment linking /2015/12/21/real-mixins-with-javascript-classes/
on “Refactoring Legacy JavaScript Code to Use Classes”
