Out dated

[joeblew999]

Is there a reason the code is so old ? Just wondering since the web API is a living standard and I wanted to use this to build WASM based web apps but am worried it’s missing certain things .

Thanks 🙏

[janpfeifer]

hey @joeblew999 , it is indeed out-dated.

I was using it a lot a few years ago and helped with a couple PRs. But I assume it's lacking a maintainer.

Btw, it is still working though. Just last month I quickly coded a Hive in Go (demo) using it (github.com/janpfeifer/hiveGo ).

[joeblew999]

hey :)

appreciate all this. I will have a look at Hive demo now.

I did a bit of research into how you are generating off the WebI. I saw how complex it was. I was thinking about how we could use W3C ( or whoever it is now ) repo and generate all the way up from their DSL.

Is it a bridge too far still ? Boiling the ocean too maybe.

I am working on a Service worker with web workers inside. Using golang and tinygo to get to wasm.
These mini workers then talk to the DOM etc.

Let me know how nuts this is and if I am boiling the ocean on this... Maybe there is enough in the current webIDL to do what I need to do ....

[janpfeifer]

So I never contributed or read the code that handles the IDL (reading the spects and auto-generating the code) -- it is indeed a bit complex.

But I think this is the right approach to create an API to the DOM and all web standards to a Go WASM environment.

Whenever I used it, it was simple to find how it was done in Javascript and then translate to the exact equivalent in Go. I even used WebGL with it in another project (animating thousands of stuff with decent fps).

If you want to brave it, your are most welcome 😄

[joeblew999]

I just wanted to know if you had a pipeline that worked for the generation layer .

Since it’s real working it would be a hell if a job .

AI could write something like that very quickly based on the code you have though . Food for thought