i know that your training in the greatest programming language #golang gave you an instinct for making use of implicit things instead of forcing constantly to use explicit statements... it is the same with websockets... you can just trust that it was received if it was not timed out, the whole point of TCP, in fact, is all about eliminating this double checking from having to be done at the application layer
and also the way you designed the main protocol envelopes, making use of the ordered, non-set property of json arrays, this bamboozled me at first with the # prefix for the tags but why add a [], when you don't need to, or set up complicated logic about when you wrap it or not wrap it - it's just like the terminal variadic in Go function parameter tuble syntax (and ironically, a smart contract language called Move, based on Rust, literally rips off Go parameter/return and assignment tuple syntax, and rips off numerous other great features of Go that i don't feel utterly raped by Mozilla to use it
Showing page 1 of
1 pages
