Is niché a portmanteau of niche and cliché?

No, it's niche with a French accent

Fun fact: niche is a French word that doesn't have an accent. So niché is the heavy metal ümlaut version.

niche with a french accent sounds like the "nish" in "varnish".

It’s pronounced “NEE-chuh”.

Like Nietzsche?

More like neesh.

Good content.

We're so close to the official V2 release, but there are still issues. I'll make sure to fix most by then. You totally have a point about the lack of an ecosystem, but building one is where the fun is. I am sure we'll get there! Thank you for your feedback.

It's been like that for months - seems like the project is not seeing the activity they expected for v2.

Also server-side routing is broken and that link will not work.

We are very close to the official V2 release, but right now that page is still a WIP.

The link works fine, though.

Also, if you click "join us" and then "tutorial" your scroll position is in an unexpected place.

It’s broken here too.

Do you know why?

Oooh, I see. It (https://hyperapp.dev/ecosystem) is broken if you've never been to https://hyperapp.dev before.

Ah, gotcha gotcha. Thank you for reporting it! :)

Yeah, I got a 404 page when visiting it, too.

I am on macOS / Safari 13.2.1 and I can not visit hyperapp.dev/ecosystem after visiting hyperapp.dev

The link does not work.

Any idea why? Any info you can share would help us debug whatever the issue is.

Missing a wildcard route? No idea how your routing is setup

It's all client-side. When I click that link, it opens the site as usual.

Click the link directly: https://hyperapp.dev/ecosystem

As the parent said, you don't have a catch-all route. That is why!

That's what it is, thank you for clarifying.

Their guide (https://hyperapp.dev/guides) page is also filled with Lorem Ipsum.

Ouch, yes, that's also a WIP, thank you for checking in, though.

The quickstart is quite clear, but I'd love to see some slightly larger examples like, how is state passed between components? How do event handlers work? The API page seems sparse as well.

But it looks like a great start

And you'll get it! Just check again soon as we should have the official release out there in just a few months, maybe less.

> but the lack of ecosystem makes it unfit for anything larger

What does this mean?

Some problems are hard, common and already solved. Sometimes solving these problems yourself adds no unique value to your product. In that case, you should just use a well-reviewed external ecosystem package.

A large project will run into many of these problems. It is a waste to re-invent the wheel because a cool new framework has too few pre-made wheels.

Lack of libraries, as sibling says. Any libraries that exist are not generally well supported relative to similar libs for popular frameworks. Much smaller community, much less ease at finding others who may have had similar issues. Fewer eyes on, fewer bugs picked up. Fewer contributors, slower fixes/updates. Docs there are tend to atrophy faster.

Developed with Hyperapp on big prod apps about three years; was used to inject small amounts of interactive functionality into existing apps (.Net with jQuery powered frontends). Sorta worked, nice, simple idea, but docs almost nonexistent at the time (to be fair there's very little to it), was in process of being dumped for React just as I was leaving (to work on apps with Elm frontends, which Hyperapp takes a lot from, and suffers from similar issues, heh)

I interpret this as you need to do everything yourself rather than using off-the-shelf libraries.

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!

Thank you. That's a marquee haha.