1. Always a red flag, we don't really consider any tools which require a bespoke programming language. We prefer the tool developers focus on the problem and not be distracted with the tasks of implementing a language. We also don't want to waste developer cycles on a tool specific language. FWIW, we are moving these kinds of things to Dagger
Bespoke language for inflight, no thanks, we do not want to develop our applications in a bespoke language and ecosystem. The trade off is too big and risky. It would also be a nightmare to hire and retain talent
Wing, wasp, and darklang all suffer from these issues.
I get where you're coming from about a new language for inflight. We will have support for existing languages in the future, through an SDK, although you will not get all the benefits of the Wing compiler this way.
About #2, we've identified the issue to be the lottie animations. Working on a fix
1. Why should users need to learn a bespoke language where an SDK in our primary languages could be better?
2. Why does your landing page use 100% CPU indefinitely?