111–120 of 169 posts
Earlier quoted context omitted.
Yeah nah, I'm not watching a 30mn video on something I'm not interested in to get what amounts to a 2-paragraphs answer.
30m sends you home? Watch it on 2x and skip parts you aren't interested in.
Earlier quoted context omitted.
We use Hyperapp to power our most complex UIs (decision trees, onboarding sequences, etc.). We didn't need any of the existing React ecosystem for that, and by removing React, we saw several benefits: 1. Smaller library for faster page loads 2. Simpler API, docs and library made it easy to get started and understand what's happening behind the scenes as well as debug any issues we faced 3. We aren't supporting a proj…
Why not Preact?
Hyperapp is Elm-like state management (and soon effects and subscriptions in 2.0) on top of an ultra-lightweight virtual DOM diff engine.
Preact is a React 15 clone at best. Check out also https://github.com/NervJS/nerv for another React clone that is closer to React 16 (but still no fiber).
This is an exceptionally simple library to use in place of React. Both its performance and the development experience have been great. My company's been using it in production for more than a year now without any issues. Highly recommend giving it a look.
people should really give it a book
There's a book though: https://booth.pm/ja/items/825889 (Japanese)
If you're interesting in a reactive template library that doesn't require a compiler for non-standard JavaScript syntax, check out a library I've been working on for a little while now, lit-html: https://github.com/Polymer/lit-html Where JSX would look like this: const view = (state, actions) => ( {state.count} actions.down(1)}>- actions.up(1)}>+ ) The lit-html would be: const view = (state, actions) => html` {state.…
But then you miss out on html syntax highlighting and jsx eslint. Or is there tooling that works for the tagged template approach?
This makes me almost want to write web code again - compared to things like React and Angular 1-2-3-4-5-6.
Just curious what intrigues you about this framework in ways that React does not?
Earlier quoted context omitted.
Not sure what your problem with React is, is it the configuration?
React is a ghetto, basicly + vdom has its own size. IMO thing like hyperhtml or lit-html are the way forward - especially with new templating proposals. Not to mention react is not interoperable really with other solutions - I'd expect webcomponents win long term, since they are built into clients.
This looks pretty awesome! Inspired by hyperscript I assume? https://github.com/hyperhype/hyperscript Question: I was looking over the source and noted that you weren’t building your virtual dom with the document fragment API https://developer.mozilla.org/en-US/docs/Web/API/DocumentFra... Is there any particular reason why? I’m curious because it’s my general understanding that creating a document fragment and attach…
I've seen "Show HN: HyperApp" type of submissions at least 5 times earlier. Congrats, you made a 1Kb JS library. Please stop spamming HN though. https://hn.algolia.com/?query=hyperapp&sort=byPopularity&pre...
Here is another angle to this: go into React type of submissions and ask them to stop spamming HN with that?
https://hn.algolia.com/?query=react&sort=byPopularity&prefix...
I've seen "Show HN: HyperApp" type of submissions at least 5 times earlier. Congrats, you made a 1Kb JS library. Please stop spamming HN though. https://hn.algolia.com/?query=hyperapp&sort=byPopularity&pre...
I don't even get why it is important that it's 1kb. Give me a library with great API and easy to use. Nobody cares if library is 1kb or 100kb (minified).
It's not very performant compared to other v-doms https://rawgit.com/krausest/js-framework-benchmark/master/we...