-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Golang working group / Gnolang 1.x #15
Comments
For reference, golang/go#33702 to have deterministic execution in Go. |
Let's create a newsletter featuring the latest updates, including both successes and challenges, and current progress (possibly quantified by percentage). This newsletter will also highlight ongoing obstacles and propose future concepts. It will comprehensively cover our Go interpreter projects: gnovm, gnors, parscan, and possibly yaegi. This will be a straightforward engineering-focused communication, free from marketing. We plan to share these reports regularly on Gopher Slack, Twitter and Reddit, allowing interested individuals to discover, engage, and potentially contribute at their own pace. Additionally, we'll craft a technical blog post to introduce this newsletter initiative. It will reiterate our challenges and our vision of developing an interpreted Go language, not just for blockchain applications, but also as a competitor to Python. |
Who writes this newsletter? Is it a rota of the engineering team + devrels? Is this endeavour not very closely related to The More You Gno? Would it replace/evolve The More You Gno? |
Here are some relevant links and discussions regarding Golang initiatives we could engage in:
go2gno
andgno2go
)Things we consider for post-release versions of Gnolang (Gno1.x)
gno2go
similar to CoffeeScript/TypeScript and generate good usage Go codeThere is a meta issue on the main repo that could help a lot addressing all those topics, see: gnolang/gno#972.
The text was updated successfully, but these errors were encountered: