# Jordan perspective
## wasmcloud-go
liked the name
How Jordan figured out what to do:
Main page, Capability Providers from Spec
treated Host reqs as checklist
"Don't do the security"
Doesn't remember why he did it, 1 year ago
Go port for connecting to the lattice
Then examples is poor man's wash
No tags right now, add tags
Bespoke, nkeys
Forked, edited and made it wasmcloud Friendly
Host key and stuff
Nats can be run within the binary
in NATS slack, not documented
If you set the port to 0, it'll use pipes vs network stack
Giant thing of topics, nats subscribe
lots of not implemented pieces on the subscribe
actors with random key
wascap stuff here. AKA not checking claims
archive config doesn't have jwt, confused by it
Doc is fantastic
echo is the rust impl of the echo actor
Deserialization issue
Interfaces for Rust and Go need to stay in sync
Core interfaces for rust are managed with weld
msgpack Rust
Go is not getting updated at the same cadence
Code generation is actor specific
So when generating for providers, you get actors and don't need it
wasmcloud-go/examples/cli
claims ls
"poor man's wash":
- elixir wash running there
- wash ctl post get host
## wasmcloud/interfaces/tinygo
Get a deserialize error
Biggest SDK
We have to get deserialization in sync
weld #134
Code generation is actor specific
So when generating for providers, you get actors and don't need it