hyperscript

Maybe you could try with hyperscript syntax for react(which I've just found the existence of). https://github.com/hyperhype/hyperscript https://github.com/mlmorg/react-hyperscript which might be actually similar except for the dollar sign which adds some noise. But some of your prop/attr setting would be inner function/methods instead of being passed as an array. That would shorten some lines. > Show me what that code would look like if it was done better I'm definitely not going to try to provide an example if you do not offer the courtesy of a smaller representative example though. By the way, why is $(Label,...) not simply Label()? That could be a function.

One of the comments the other day was "You have reinvented Hyperscript". In case you didn't see it, they meant this [0] and also this [1]. I don't mean this as a critique or dismissal of your idea, but I think it's fair to prefer Hyperscript since it's well tested code and has a couple of additional features (like event handler support) without being much larger than your own code. Also, I think Hyperscript is more correct in the way they build the elements. [0] https://github.com/hyperhype/hyperscript [1] https://github.com/ohanhi/hyperscript-helpers

Your project looks great and I like the fact you can use it with MicroPython. I've also been working on a library with a similar idea: https://github.com/SamDudley/neat-html It's still a work in progress so an example might be better to look at: https://github.com/SamDudley/neat-html/blob/main/examples/fo... I was inspired by some JavaScript libraries that I've used in the past: - https://github.com/jorgebucaran/hyperapp - https://github.com/hyperhype/hyperscript There is also a working integration with Django that enables the use of neat-html as a template backend, however it isn't up on GitHub yet. I find the space of HTML generation libraries which can leverage the power of Python, really interesting.

Does anyone else get this confused with https://github.com/hyperhype/hyperscript ?

Hyperscript (https://github.com/hyperhype/hyperscript) is actually quite nice when you get used to it, and I actually prefer it over JSX. Pair it with something like microh[0], and it gets even better. [0] https://github.com/fuzetsu/microh

I believe you are talking about this hyperscript: https://hyperscript.org/ Whereas the parent post is talking about: https://github.com/hyperhype/hyperscript Unfortunately, the creator of https://hyperscript.org/ hijacked the name even when the term "hyperscript" is still used to refer to dominictarr's project and the `h('p', 'hello world') API of declaring templates in JavaScript (as seen in React, Preact, Mithril, etc.).

>The key reason web frameworks dominate these days is that it's very hard to keep the UI in sync with state. This isn't wrong, but going one level down, this is how it bites you: - The imperative DOM api just suuuucks. Please try it for yourself to see. Even if you're writing a very limited bit of reactivity in your app, you will be forced to invent your own declarative framework very soon. - Very hard to make reusable components (at least before webcomponents, which I haven't used personally) If you want to stay close to vanilla, I recommend one of the following solutions: 1) https://htmx.org/ 2) https://github.com/hyperhype/hyperscript 3) https://github.com/vuejs/petite-vue

It’s an interesting idea but I don’t appreciate the name hijacking. Hyperscript has been around for a long time: https://github.com/hyperhype/hyperscript

The naming of this project clashes horribly with https://github.com/hyperhype/hyperscript. It's not like it's in a different ecosystem or something. It is a web project that is guaranteed to cause confusion.

Hyperscript already has an established meaning in this space, as a pure JS-based syntax alternative to JSX. See https://github.com/hyperhype/hyperscript and all its descendants, like Mithril, HyperApp or Sinuous. Could you please think of another name ?

That name is unfortunate because there's already a hyperscript: https://github.com/hyperhype/hyperscript which is completely different (which I am quite enjoying for constructing virtual dom in pure js)

For a moment I was very confused since I remembered hyperscript being this and existing for a longer time: https://github.com/hyperhype/hyperscript Hopefully you are already aware of the name clash. I am definitely interested in your hypescript more than the old one but the name clash is unfortunate.

Not to be confused with hyperscript[0] hyperscript[1] hyperscript[2] hyperapp[3] [0]: https://github.com/hyperhype/hyperscript [1]: https://cycle.js.org/api/dom.html#api-h [2]: https://github.com/vuejs/babel-plugin-transform-vue-jsx/issu... [3]: https://github.com/jorgebucaran/hyperapp

Not to be confused with HyperScript [0], a popular JS templating library. [0] https://github.com/hyperhype/hyperscript

I believe jorgebucaran (hyperapp author) was aware of mithril.js' existence and may possibly have been inspired by it, but I don't take credit for hyperscript itself (it was already a concept used by various other systems - the word "hyperscript" itself comes from the name of a project[0], and there were already other similar frameworks like mercury[1] at the time). For mithril.js specifically, the hyperscript variation offers an extra feature that AFAIK not many other libs do: the ability to write emmett-like CSS expressions as the tag name (e.g. `m('input.required[type=password]')`). Totally understandable if you think that's too much sugar for your lib, but I've found it handy for usage with CSS frameworks like bootstrap. Mithril.js users also appreciate it and some interesting unexpected patterns came out of that (e.g. `const Foo = '.