Question: Current state of goja vs v8?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
I remember seeing bud on HN and I'm happy to see that you are still working on it!
I go a recent interest into JS runtimes and I have read a lot of your issues/discussions in other repos (v8go, goja...).
I would love to hear your insights and experience about the pros and cons of v8 vs goja.
From what I understand, v8go is posing many problems (CGO, big binaries, `libstdc++`, no binaries for windows,...), so what is missing from goja to switch?
Cheers
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the project's current JavaScript runtime choice and the referenced goja and V8 integrations, then summarize their trade-offs and identify what would still be needed to switch; done means a clear maintainer response to the comparison question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100