Show HN: Zero – DX focused non framework to interact with the DOM

33 pointsposted a year ago
by _nhh
(github.com)

14 Comments

5cott0

a year ago

Interesting, I cooked up something similar a few years ago to use on my personal website and d3.js viz projects. Originally for use with webpack/babel but now I use it exclusively with Vite.

https://www.npmjs.com/package/jsx-pragma

_nhh

a year ago

Nice work! JSX is such an awesome piece of technology. Using it with the dom feels like a component based and maintainable jquery.

dvh

a year ago

Isn't there xss in the first demo? What if title is user supplied and it's something like <script>alert("xss")</script>

_nhh

a year ago

User supplied stuff must always be sanitized :)

skeptrune

a year ago

API would be the proper term for this, no?

Maybe "typed API"?

_nhh

a year ago

What do you mean?

skeptrune

a year ago

"non framework" just seems like a weird term

_nhh

a year ago

I agree :D Do you have a better term for a thing that does not want to be a framework? Maybe it's really just code snippets. It's also not really an API, because the API is the DOM. :thinking:

meiraleal

a year ago

There is no way to not be a framework. A bunch of code snippets is already one.

_nhh

a year ago

That would make every stackoverflow snippet a framework. I mean framework in the sense of products like next.js/nuxt.js.

bitbasher

a year ago

I'd like to understand when the term "DX" was popularized. It certainly feels like it was a rather recent invention and often tied to a tool or platform to get locked into.

If I were into conspiracies, I would hazard a guess the term "DX" was created by a marketing department for a PaaS.

ivanjermakov

a year ago

DX is a compelling argument to sell one more level of indirection (i.e. framework or metaframework or whatever "non framework" means)

_nhh

a year ago

I agree. There's a fine line between useful abstractions and bloat.

_nhh

a year ago

For me great DX is when the editor provides useful information about my code. :)