Live data from Hacker News

Viewing profile — TonyPeakman

TonyPeakman

HN member
Joined
Wed, Aug 06, 2025, 8:20 AM UTC
HN karma
48
Public activity
41 items

About TonyPeakman

the author of dagger.js https://github.com/dagger8224/dagger.js https://daggerjs.org

Recent public activity

  1. comment
    Comment #45356076

    Haha, that’s a great way to put it . Writing one-line code does feel clever in the moment, but you’re right, the “writer’s joy” often turns into the “reader’s pain.” Striking the b…

  2. comment
    Comment #45341482

    Thank you — that really means a lot to me. One of the best parts of sharing dagger.js has been hearing from people like you who’ve been down the same path and thought about buildin…

  3. comment
    Comment #45331031

    Hey, I added two more examples about routers for dagger.js: minimal: https://codepen.io/dagger8224/pen/PwZwgWp?editors=1000 nested: https://codepen.io/dagger8224/pen/bNENZNN?editor…

  4. comment
    Comment #45309472

    Thanks a lot for the detailed suggestions — this is super helpful. You’re right that symbols like +/ /@ aren’t valid in XML/XHTML, and the original idea was just to keep things as …

  5. comment
    Comment #45302020

    Thanks for laying this out — I share your priorities on minimal boilerplate and a buildless-first workflow. dagger.js is designed around that: no bundler by default, just HTML + JS…

  6. comment
    Comment #45301864

    Thanks to both of you for the thoughtful discussion — I really appreciate seeing different perspectives here. On the “lock-in” concern: that’s a fair point. dagger.js is still youn…

  7. comment
    Comment #45297003

    That’s a really good point — thanks for laying out the example so clearly. You’re right: Aurelia can avoid a build step and still preserve flexibility, and the kind of helper you s…

  8. comment
    Comment #45296958

    That’s a great example — I agree, with JS Modules and import maps you can already do a lot of dynamic composition in the browser, even with heavier frameworks like Vue. dagger.js i…

  9. comment
    Comment #45276223

    For anyone curious, I’ve put together a collection of comparison demos here: https://codepen.io/dagger8224/pens . They show the same functionality implemented with dagger.js alongs…

  10. comment
    Comment #45276123

    Really glad to hear that — thanks for the kind words! dagger.js is meant for exactly that use case: if you normally avoid heavy JS but occasionally need a bit of interactivity, you…

  11. comment
    Comment #45276113

    Aurelia is a great framework — I really like the way it ties template, JS, and CSS together into one unit. That convention makes it very natural to organize components and reduces …

  12. comment
    Comment #45257231

    Thanks for the thoughtful feedback — you raise valid concerns. The reason dagger.js allows JS expressions in attributes is mostly about lowering the barrier to entry. By keeping ev…

  13. comment
    Comment #45249398

    As a frontend framework, Svelte apps absolutely run in the browser.However, Svelte relies on a compile step: your authoring code is compiled ahead of time into efficient JS that ru…

  14. comment
    Comment #45248390

    Glad to hear that! Buildless is the whole idea — drop in a , wire up a few +click / +load attributes, and you’re up and running. The goal is to keep things simple and view-source-a…

  15. comment
    Comment #45247996

    Well put — that lines up with how I see the ecosystem too. For small sites, vanilla JS is fine; once you move toward “app,” you either reach for a framework or start reinventing bi…

  16. comment
    Comment #45247992

    That’s totally valid — if you’re comfortable living close to the DOM, zero-runtime + zero-build is the purest path. dagger.js is meant for folks who want to stay mostly in plain HT…

  17. comment
    Comment #45247984

    Haha, true — the front page doesn’t always need another JS framework dagger.js is tiny and pretty niche compared to the “big ones,” but I figured it was worth sharing since it’s tr…

  18. comment
    Comment #45247977

    Totally agree — the ESM build of Vue gives you a great “no-bundler” experience with a full framework behind it. dagger.js sits in the same no-build space, but deliberately strips i…

  19. comment
    Comment #45247970

    That’s a good point — the ESM build of Vue is solid, actively maintained, and does give you a no-build setup with the full feature set. dagger.js aims a bit differently: it’s even …

  20. comment
    Comment #45247955

    Yeah, that’s a fair comparison — Dagger.js lives in a similar space to petite-vue / Alpine: no build step, HTML-first, sprinkle behaviors where you need them. The main differences …

  21. comment
    Comment #45247929

    Good catch — thanks for digging into that. You’re right: the domain still has a mix of A records (AWS + GitHub Pages), which explains why some people see different results. I have …

  22. comment
    Comment #45247918

    Exactly — that’s a good way to frame it. One of the reasons I kept Dagger.js tiny and runtime-only was to minimize those risks: no exotic build chain that might break, and nothing …

  23. comment
    Comment #45247899

    Totally fair — longevity is a real concern, and I’ve had the same hesitation with new tools myself. The nice thing about Dagger.js is that it’s intentionally very small and HTML-fi…

  24. comment
    Comment #45247831

    Really appreciate you taking the time to look through the docs and write such a thoughtful comment. You’re right — JavaScript carries a lot of quirks and limitations that aren’t go…

  25. comment
    Comment #45247791

    Thanks! Totally agree — in most real-world apps the “runtime overhead” ends up dwarfed by everything else in the stack, so the build-free ergonomics can be a bigger win. And nice, …