One advantage of that kind of control is that your code does not depend of the implementation of any abstraction (except the operating system if any?) since eve

One advantage of that kind of control is that your code does not depend of the implementation of any abstraction (except the operating system if any?) since everything is written "in stone". I also think it makes a great learning tool, mainly to understand: - how a GC or memory management is/should be implemented - what pain points they solve (or: why they are important) When you don't have to think about the abstractions but only your code, it prevents the student from being confused about what happens when. But I would not use it in production, just like you said, because in production, I want to maintain as little code as possible, and delegate the complexity to other better tools/people.