It's just too goddamn easy to make a mess in C++ without noticing it. In C, if you make a mess, you will more likely notice it before it's unmanageable.
648 karma · joined November 12, 2009
It's just too goddamn easy to make a mess in C++ without noticing it. In C, if you make a mess, you will more likely notice it before it's unmanageable.
I'm pretty sure that C folks are much more productive using C than C++. Hating the tools you are using tends to lower productivity to a halt.
If I were to heed that advice, I couldn't do anything productive. Heck, even as it is I'm worrying about stupid laws far too much, even though I'm not breaking any (that I know of), and it's taking time away from my productive behaviour. Your argument doesn't hold water in an environment where there are many, many stupid laws.
I used to program in Haskell for fun and school and I liked it. I find it very well thought out language. I may very well come back to programming in Haskell when I encounter a suitable project.
But there is a tendency among Haskeller's to get too caught up in praising purity and laziness, while ignoring the nice practical aspects of the language that could enable it to rise to be an even greater language.
I'm not saying that author is guilty of this, this is just a general observation. And I must admit that I'm not quite up to date of what's up with Haskell. My point is that Haskell is great for reasons other than purity and laziness, too.
The compiler is slow as fuck to get started and the syntax of the language is such that whitespace appears to matter. No thanks.
But I wish y'all good luck anyway.
Apple is the hip and cool thing that your artistic cousin uses, whereas Microsoft is the lame and boring thing that the enterprise uses.
Between these two stereotypes, what would be the image you would market to in order to turn huge profits like Apple is doing? I have no idea, and I think it would be unwise to just imitate Apple, they have more experience being Apple than anybody.
Implementation details largely determine how fast a given program will run.
C makes it rather easy to predict how fast a piece of code will run, and what its bottlenecks will be. Lisp makes that rather hard.
Given that there are always programs that need to be as fast as possible even with hand-optimized algorithms running on top-of-the-line hardware, C will win for many applications that have even moderate performance requirements.
Also, current mainstream operating-systems favor C and C++, if only implicitly.
(It's common misconception, and a confusing name)
In other words: the beginning of the learning curves of Lisp vs. other languages are about the same. Lisp's curve just continues after that.
It's perfectly okay to use Lisp just like you would use any other language.
It's better designed and more consistent than most others, and has good implementations. It makes sense to use Lisp as just a regular language without any wizardry.