# Rust vs Go for client implementations
**URL:** https://forum.pokt.network/t/rust-vs-go-for-client-implementations/24
**Category:** Research
**Created:** [September 24, 2018, 9:44pm UTC](https://forum.pokt.network/t/rust-vs-go-for-client-implementations/24 "2018-09-24T21:44:06Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@jray](https://forum.pokt.network/u/jray)
#### Post date: [September 24, 2018, 9:44pm UTC](https://forum.pokt.network/t/rust-vs-go-for-client-implementations/24/1 "2018-09-24T21:44:06Z")
Read these:
- [Rust Programming Language](https://www.rust-lang.org/en-US/)
- [Why Rust?. What is Rust language and why Parity… | by Dmitriy Kashitsyn | Parity Technologies | Medium](https://medium.com/paritytech/why-rust-846fd3320d3f)
- [Benchmarks · ethereum/wiki Wiki · GitHub](https://github.com/ethereum/wiki/wiki/Benchmarks)
Also:
- it’s compatible with Wasm now.
---
### Author:  [@jray](https://forum.pokt.network/u/jray)
#### Post date: [October 31, 2018, 3:37am UTC](https://forum.pokt.network/t/rust-vs-go-for-client-implementations/24/2 "2018-10-31T03:37:07Z")
Generally, Rust is faster and safer than Go. Rust is more complex than Go, but this complexity is worth the speed, safety, ability for low-level programming, flexibility, better suitability for large projects (which Rust can actually reduce the complexity of—e.g. the compiler does a lot of the work for you, easier to debug, etc.), and other benefits.
FMI see e.g. [https://duckduckgo.com/?q=rust+vs+go&t=fpas&ia=web](https://duckduckgo.com/?q=rust+vs+go&t=fpas&ia=web) (I read some of [https://news.ycombinator.com/item?id=13430108](https://news.ycombinator.com/item?id=13430108)).
---
### Author:  [@jray](https://forum.pokt.network/u/jray)
#### Post date: [November 5, 2018, 3:21am UTC](https://forum.pokt.network/t/rust-vs-go-for-client-implementations/24/3 "2018-11-05T03:21:40Z")
Also using Rust allows use of Parity Substrate and Wasm, with associated benefits. [https://www.parity.io/substrate/](https://www.parity.io/substrate/).