Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Are there any plans to have a package for Golang? (I'd love to help with that too) #506

Open
dhanielsales opened this issue Dec 18, 2024 · 5 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@dhanielsales
Copy link

Hi there,

First, thank you for starting work on Limbo—it sounds like an exciting project!

I was wondering if there are any plans to develop a package for Golang? If such a package isn’t currently in the roadmap, I’d be thrilled to contribute to making it happen. I have experience in Golang and would be happy to collaborate. Let me know if this aligns with your goals for the project and how I could get involved.

Looking forward to your thoughts!

Cheers

@penberg
Copy link
Collaborator

penberg commented Dec 18, 2024

Hey @dhanielsales, we absolutely want Limbo to be packaged for Go, but I am not aware of anyone actively working on it.

As Limbo implements a subset of the SQLite C API, https://github.com/mattn/go-sqlite3, for example, should be straight-forward to port.

Of course, some Go folks dislike cgo so much they did:

https://github.com/ncruces/go-sqlite3

Curious to hear from you and other Gophers what's the best strategy to make this happen! And absolutely happy to take contributions here either in bindings/go or as an external package!

@penberg penberg added enhancement New feature or request help wanted Extra attention is needed labels Dec 18, 2024
@Tejasmadhukar
Copy link

Tejasmadhukar commented Dec 18, 2024

Hello there, building this project would be awesome!

Here is a benchmark for different sqlite3 drivers in go - https://github.com/cvilsmeier/go-sqlite-bench, this includes both cgo and pure go drivers along non database/sql drivers.

There is not a clear winner, this design choice/decision would be upon you.

The only thing I would like to add is the obvious fact that it would be better to have this as database/sql driver as it's defacto in go and would allow for drop in replacements in most projects.

Looking forward to hearing your thoughts and to work on this!!

@PThorpe92
Copy link
Contributor

I'm on team avoid CGO, and I would likely contribute to this as well 👍

@dhanielsales
Copy link
Author

Yeah, I'm on avoid CGO team as well, so cound on me to help with it!

@nikoksr
Copy link

nikoksr commented Dec 21, 2024

+1 for pure Go. Package management and distribution is much smoother without cgo dependencies in my experience. Happy to chip in on the implementation!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants