Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hyperapp – A tiny framework for building web interfaces

hyperapp.dev

Post reply on HN
Print view View original

161–170 of 198 posts

Re: Hyperapp – A tiny framework for building web interfaces

#161

Post by franciscop »

mrozbarry wrote: post #34

Bit of a Hyperapp fanboy here, so bare with me. First, I think Hyperapp can make both small and big applications, opposed to u/PufPufPuf's opinion. A lot of people have this opinion because they are more familiar with v1's wired-in actions, which can become quite unruly. In the latest version, actions are decoupled, and can be organized/extracted however you see fit. I've made a handful of applications in both v1 and…

> "A lot of people have this opinion because they are more familiar with v1's wired-in actions, which can become quite unruly."

u/PufPufPuf only mentions the lack of ecosystem, nothing about the wired-in actions/etc, so it's odd that you defend v1 vs v2 instead of the lack of ecosystem here. This should probably have been a reply to that thread as well because otherwise it's two very unrelated comments in the list.

Re: Hyperapp – A tiny framework for building web interfaces

#162

Post by wes-k »

wackget wrote: post #143
Kiro wrote: post #120

Earlier quoted context omitted.

There has never been any separation of concern in web development. Just because you put your scripts, HTML and CSS in different files doesn't mean they are separated.

Isn't that the definition of separated? If you want to edit content or markup, you open the HTML file. If you want to edit business logic, open PHP or JS. And so on.

They are still tightly coupled.

Re: Hyperapp – A tiny framework for building web interfaces

#165

Post by Uehreka »

foobarbecue wrote: post #33
PufPufPuf wrote: post #7

I 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 )

Is niché a portmanteau of niche and cliché?

It’s pronounced “NEE-chuh”.

Re: Hyperapp – A tiny framework for building web interfaces

#166

Post by _old_dude_ »

jorgebucaran wrote: post #130
hellcow wrote: post #92

Earlier quoted context omitted.

Agreed. The lack of lifecycle events in v2 complicates things a great deal for seemingly no reason. Subscriptions and Events are similar enough that they could have become a single thing, instead of having two highly similar but not-quite-the-same things to grok. The tuple syntax it uses is very strange coming from v1. I wish I could call it a strict upgrade instead of saying "some things are worse, but other things…

It's my fault for not fully understanding the functional universe I was getting into when I first started working on Hyperapp. The latest Hyperapp is more strict, but it's all in good measure. Lifecycle events are impure, that's why they're no-good. I can tell you that Hyperapp is not for everyone. If you want to write pure, immutable, functional JavaScript and think hard about client side app architecture (unidirect…

If we talk about functional API, did you consider providing a push method, like with a Promise, to express the updating of an effect or a subscription ?

(the function 'update' in the code below)

  app({
    init: 0,
    view: state =>
      h("div", {}, [
        h("h1", {}, state),
        h("button", { onclick: (state, event, update) => {
          window.setTimeout(() => update(state => state - 1), 1000);
        } }, "subtract"),
        h("button", { onclick: state => state + 1 }, "add")
      ]),
    node: document.getElementById("app")
  })

Re: Hyperapp – A tiny framework for building web interfaces

#167

Post by AndrewUnmuted »

PufPufPuf wrote: post #7

I 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 )

To be fair, they did make a pretty deliberate effort to warn visitors that the website is incomplete, with some animated text:

> this site is a wip, stay in touch!

Re: Hyperapp – A tiny framework for building web interfaces

#168

Post by pryce »

com2kid wrote: post #131
onetom wrote: post #101

Earlier quoted context omitted.

I can highly recommend you watching this talk: https://github.com/matthiasn/talk-transcripts/blob/master/Hi... It explains very well why is something being easy shouldn't be the main metric, when choosing some technology. In this case you are advocating to pull in webpack (28MB, 348 packages from 210 contributors), @babel/core (12MB, 54 packages from 60 contributors), typescript (53MB, 11 packages, 4 contributors), t…

If you are doing back compat for old browsers, Babel is necessary anyway. Typescript is a choice independent from anything else. There are alternatives to Webpack, none of which have gained traction, possibly because developers appreciate other features that webpack provides out of the box. But, you are complaining about the developer tools, why? The source code size of emacs/vscode/vi is just as relevant, or the siz…

> But, you are complaining about the developer tools, why? The source code size of emacs/vscode/vi is just as relevant

I think you have a fair point that if it's not making the build artefacts larger in size it shouldn't be criticized for that.

Where the problem arrives is really about cognitive load: If my tools are emacs/vscode/vi or even visual studio or webstorm, I can use these tools, and come back to them in 18 months for a different project and use the new versions without giving it more than a few seconds of thought.

With Webpack, I am strongly encouraged to use create-react-app to allow for sane creation of new react apps with React/Redux/SASS. But: it's April 2018 and create-react-app doesn't yet support TypeScript, so I have to find somebody's forked version of it that does, but then that forked version doesn't support SASS, so I have to stitch support for that together into my own fork, and then understand it well enough to debug that if it doesn't immediately work.

When I want to make a new app 18 months from then, there is a new version of Webpack, CreateReactApp, etc which finally adds full typescript support, but the way these tools are configured is completely different which itself requires a lot of time and effort to adjust for.

The truth is that the experience of using a developer tool like Webpack is categorically very different than choosing your Code editor.

Re: Hyperapp – A tiny framework for building web interfaces

#169

Post by ehutch79 »

jorgebucaran wrote: post #115
ehutch79 wrote: post #95

This page does not inspire confidence in the framework. I don't need a non-ui piece of software to have the slickest site... but no lorem ipsum please.

I put it there, so I apologize for it. We were in the middle of a rewrite while working towards the official V2 release and weren't expecting to be on HN right now haha. Thanks for chipping in!

Ouch. that's rough.

I've seen some incidents before where backend frameworks were posted before they had things like authentication ready.

Re: Hyperapp – A tiny framework for building web interfaces

#170

Post by paultannenbaum »

mrozbarry wrote: post #34

Bit of a Hyperapp fanboy here, so bare with me. First, I think Hyperapp can make both small and big applications, opposed to u/PufPufPuf's opinion. A lot of people have this opinion because they are more familiar with v1's wired-in actions, which can become quite unruly. In the latest version, actions are decoupled, and can be organized/extracted however you see fit. I've made a handful of applications in both v1 and…

Your mobtime app does not look like it was built with hyperapp, but instead is using ferp.
Post reply on HN