Hacker News new | past | comments | ask | show | jobs | submit login

Message passing within a process and function calls are exactly, precisely isomorphic, so complaining about one or the other is just parochialism.



Smalltalk and Common Lisp are on my favourite languages list.

Yet I never got the point of arguing about implementation details regarding virtual method dispatch versus message passing.

Specially when many OOP GUI frameworks combine both approaches.


It's not even an implementation detail. Both use, ultimately, JSR and RET instructions.

It really comes down to fetishism, which is why I don't use either of them. I am not a Fetish-Oriented Programming enthusiast.

It is also why I am not all in on Rust. Memory safety is pretty important, but it is far from the only important thing in programming. The amount of attention Rust insists I devote to it is attention I don't have available for the other things that, frankly, deserve it more.

Considering that in the last 10 years I have spent strictly less time debugging memory usage errors than preparing compiler bug reports against Gcc, putting memory correctness guarantees front and center ahead of all else seems to me a mis-allocation of my extremely scarce attention.

Attention is by far the scarcest resource available to any programmer. Allocating and applying attention where it is most needed is the central problem of programming. A language that overrules your judgment as to where your attention must be thus interferes with the core business of programming.

C++ does demand just a little more attention to memory management than some other languages, but less all the time. It pays that back by eliminating most taxes on performance, a swap I agree to.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: