hyperscript VS _hyperscript

* 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 ?

This works like Reactʼs createElement function. Or a library such as hyperscript. Sure, weʼd prefer JSX for its much reduced cognitive load. But our alternative here is the DOM methods such as createElement. Unless we want to load up a bulky library such as React, that is.

Consider looking at hyperscript, which is a plain-javascript library for constructing html nodes (NOT a transpiler). Similar to what you have here, but way nicer

In fairness, there's a lot of overlap between embedded DSLs and libraries — a library like Hyperscript for generating HTML in JavaScript is in many ways a DSL, but it's also just a bunch of functions that are easy to put together in a particular way. But this is often good enough!

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

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.

With Mithril.js, you generate HTML using a hyperscript dialect like this:

I'm confused. Hyperscript is supposed to be an alternative way to writing JSX.

Hyperscript.org doesn't seem to be related to this at all?

https://github.com/hyperhype/hyperscript

The reason is dead simple. It's exported as h because it's a hypescript function. So what exactly is hypescript?

It seems to be this one:

https://github.com/bigskysoftware/_hyperscript

https://hyperscript.org/

but no sure it's anything to do with the OP though

You could help hyperscript get to a stable 1.0 by reading docs and writing up some use cases if you know anything about front end web development

If we returned from a function, we step out of it (discussed below). Otherwise, if the command returned a Promise, we await the next command, set cmd to it, notify the event bus and log it with some fancy styles. If the result was synchronous and is a HALT; we stop debugging (as I write this, I'm realizing I should've called continueExec() here). Finally, we commit the kind of code duplication hyperscript is meant to help you avoid, to handle a synchronous result.