mixing the turing complete of javascript with the markup of HTML eliminates the readability of JSX so that it is actually harder to parse than a solution like hyperscript
12 Matching Annotations
- Oct 2020
-
-
-
hyperscript is much simpler to refactor and DRY up your code than with JSX, because, being vanilla javascript, its easier to work with variable assignment, loops and conditionals.
-
I have a few colleagues that converted to hyperscript, and while they were adverse at first, they were satisfied with having switched once they had become comfortable with the way it looks/reads.
-
hyperscript is a perfectly good alternative and uses the same interface as matt esch's virtual-dom
Tags
- making it easy for later refactoring
- bad combination/mixture/hybrid/frankenstein
- readability
- javascript
- react-hyperscript
- comfortable
- good point
- template language vs. reusing existing language constructs
- reuse existing language constructs
- missing out on the benefits of something
- same/compatible API
- comfortable because familiar
- hyperscript
- JavaScript
- Turing complete
- comparison with:
- JSX
- it's just _
- overcoming preconceived opinions
- hybrid/mixture
- virtual-dom (library)
- template language: bad: by not reusing existing language constructs; forced to reinvent equivalents which are inferior and unfamiliar
- changed their mind/opinion
Annotators
URL
-
-
github.com github.com
-
JSX remains dominant syntax for React. Still, pretty cool. And inspiration for svelte-hyperscript probably?
-
-
Hyperscript syntax for React.js markup
-
-
github.com github.com
-
Create HyperText with JavaScript
I assume that's where the name "HyperScript" came from? A portmanteau?
-
hyperscript
-
-
github.com github.com
-
svelte-htm - Hyperscript Tagged Markup for svelte; a jsx-like syntax using Tagged Templates
-
-
github.com github.com
-
Solid supports templating in 3 forms JSX, Tagged Template Literals, and Solid's HyperScript variant.
-