aabbcc1241

The syntax looks similar to dom-proxy [1]

[1] https://github.com/beenotung/dom-proxy

The download count may not reflect the adoption rate. It is largely affected by CI/CD.

You can drop this script on your website then it'll likely just work

    <script type="module" src="https://cdn.jsdelivr.net/npm/@bufferhead/nightowl@0.0.12/dist/nightowl.js"></script>

You may have a look at zeronet and ipfs, they're not blockchain but maybe interesting to you

I use a local hosted web spider and search engine

It only index the pages that I've viewed so it's not spammed by SEO junks

https://github.com/beenotung/personal-search-engine

You may try cast.ts. It is similar to zod but the parser has .type property which expose the typescript type of the validator, and .sampleValue property which expose a sample value. So you can access the metadata at runtime, which can be reused by other tools like yours.

Maybe you want a Typescript SDK more than a HTTP endpoint.

the flexibility you describe seems to be coming from lisp (schema) that javascript was designed on top of initially

previous discussion: https://news.ycombinator.com/item?id=28511570

You can use validator like populate-env[1] to check for missing env variables

[1] https://www.npmjs.com/package/populate-env

The render function is a pure function returning jsx based on the input, not invoking any stateful operation like "functional hook".

So this style of code is fine in react

I want to add more on the “other staff you should try” list:

- phoenix liveview / ts-liveview / hotwire

- htmx

- clojure

- cycle.js

- dom-proxy

- data-template

The title is misleading, there is schema (defined with zod in specific)

The approach mentioned in this article is more abstract than SSR and liveview, making it adaptable to both webapp and mobile app

> I can't imagine things being much simpler than this

Imagine simplifying the last example without useState and setState, nor useEffet and depList

The setup can be automated with bash script or "npm init <template-name>" or unzip from a template archive

Do you mean hacker news as "this site"? HN seems to be server side rendered, so it should display well without Javascript.

An alternative web search architecture, is collaborative sharing the site we made or visit.

I made a self hosted spider that only index sites that I've visited and search engine with "and" "or" logics.

Thinking to make it a federated search engine by allow each user whitelist domains that are not sensitive to search with the peer. And users can follow/block other users explicitly to avoid spam.

https://github.com/beenotung/personal-search-engine

You can write custom jsx function and let typescript call your function instead of react's.

Your custom jsx function can return data in reusable format, that is passed to different functions for difference use case.

ts-liveview is using this approach to use jsx for both server-side rendering and compact over-the-wire updates

Yes, the demo in readme shows you to create/edit source code in type-safe manner

Youglish [1] is a website that allow you to search video with timestamp by transcript text

[1] https://youglish.com/

That's interesting!

I think Typescript would be "easier" for a larger group of developers to hook on

Maybe a transpiler and type checker that convert typescript into erlang can help to drive the adoption

dom-proxy is the most recent work, I'm glad it stands out to you

Wish you'll keep up and see more adoption over time :)

I made a similar library [1] using data-* attributes. It also supports nesting, looping and conditions. For event handling, I use function in object (a.k.a. method) while you support writing them inline.

Your way to support inline logic in the text and style is interesting.

[1] https://github.com/beenotung/data-template

Would you also add these js library to the list? They don't require build step as well.

https://github.com/beenotung/html-template-lite

https://github.com/beenotung/data-template

https://github.com/beenotung/dom-proxy

I'm experiencing the trade off between simplicity and expressiveness for a lightweight frontend library that doesn't involve VDOM.

On one hand, a library [1] can be very concise (update dom from object, with looping and nesting supported).

On another hand, a library [2] can be very flexible and reactive (update dom from dom events).

However, when double-binding (a.k.a. bi-directional binding) is required (update dom from object and update object from dom), it seems more complex than I would consider it lightweight.

When double-binding is preferred, I'd rather go for angular / vue. Still exploring alternatives.

[1] https://github.com/beenotung/data-template

[2] https://github.com/beenotung/dom-proxy

This concept is similar to liveview, with suggestion to run the backend in local / remote environment

Develop lightweight and declarative UI with automatic dependecy tracking without boilerplate code, VDOM, nor compiler.

The concept is to use Proxy API to wrap the DOM object, and auto keep track of the dependency of some reactive statements.

The DOM event listener is auto setup to trigger re-run when the UI is updated by user, and the proxy setter triggers re-run when other part of code is updating the reactive statement's dependency.

The current implementation is a lightweight library with inferred Typescript types.

This design could be extended to support server side rendering as well.