mleku on Nostr: none of this needs to be understood to write reasonable Go code it's only really when ...

none of this needs to be understood to write reasonable Go code

it's only really when you start shuffling large amounts of memory that Go's GC fails to work in your favour and you need to start to look at schedulers and buffer freelists

c++ boost libraries are a constant breaking change party that never stops, and c library versions don't seem to be much kinder but at least they are a bit slower moving

if your task is analytics, you want simple languages, that's why most mathematicians just use mathematica, but if your data crunching is memory heavy you need an efficient language and preferably binary not interpreted (or at least VM based)

C really is mainly for fast performance and low level systems stuff, and anyone who tells you that you need to understand OOP garbage to write systems code is just straight up lying because windows, mac and linux kernels are all written in C, not C++, for a reason (that being unintended complexity)

i wish OOP would just die, it was a dumb idea that Jobs and Gates got hooked on because of Smalltalk and it was possibly the least performant model possible for GUI programming, structural typed and concurrent sequential processes are much more simple to reason about and compile for these same purposes (i used to be an amiga user as a kid, and it pained me so much that a C compiler and the manuals cost more than 2x the hardware)

it was just an accident of history that ONE GUI development project that both apple and microsoft's CEOs went to check out at Xerox used an interpreted OOP language and now we all suffer from this eternally