gdotdesign

Thank you for this comment! It really helps a lot to get decent feedback.

> What I didn't see is some performance promise like Elm, or simplicity, where it make sense to use this over anything else.

I was focusing on the example, it seems I should really put up more information about this on the website, but to answer for this is basically:

- it uses React under the hood meaning you have the same performance, the devtools works the same, it is possible (with some work) to use components from Mint in React and vice versa.

- the error messages are really nice (there 281 unique error messages overall) both for syntax errors and type errors

- easy JS interop using backticks

- no import statements

- fast compile times (the website compiles around 1 second)

- single binary with all the tools included (development server, production builder, favicon generator, test runner)

> The downside is really a combination of building a community and educating people about it

Yes, this is what I'm worried about.

I'm still tweaking a lot of things and I wanted to share it with HN when I thought it was ready, but on the other hand it's a nice that it got some attention already.

I hope there will be enough interest over time to actually build up a community.

The author here, I was using Elm for a while invested a lot of time in it so there are parts of it that I like and that are parts that I don't.

In a sense it tries to be like Elm:

- good developer experience with nice error messages

- single binary that have all the tools

- enforcing types

- no runtime exceptions is you don't use JS interop

In an other sense it tries not to be like Elm:

- JSX syntax with easy compose-ability

- Straightforward JS interop

- Decentralized and open package management