Replies: 1 comment
-
Probably. It may have some bugs but it's enough for playground purposes.
It can be considered. The only concern is how well it's maintained, as Go +1.21 support was added very recently and library didn't have that support for a quite long time. But I'm happy that they added a new version support.
Probably the last release before v2.0.0
Idk, but it will take a descent amount of time, considering that this isn't a full time project. Contributions are welcome. Regarding tinygo - tinygo isn't a fully Go compatible and has some quirks (reflection, etc). plus you probably need LLVM. |
Beta Was this translation helpful? Give feedback.
-
Based on your response in #460 (comment):
Q1 When you had Yaegi support, did that mean you could run entire apps in the browser (with a package main, multiple files etc) (obviously excluding features that are sandboxed by the browser), or just "scripts" written in go?
Q2 If Yaegi supported all new language features (including Generic), will you add it back in? They say
Support the latest 2 major releases of Go (Go 1.21 and Go 1.22)
andComplete support of [Go specification](https://golang.org/ref/spec)
.Q3 What is the last commit before you removed Yaegi? Is it difficult for someone like me to put it back in a fork? I'm trying to run Go applications in a browser.
Q4 If it it was just you, how long do you estimate it would take to port the Go compiler to WASM? What about the tinygo compiler (which now has a simple garbage collector)
Beta Was this translation helpful? Give feedback.
All reactions