I don't get the point of this article.
All it did was cover some C standard library functions and say that what a GC does is manage the memory lifecycle in languages like Python.
What did other people take from this?
All it did was cover some C standard library functions and say that what a GC does is manage the memory lifecycle in languages like Python.
What did other people take from this?
It covers pointers/addresses, what they are, the notation for declaring them, finding the address of variables/functions, how they're represented, and how to dereference them. Then the stack and the heap, and how memory is allocated/freed on both.
It's a primer on the important concepts, if you've only ever worked with languages that abstract those details away (e.g. python/javascript).
And, giving it a bit of a skim, it looks like it does an OK job of that. (But I'm not a beginner there, so what makes sense to me might be taking overly large steps for actual beginners in some places.)
¯\_(ツ)_/¯
I don't understand that implication that this is somehow not enough to warrant existing in writing (i.e. that there is "no point").
I have talked to full stack devs that don’t know what the stack and heap is, they think I am talking about leetcode data structures.
This is a beginner article for sure, but I think that’s the point
For python, I believe a correct use of mmap for large files (ex: pickles) could offer a lot of advantages.
This was seen recently with the orders-of-magnitude increase in performance for the several hundreds of GB worth of weights, it might extend to other languages.