Content
@
0 reply
0 recast
2 reactions
Haardik
@haardikkk
websocket servers in nodejs are a sin
1 reply
0 recast
6 reactions
Gabriel Ayuso
@gabrielayuso.eth
I'd argue that all nodejs servers for more than just a toy app are a sin. (Even though I work on one lol) Bun seems like a promising solution for folks that want to stay in JS/TS land. I'd still chose something else though.
2 replies
0 recast
4 reactions
Tayyab - d/acc
@tayyab
What would you use instead? Feel free to specify a small handful based on use cases, if "depends". Working on side projects and might be good to try my hands at a few thing
1 reply
0 recast
1 reaction
Gabriel Ayuso
@gabrielayuso.eth
I'm a big fan of Go since it's great across the board, regardless of use case. In the rare case where you need to squeeze as much performance as possible then languages such as Rust, Zig and C/C++ will do. I've never used it myself but if I were to start a backend focused on real-time and websockets then I'd try Elixir since it seems to be the best for that. Scala might be another good option if your servers are always on since JVM has a cold-start problem but given its learning curve, I might as well just use Rust instead.
1 reply
0 recast
2 reactions
Tayyab - d/acc
@tayyab
I think I saw somewhere that Merkle uses Nodejs for its web api. Do you guys also use Go and or other languages across different services?
2 replies
0 recast
1 reaction
Gabriel Ayuso
@gabrielayuso.eth
We use TS for everything Warpcast except for some Python for ML. For Farcaster, Snapchain and parts of Hubs use Rust.
1 reply
0 recast
0 reaction
Haardik
@haardikkk
Hubble is node, but new snapchain being built is rust
0 reply
0 recast
0 reaction
