TBH, I'm not very sure what web3 backend is 🤣. But the answer is 100% yes!

FormML only focuses on the problems of how people model/build/submit (in plan) forms. It has no opinions on how to store form data. You can of course store them anywhere, including on blockchains.

This option does look prettier, but I'm hesitant b/c

1. It simplifies user writing but increases implementation complexity, and potential conflicts with a planned feature - multi-language support

2. Type doesn't seem to be an overly difficult concept. It also exists in some graphical form builders

💯

BTW, "I have failed any coding course I have taken" - It's a little hard to believe since you have a penguin avatar 🤣

Feel free to give a ⭐️ if you are interested in its idea 🙏🙏

Also, there is a post in HackerNews , feel free to upvote it. Thanks a lot! 🙇

Got it. It's a little confusing for people who never learned programming. Sadly the type info is critical for a PL, we can only simplify it w/o completely eliminating it.

One direction is postfix types + type inference.

Again, it only simplifies things and doesn't seem to solve people's problem.

Thanks for your feedback!

Do you mean the concept of "type" of a field is confusing to non-programmers?

Or you mean abbreviations are confusing? (e.g. num vs number)

Same 😂

I started using it to quickly build slides, but always ended up spending too much time fiddling with custom styles.

Ok, seems they only suits scenarios that people don't really know what date they want to input.

So what's the real use case of such popular date pickers that have fancy functionalities? I even cannot imagine one ATM...

Typically there is a date picker that also supports input date directly I guess? 🤨

BTW, your proposal of `.fml` was accepted @sinfullycoded.com 😜

@jionnymagiah.bsky.social @sinfullycoded.com @karlhorky.com

I wrote a blog to share the motivation of FormML. See if it makes any sense for you.

.ninja is cool as a domain!

TBH, as a Chinese, it's hard to understand why the concept of ninja is so popular in the English world. 🤣

In this side of the world it is just a niche Japanese cultural symbol. 🤔

How does FormML address them?

By out-of-box features:

👨‍👩‍👧‍👦 Non-dev friendly DSL
✂️ Model-View separation
🔄 First-class dynamic forms support
⚡ First-class real-time forms support

and so on.

Imagine you're a financial company building a loan application form. What challenges might you face?

I list some in pic.

They aren't problems specific to only this case, but common challenges when building complex forms.

I call forms with similar pain points "Enterprise-Level" forms.

Forms can be simple or complex.

While there are many awesome tools in ecosystem for building basic forms, such as React Hook Form.

There isn't yet a serious solution (to my knowledge) that specifically addresses the pain points of really complex ones - Enterprise-Level forms.

It's not related to React. It's a magic provided by bundlers (webpack, vite etc.)

There is also a native feature in ECMAScript called "import attributes" may can help. But it's too new so not well supported by ecosystem yet. I have no idea how to take advantage of it at current stage.

Oops! Transparent bg looks a little weird, here are white bg versions.