4 ms·

Thank you! This is exactly the kind of feedback that we need to improve our presentation. I might just update the tutorial to use @hyperapp/html [1] instead. [

Thank you! This is exactly the kind of feedback that we need to improve our presentation. I might just update the tutorial to use @hyperapp/html [1] instead. [1]: https://www.npmjs.com/package/@hyperapp/html https://www.npmjs.com/package/@hyperapp/html

hellcow 6y ago
Please don't. Not everyone uses these additional libraries or preprocessors, and it was a big hurdle to figure out what was actually being generated behind the scenes in the v1 docs. A good approach is to show us what we need to do with no other dependencies (i.e. just as you're doing now with this h() function), and link to alternative syntaxes/libraries that may be optionally used instead.
- jorgebucaran 6y ago
  Thank you for the feedback. I'll keep this in mind too. I'm definitely not advocating JSX usage. I favor hyperscript myself, but I understand it's an acquired taste. Idiomatic JavaScript alternatives that don't involve compilation include: - https://github.com/zaceno/hyperlit https://github.com/zaceno/hyperlit, and the aforementioned - https://www.npmjs.com/package/@hyperapp/html https://www.npmjs.com/package/@hyperapp/html
tobr 6y ago
A nice flourish would be to have every example with both, and have a global switch to pick which one you prefer.
onetom 6y ago
the tutorial is great this way. it's gradually introducing concepts and shows what's possible with very few building blocks. at the end, it would be nice to mention that at the cost of some extra code and learning a few more functions/concepts, you can gradually make application code either more concise with @hyperapp/html or having a different aesthetic or more familiarity - similar to JSX - with htm or the hyperapp-tailored variant of it, hyper-lit. but please keep the current didactic of piecemeal introduction of concepts, providing clear reasons for their existence!

hellcow 6y ago

Please don't. Not everyone uses these additional libraries or preprocessors, and it was a big hurdle to figure out what was actually being generated behind the scenes in the v1 docs. A good approach is to show us what we need to do with no other dependencies (i.e. just as you're doing now with this h() function), and link to alternative syntaxes/libraries that may be optionally used instead.

jorgebucaran 6y ago
Thank you for the feedback. I'll keep this in mind too. I'm definitely not advocating JSX usage. I favor hyperscript myself, but I understand it's an acquired taste. Idiomatic JavaScript alternatives that don't involve compilation include: - https://github.com/zaceno/hyperlit https://github.com/zaceno/hyperlit, and the aforementioned - https://www.npmjs.com/package/@hyperapp/html https://www.npmjs.com/package/@hyperapp/html

tobr 6y ago

A nice flourish would be to have every example with both, and have a global switch to pick which one you prefer.

onetom 6y ago

the tutorial is great this way. it's gradually introducing concepts and shows what's possible with very few building blocks. at the end, it would be nice to mention that at the cost of some extra code and learning a few more functions/concepts, you can gradually make application code either more concise with @hyperapp/html or having a different aesthetic or more familiarity - similar to JSX - with htm or the hyperapp-tailored variant of it, hyper-lit. but please keep the current didactic of piecemeal introduction of concepts, providing clear reasons for their existence!