Skip to content
This repository has been archived by the owner on Oct 3, 2022. It is now read-only.

Question: Choice of Rust over Go #1330

Open
ECHibiki opened this issue Aug 2, 2022 · 2 comments
Open

Question: Choice of Rust over Go #1330

ECHibiki opened this issue Aug 2, 2022 · 2 comments

Comments

@ECHibiki
Copy link

ECHibiki commented Aug 2, 2022

Three questions:

  1. I'm wondering why you reduced the usage of Golang in the project and instead are doing a horizontal mix of Golang, Rust and NGINX?
  2. What issues were you resolving that could not be handled by Go?
  3. I've considered the hypothetical of using Go with Rust bindings in HTTP imageboards and might experiment with it one day, would that have been an option in your opinion? Though maybe one should just go to CGO instead of tinkering around with strange ideas... the third question could be said as "why did you not use Go Bindings if one of your reasons was better performance?"
@bakape
Copy link
Owner

bakape commented Aug 3, 2022 via email

@ECHibiki
Copy link
Author

Thanks for the response. I will keep Rust in mind for any socket related expansions, Golang has it's limitations though it's a very useful language.
In my opinion imageboards, contrary to the liveboard, require instant-messaging or traffic goes offsite into IRCs or discord: Places where the more drawn out style of posting is less preferable to a fast paced environment.

Your information is helpful in future planning.

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

No branches or pull requests

2 participants