"Nick Sabalausky" <[email protected]> wrote in message 
news:[email protected]...
> "Xavier" <[email protected]> wrote in message 
> news:[email protected]...
>>
>> "Nick Sabalausky" <[email protected]> wrote in message 
>> news:[email protected]...
>>> "Jonathan M Davis" <[email protected]> wrote in message 
>>> news:[email protected]...
>>>> On Saturday, September 17, 2011 01:53:07 Nick Sabalausky wrote:
>>>>> People who are *good* at C++ are hard to find, and even harder to 
>>>>> cultivate.
>>>>> And that's never going to change. It's a fundamental limitation of 
>>>>> the
>>>>> langauge (at least until the Vulcans finally introduce themselves 
>>>>> to us).
>>>>> But D's a lot easier for people to become good at.
>>>>
>>>> It's a _lot_ easier to find good C++ programmers than good D 
>>>> programmers,
>>>
>>> Oh, definitely. But what I meant was that good D programmers can be 
>>> cultivated. People can learn to be good at D. And while the same 
>>> might *technically* be true of C++, the curve is so steep that it may 
>>> as well be "what's out there is what's out there". It's, more or 
>>> less, a non-renewable resource.
>>
>> It's not nearly as "steep" as it used to be, for C++, the tools, the 
>> techniques, the documentation, the users have matured and one need not 
>> struggle through everything on one's own anymore while learning it, 
>> but rather just go look up or ask for the answer, and it is still 
>> improving. Sure, if one exploits every "stupid template trick" and 
>> similarly with the other language features, then you will have 
>> "steep", but it is quite tractable these days if one isn't overzealous 
>> and able to separate all the jabber about "metaprogramming" and the 
>> like from the meat of the language. It will always have its warts, but 
>> D has many of the same ones.
>>
>
> In other words, "C++ is easy^H^H^H^Hless hard than it used to be, as 
> long as you don't use any of the advanced features that are already 
> trivial in D anyway."

No, but rather that most programmers don't know how to program yet and 
they think they need those things all the time.

>
>
>>> I realize I've said this other times in the past, but I find that the 
>>> compiler bugs in DMD are much less severe than the language 
>>> deficiencies of a fully-bug-free C++ implementation.
>>>
>>
>> That's an interesting, if not odd, statement considering that C++ are 
>> more alike than they are different.
>>
>
> I don't understand what you're saying here. Did you mean "D and C++ are 
> more alike than different", or "C++ implementations are more alike than 
> are different". Either way, it doesn't make much sense.

The first one.

>
>
>>> Plus there's the idea of investing in the future to keep in mind: 
>>> It's like the old quote: "I may be fat, but you're stupid. I can 
>>> excersise and diet, but stupid will always be stupid."
>>
>> The truth of the matter is, though, that she won't exercise to any 
>> significant degree and has been on a diet her whole life and her 
>> weight has continually increased. On top of that, the fact that one 
>> can study, research and learn escapes the fat dumb blonde bimbo 
>> because she indeed is stupid, and that's why her "dieting" causes her 
>> to gain weight instead of lose it.
>>
>
> You've just completely broken the analogy because D's bugs *DO* get 
> fixed. And they're getting fixed rather quickly now, too.

To be honest, I was just spouting on, and having fun with, the phrase and 
not it's applicability to anything in this thread.

>
>
>>>  D may have some bugs, but investing the effort to deal with them 
>>> will lead to further improvements. Dealing with C++'s problems, OTOH, 
>>> will hardly do a damn thing.
>>
>> Again, I find that a curious statement for reason noted. The language 
>> names even fit together: C/C++/D. There is no denying that they are 
>> all related. Just look at those noses! C'mon!
>>
>
> Umm, yea, they're related. So what? Don't tell me you're trying to 
> imply that just because they're related they're inherently equal in 
> everything but implementation.

Ah, see now you're backing down. Now you are just trying to prove 
unequality rather than significant difference.

>
>
>>> Sure, a few things can be mitigated somewhat, such as the 
>>> C++0x^H^H1x^H^H2x^H^H3x improvents. But in general, investing the 
>>> effort to deal with C++'s shortcomings won't lead to significant 
>>> improvements - it *can't* because it's constrained by its existing 
>>> legacy design (not that that won't eventually happen to D, too, but D 
>>> is one generation past C++).
>>
>> One generation away, but still the same family. So what?
>>
>>>  Ie., D may be buggy, but C++ is crappy. Bugs can be fixed, but 
>>> crappy will always be crappy.
>>
>> All adolescents conflict with their parents and say things like that. 
>> When D grows up, the D++ or E kids will be maligning D and then D will 
>> remember back how it was just the same when it was just a youngster.
>>
>
> Are you seriously trying say that that implies each successive one is 
> inherently no better than the previous?

I was alluding to the fact that you are overstating the significance of 
the difference between the two languages. That is to say that the 
differences are rather "cosmetic" more than they are meaningful. Oh, in a 
few areas, sure, there are differences, but overall, "same old stuff".

>  If so, then that's just patently absurd. If not, then what in the 
> world *is* your point? Just to troll?

>>>>
>>>> I definitely prefer D to C++, but I honestly think that your hatred 
>>>> of C++
>>>> (which you have expressed on several occasions) clouds your 
>>>> judgement on the
>>>> matter.
>>>
>>> FWIW, I had been a huge fan of C++ for many years and used it 
>>> extensively ('course, that was quite awhile ago now...). And I *do* 
>>> think it was a great language back in it's time. I just think that 
>>> time is long since past.
>>
>> I think C++ is now coming into it's own and it sucked in the past much 
>> more. D is now in it's sucky period IMO, and may have it's day in the 
>> future. Time will tell.
>>
>
> Well, like I've said, I'd rather something with better language design 
> and a few implementation worts, than something with inferior language 
> design and perfect implementation.
>

Yeah, yeah.. OK "fan boy". ;)

>
>>> When I say "C++ is crappy", I mean "within today's context, and 
>>> moving forward from here".
>>
>> Tomorrow is surely something else, probably not D, IMO, but today is 
>> all C++.
>>
>>> I'm certainly aware of all that, and I do understand. But the 
>>> question here wasn't "Do you think OTHER people feel language X is 
>>> suitable for serious work?" It was "Do YOU think language X is 
>>> suitable for serious work?" I don't doubt other people would disagree 
>>> with me (especially people who haven't used D, and even probably some 
>>> who have), but my own answer is "Yes, I think D is suitable for such 
>>> projects, and in such a situation, yes, I would be willing to put my 
>>> money where my mouth is."
>>
>> Ha! I inadvertently just answered those questions. Well, I guess you 
>> know what I think now (not that I was going to hide it).
>
> You mean that you're just here to troll?
>
>
> 


Reply via email to