Earlier quoted context omitted.
We are very close to the official V2 release, but right now that page is still a WIP. The link works fine, though.
It’s broken here too.
Do you know why?
Hyperapp – A tiny framework for building web interfaces
71–80 of 198 posts
Re: Hyperapp – A tiny framework for building web interfaces
#72Earlier quoted context omitted.
Not sure of the reason, but it's a godsend comparatively. The reaction against JSX I find to be largely by people who've never actually used it. If you keep your components small, as is best practice, whatever gut reaction one feels to it (which IMO is misplaced to begin with) is minimized, and quite readable.
My big issue with JSX is that it forces you to use a pre-processor and source maps. If you have to do that anyway, I think I could use JSX instead of "pure" JS.
The _only_ reason I use webpack and friends are for JSX and Typescript. For me, those two tools are worth the compilation step. Qs soon as it's possible to stop using compilers while still enjoying the benefits of both, I'll dump them from all my codebases.
Re: Hyperapp – A tiny framework for building web interfaces
#73Earlier quoted context omitted.
Text templates are a good idea, placing them into the middle of JavaScript code, not really.
I absolutely disagree, but I also feel it's unfortunate that HTML, CSS, and SQL aren't first-class citizens in most languages. It's strange to treat things backed by entire standards bodies and with fully developed ASTs as plain-text. It seems unnecessarily limiting, and I'm not sure why; For the sake of history? "Division of Concerns"? How is it that using libraries meant for string manipulation upon a standardized…
We aren't, only those that keep fighting against MVC, HTML Templates and Web Components are.
Re: Hyperapp – A tiny framework for building web interfaces
#74Re: Hyperapp – A tiny framework for building web interfaces
#75Re: Hyperapp – A tiny framework for building web interfaces
#76I have tried Hyperapp some time ago. It's usable for small apps, but the lack of ecosystem makes it unfit for anything larger -- as is usual for all niché JS frameworks. Funnily, the "ecosystem" page contains just Lorem Ipsum ( https://hyperapp.dev/ecosystem ) and the Awesome Hyperapp section for V2 is almost empty ( https://github.com/jorgebucaran/awesome-hyperapp )
> but the lack of ecosystem makes it unfit for anything larger
What does this mean?
Re: Hyperapp – A tiny framework for building web interfaces
#77I have tried Hyperapp some time ago. It's usable for small apps, but the lack of ecosystem makes it unfit for anything larger -- as is usual for all niché JS frameworks. Funnily, the "ecosystem" page contains just Lorem Ipsum ( https://hyperapp.dev/ecosystem ) and the Awesome Hyperapp section for V2 is almost empty ( https://github.com/jorgebucaran/awesome-hyperapp )
> but the lack of ecosystem makes it unfit for anything larger What does this mean?
I interpret this as you need to do everything yourself rather than using off-the-shelf libraries.
Re: Hyperapp – A tiny framework for building web interfaces
#78React was made in 2013 and is pretty old at this point. How does Hyperapp compare to current tech like Svelte?
Re: Hyperapp – A tiny framework for building web interfaces
#79Re: Hyperapp – A tiny framework for building web interfaces
#80Now it looks like Elm
Exactly! And the latest version (which is not officially out yet) is even closer to Elm that the first version ever was.