Thread: D language?

I just typed www.dprogramming.com into my address bar and guess what I got - the D programming language!

Originally Posted by Mad_guy

Would you also advocate the use of wood to build skyscrapers and say that steel isn't needed, people just need to learn how to "build things better"?
Didn't think so.

Those extra features doesn't make the program "stronger", I think performance is close to stronger than "repairing the skyscraper every day". Anyway, let's cut the crap - we just have different opinions and that won't change anyway. Let's concentrate to the meaning of this thread - enterntainment.

Originally Posted by maxorator

Those extra features doesn't make the program "stronger", I think performance is close to stronger than "repairing the skyscraper every day".

So... You'd rather run really fast and do it in a shakey, non-reliable manner (you might not even get to the finish line, mind you) than go somewhat slower and be correct? Be composable and extendable? I fail to see how being wrong helps anybody, regardless how fast you come to the conclusion. I'd rather have my program spend an extra 5 seconds doing something internally with the runtime (GC, proper thread synchronization using STM, etc) than just leak memory, have a deadlock or just crash. I'm pretty sure the people who use my program would feel the same way.

I'll agree to disagree at this point, but I still wonder why you would rather go fast than be a little slower but be more composable, reliable and modular. Speed is not the same as strength.

Originally Posted by Mad_guy

So... You'd rather run really fast and do it in a shakey, non-reliable manner (you might not even get to the finish line, mind you) than go somewhat slower and be correct? Be composable and extendable? I fail to see how being wrong helps anybody, regardless how fast you come to the conclusion. I'd rather have my program spend an extra 5 seconds doing something internally with the runtime (GC, proper thread synchronization using STM, etc) than just leak memory, have a deadlock or just crash. I'm pretty sure the people who use my program would feel the same way.

First debugging... then testing... then testing again... then releasing beta version. Just a hint. I know what you're going to say (that it still may have some mistakes AND/OR that some time of developing could be saved not doing those things) and then you know what I will say (that a long process like that will definitely catch every critical bug AND/OR though it runs, the bugs will probably cause the program to behave not the way it should). Why? I mean why bother saying that? We know what the other will say, we know what are our opinions. Let's just enjoy ourself and have fun.

Any comments about the D language?

I found it useless for my needs.

I kinda fell in love with C++, ya know and as such fail to see why should I get a blonde if the brunette I love so much can paint her hair. Besides the blonde I get is not as good as the brunette I have.

This to say what I said last... D offers nothing that C++ doesn't offer already and it doesn't have the history, support and user base that C++ benefits from. Regardless, as a programming language I never cease to be amazed at those behind its development and respect them for their knowledge and capabilities.

Originally Posted by simpleid

what kind of girl would you say assembly is?
:-D

Assembly is a robot. It does what you tell it to do.