Skip to content
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

How can I help? #9

Open
ghost opened this issue Oct 22, 2017 · 2 comments
Open

How can I help? #9

ghost opened this issue Oct 22, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented Oct 22, 2017

Title says it all. I am a dev who has an interest in this side of things and alot of free time at the moment... how can I help?

@nick-korsakov
Copy link

@rucuriousyet, could you dive into the code, learn it architecture and explain it in some text file or inline here? I'm interested in this project too, but I have no much free time. My questions:

  1. What is the overhead (%) of Go layer compared to the pure C call to Vulkan?
  2. Is it full Vulkan API wrapper or it's just a minimal piece of it?

@xlab
Copy link
Member

xlab commented Oct 25, 2017

@nick-korsakov

  1. Varies from 0% to 1000%, depends on the overall workflow. It's obviously slower than pure C or Rust, but the idea is to provide much more easier methods to work with Vulkan. Go is simple to write and maintain, C is not.

  2. It's 100% full. Autogenerated from the official headers, the latest version possible. It also covers all vendor extensions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants