C++ - The Forgotten Trojan Horse
ejohnson.blogs.com
C++ - The Forgotten Trojan Horse
1–10 of 40 posts
Re: C++ - The Forgotten Trojan Horse
#2Re: C++ - The Forgotten Trojan Horse
#3Re: C++ - The Forgotten Trojan Horse
#4http://thread.gmane.org/gmane.comp.version-control.git/57643...
Re: C++ - The Forgotten Trojan Horse
#5Re: C++ - The Forgotten Trojan Horse
#6Linus Torvalds thoughts on C++: http://thread.gmane.org/gmane.comp.version-control.git/57643...
Re: C++ - The Forgotten Trojan Horse
#7http://yosefk.com/c++fqa/defective.html
The rest of the FQA site is good too, but the summary is the best enumeration of all the brain damage.
Re: C++ - The Forgotten Trojan Horse
#8Look at all that comment spam. How lovely.
Great post, but the comment spam shows that this site isn't very well maintained. Clearly the author hasn't spent much time on it in a long time.
Too bad.
Re: C++ - The Forgotten Trojan Horse
#9This is the same strategy that Clojure is now using, which is why it's the only LISP that has any chance of going mainstream.
It does use the Java virtual machine, however, which allows it to use existing java libraries.
Re: C++ - The Forgotten Trojan Horse
#10Always useful reading for anyone who thinks C++ is great and can't understand all the curmudgeons who think otherwise: http://yosefk.com/c++fqa/defective.html The rest of the FQA site is good too, but the summary is the best enumeration of all the brain damage.
It helps to remember, that C and C++ don't exist on an "VM island", i.e. as an isolated process, like all high-level programming languages do. They are effectively extensions of UNIX-derived operating systems, i.e. they run under "UNIX VM". They even have a garbage collection of sorts: when you exit the program, the memory gets freed. And, according to Linux philosophy, launching processes or forking/dying should be quick, efficient and, in fact, desirable. Also, having many independent binary modules is the norm, so here is your runtime encapsulation.
But C family is still the only tool out there that allows you to extend an OS, i.e. for instance to build a piece of code, a single instance of which will be serving all other simultaneously running processes. This explains why Apache eats so little RAM. None of VM-based languages can do that. It's called systems programming.
Building a web-based CRM in C++ is stupid. Building a filesystem in Python is impossible.