This is actually a great technique for programs that do a task and terminate where big-O for peak and total mem usage are the same.https://twitter.com/qwertyoruiopz/status/815711346323058688 …
No matter how smart you are, writing unnecessary, and unnecessarily complex, code is an unjustifiable risk.
-
-
I agree code is a liability; that still hasn't stopped us from pretending that external code "just works" and creating >>
-
increasingly complex projects where everybody working on it only knows how their portion works. Something's gonna give soon.
-
Pretend the phones are programmers, each only familiar w/ their own section of code: https://en.wikipedia.org/wiki/Network_effect#/media/File:Network_effect.png …
-
(GC in particular is one area where the only ppl who understand it in any appreciable detail are those who research it :/)
-
Basic GC algorithms are quite simple though and are useful in contained use cases too not just for GC languages.
-
It's not that complex / large in the context of the rest of a programming language implementation and is reused.
-
Also, GC isn't just used in memory. It's used by filesystems, databases, version control systems, etc.
-
Not usually quite as complex as the in-memory concurrency semantics but they often still need to cope with those issues.
- 23 more replies
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.