Programming languages without garbage collection send us down a long path of design decisions that lead to slow compile times and fragile runtime performance cliffs.
-
Show this thread
-
Replying to @TimSweeneyEpic
I've been on the other side, using Bohems GC jacked into C malloc and IMHO it was a big design mistake to use it. We are now chained to slow performance, poor caching, random drops in perf. due to mem scans and memory retention.
2 replies 0 retweets 0 likes -
Replying to @JimmiesCrowns @TimSweeneyEpic
Once the GC was put in, the pattern has spread in the sys and is now basically impossible to remove. GC is a bad crutch for devs who dont know other, better memory management options and should be avoided at all costs.
3 replies 0 retweets 2 likes
Conservative stop-the-world-and-scan-all-memory GC carriers a much heavier cost than other methods. ARC and concurrent GC are much more reasonable, but require pointer abstractions rather than just using raw pointers.
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.