Whenever people talk Go's "readability", I can't get over how every line of actual code is buried in an additional 3+ lines of redundant error handling boilerplate. "...but you get used to it!" is the counterargument, and one I think can be used to justify anything as "readable"
-
-
-
If you actually add some valuable context and not just "return err", it makes a lot of sense. I like it, because the control flow is so explicit.
- 7 more replies
New conversation -
-
-
Code produced by async/await can be less performant. At least in Rust, async/await produces a set of enum variants that requires runtime matching. Memory based "trampolining" is common in manual future code & there's no runtime overhead. This matters *sometimes*.
-
But match often compiles into a jump table, no?
- 2 more replies
New conversation -
-
-
In my day, we had 10 IF INKEY$ = "" THEN GOTO 10 and we liked it
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
A state machine encoded as a transition table might be the most easily verifiable and interpretable software specification of all.
-
Yeah I was gonna say
End of conversation
New conversation -
-
-
If there's any benefit to the latter it's the ease with which you yourself can serialize/see the state if you should need to, with async/await it's all opaque. Not that this is usually a concern when dealing with like web stuff but state machines in general (games for instance).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
People are scared of abstraction until they understand it and learn to trust it
-
Abstracted: people are afraid of anything that they don’t understand and trust.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.