iodide-project / iodide-project/iodide
Feature Proposal: Golang Support
- Dominant language
- JavaScript
- Stars
- 1.5k
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Description
_I'm sorry if this is the wrong place for this._
## Do you think Golang has the potential to become a decent data science framework if you have access to a GUI/DOM, and some decent data science libraries and/or frameworks?
### I think people may be more willing to develop after a decent GUI is developed. Also, Golang may not have the flexibility of Python, but it is a few dozen times faster (in most use cases).
---
I was thinking that the interface for the GUI would be simular to that of Pyodide.
#### Potential Issues (off the top of my head):
I did see that the Golang compiler binary is even bigger than that of Pyodide, but I think if you remove all build targets except for WASM, you may be able to reduce it's size. You would also need some virtual filesystem for packages, but I heard [Emscripten has filesystem support](https://emscripten.org/docs/api_reference/Filesystem-API.html). Hopefully JIT compiling for Golang (maybe with cache) wouldn't take too long in WASM. Golang is statically typed so interacting with JS and the DOM may be hard.
Contributor guide
Research direction
The issue does not name repository files, tests, or entry points. Start by reviewing the existing Pyodide-style interface and WASM-related architecture, then assess whether Go can provide GUI/DOM access, package filesystem support, and practical compilation performance. Done would require an agreed implementation scope rather than only a feasibility proposal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, wasm
- Domain
- data, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100