Matry (@matry/dom)

Languages and libraries

ui library

SHOW HN2024

41points
53comments
#1,413of 3,515 in 2024
Top 41%of 2024 by points

How HN took it

MixedNo clear lean

1 positive, 6 neutral or asking, 0 mixed, 6 critical, out of 13 comments about the project. Thread score -0.24.

Idea: 1 for, 3 againstDesign: 0 for, 3 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Interesting novel idea worth discussing

    From 1 comment
    • It's cool to see a novel idea like this get prototyped and then opened up for discussion. As others have hinted at, this feels like jQuery with different syntax and more…
      justin_murray on HN
  • Declarative JSX is appreciated for its clean structure

    From 1 comment
    • The only thing that is awkward imho is the focusing, the rest is a really good fit for declarative, e.g. here's your list of "things", render a UI for each.
      gedy on HN

Objections

  • Essentially jQuery with different syntax and more limitations

    From 3 comments
    • It's cool to see a novel idea like this get prototyped and then opened up for discussion. As others have hinted at, this feels like jQuery with different syntax and more…
      justin_murray on HN
    • This is jQuery-like. Just syntax sugar above the imperative DOM API. Looks like the younger generation didn't know the pain of years of imperative UI "frameworks" and needs to…
      crubier on HN
    • That's the worst idea for framework I've seen recently
      mati365 on HN
  • Lacks React's component isolation and state sync guarantees

    From 2 comments
    • It's cool to see a novel idea like this get prototyped and then opened up for discussion. As others have hinted at, this feels like jQuery with different syntax and more…
      justin_murray on HN
    • Just a few more thoughts to add: When I see code like ``` count++; setContent(<p key="counter">The count is {count}</p>); ``` I immediately think about how someone, at some…
      justin_murray on HN
  • Global keys and selectors risk rogue DOM changes

    From 2 comments
    • It's cool to see a novel idea like this get prototyped and then opened up for discussion. As others have hinted at, this feels like jQuery with different syntax and more…
      justin_murray on HN
    • Just a few more thoughts to add: When I see code like ``` count++; setContent(<p key="counter">The count is {count}</p>); ``` I immediately think about how someone, at some…
      justin_murray on HN
  • Cleanup of timers and effects is not handled

    From 1 comment
    • This is IMO a great example for React and declarative programming. > There's no special concept to understand By not understanding that you need to cleanup timers when your view…
      SebastianKra on HN

Requests

  • Larger examples with widget reuse

    From 1 comment
    • It's cool to see a novel idea like this get prototyped and then opened up for discussion. As others have hinted at, this feels like jQuery with different syntax and more…
      justin_murray on HN
  • Explain the pain points it solves

    From 1 comment
    • Can you talk a little about the pain points you encountered, which this presumably solves?
      lgas on HN

Questions

  • Why use JSX for querying instead of jQuery-style calls

    From 1 comment
    • Hmm, interesting. What advantages do you see of using JSX for querying over the old jQuery-style $("#id").append(...)? Did you consider doing something more like that, but…
      gushogg-blake on HN
  • Why not use template literals or CSS-like syntax

    From 1 comment
    • Why not use template literals and a css like syntax for selecting and update? setContent(css`p[key=counter]{ content: 'The count is ${count}'}; }`);
      fbn79 on HN

Alternatives named

  • jQuery

    From 2 comments
    • It's cool to see a novel idea like this get prototyped and then opened up for discussion. As others have hinted at, this feels like jQuery with different syntax and more…
      justin_murray on HN
    • This is jQuery-like. Just syntax sugar above the imperative DOM API. Looks like the younger generation didn't know the pain of years of imperative UI "frameworks" and needs to…
      crubier on HN
  • React

    From 2 comments
    • It's cool to see a novel idea like this get prototyped and then opened up for discussion. As others have hinted at, this feels like jQuery with different syntax and more…
      justin_murray on HN
    • I have to strongly agree with this. The entire point of react was to avoid all the challenges of old imperative coding of syncing up state with render state. The Dom digging was…
      Justsignedup on HN
  • SolidJS

    From 1 comment
    • > If we accept the fact that the web is inherently imperative, then I believe we can resolve most if not all of the above problems. We don't need to throw the baby out with the…
      udbhavs on HN
  • Mithril

    From 1 comment
    • Mithril seems like it can do something pretty similar: https://mithril.js.org/jsx.html (Not trying to discourage you, just linking it)
      llimllib on HN
  • Google incremental-dom

    From 1 comment
    • This reminds me of google’s incremental dom (https://google.github.io/incremental-dom/ ) it surely made some things (like making sure an element has focus) a lot easier to do and…
      jauco on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/40889951)