ianertson

Thank you!! Indeed, it's really fun actually

It's definitely not a language that needs to be created. I was just in the need for a scripting language in my game engine, and I wanted something that felt like GLSL.

Well, I'm going to use it for one of my personal projects. I wanted a scripting language for a game engine that I'm working on, and wanted something that felt like GLSL

Right, I'll have to fix this too

Yes, this is because Im building it in "dev" for FJB as well. The circumstances should be equal for all benchmarks.

Sure, but it was just an example of what kind of things FJB is doing to the code

What I mean with "adapts the code through static analysis" is:

1. Finds dead code and removes it 2. It converts nodejs code that isn't compatible with the browser into browser code 2. It converts JS code that isn't compatible with nodejs to nodejs code

It tries to always make things work both in nodejs and browser js.

One example is the optional chain syntax which doesn't work in nodejs but works in the browser. FJB converts it to something that works everywhere.

I'm planning to make the typescript support an optional feature, so that one could integrate something else.

We will see.

Anyhow, appreciate your feedback.

Thanks for the tip, will make sure to fix this

Hey!! Great to see you here ;)

Yes that docs page is actually auto generated from the github README, and it doesn't convert the links to anything appropriate