Conversation

Stuff like avoiding data races, nils behind interfaces, the way it represents potentially erroneous data using pairs as opposed to disjoint unions, remembering to check for errors, how you need to be conscious of default values and data initialized in an invalid state…
1
1
Yeah, it's pretty obvious that the designers were coming from a C perspective and their threshold was quite high too. Just hoping people learn over time that programming doesn't need to be this janky. I think that's happening, but it's a slow process. 😅
1
Show replies