Hey, John. Sorry, random bug spot: at 3:14 or so, there's an extra return on line 15 that means the function can't ever execute successfully. (It's a good example of how the volume of error-handling code can allow bugs to creep in. ;-) ) I hope everything's going okay with you.

Thank you so much for sharing your wisdom. It's very much appreciated.

From my experience C++ isn't much harder to write than java if you do it right. In most cases you don't need to use pointers. You can just instantiate objects on the stack and use move() and references when needed. In case you do need to use pointers, you can always use smart pointers.

Rust brings the best of both worlds: the avoidance of garbage collection, but without needing explicit de-allocations, just by controlling ownership of variables and dropping (de-allocating) them automatically when not used anymore.

Thank you john, this is an important one and as usual the long-hands on experience reflected on this controversial subject in a way that begins with the real world while noticing how things move in history (i think mentioning moving from a position where resources were limited to the current state where there are resource-rich environments is an important insight), this is the first time i know you also reached to work with OSs, if anything to suggest here is shedding light on the terms appeared in the video (perhaps in an exclusive way without going in-depth - memory management, resource allocation, garbage collectors ..etc.), this is because there are people capitalize on deliberately obscuring these things, i get confused whenever there is a discussion about why we should switch from X-lang because of memory management, or how X compiles, or type safety (and i know some of these topics are crucial, and some of - like what we saw on this episode- have a specific context), at least what you think make important research topics for building commercial-grade software (from a programming language/operating system point of view) . As usual thank you john for the great insights, and have a nice day !

I think the comparison is fair, I think I typically reach for garbage-collected languages first because of the productivity. I think you hit the nail on the head about productivity, testability, and how modern hardware is less resource-constrained. I think like most things in our world the answer is "It depends" which isn't really the most satisfying thing to most people these days because that implies there's nuance and people want "Yes or No". I tend to reach for something else when latency is critical and resources are more constrained. Although these days with where my career is currently, it tends to be exclusively garbage collected. One other interesting thing that could be covered is some languages, I know specifically Java for example allow you to call out to external native libraries (Foreign functions) written in other languages. I've written Java applications before that use JNI for near-hardware type things (One example that comes to mind is an application I worked on that used JOGL for rendering), so you can get some of the best of both worlds.

I will say as a C++ embedded dev that modern post-2011 versions of C++ completely stopped the need for new and delete for that reason you listed, even in a resource constrained environment the modern features of smart pointers and Rule of 5/RAII seem to solve that. Really there are issues with modern C++ but a lot of that has to do with backwards compatibility or confusing newer features. The biggest weakness is the build system/package management. Java is fast enough in most cases and was better for backend stuff especially compared to pre-11 C++, but now I find Java does not have the web advantage. It's easier to do most web stuff in JavaScript and mix that with whatever your team needs/is comfortable with in my experience. 👍

What do you think about Cython as alternative of Python? As far as I know, cython is as fast as C++ and easy to be compiled from pure python code. So I think Cython has two advandates: Easy implementation and Fast running time. What do you think? (I am just junior developer so my explanation should be not correct)

i prefer C++. here's why. harder language --> more talented people. aka. your peers are going to be smarter and you'll benefit from that. better performance --> why bother sacrificing performance when you don't need to. just work around it and get better. control --> you're better off just writing longer code. it doesn't matter if it's harder, just learn it and get over it. if not, you'll have your smarter peers to help you out. just my 2 cents. don't bother with gabage collected language. you're better off just sticking with something faster and something with smarter people writing it.