Comments

SecretSoftware wrote:

Why does C++ even exist? Why does MS keeps maintaining such a language that caused so many buffer overflows, and generally was not as secure as C# or Vb.NET.

Try writing a device driver some time, or say, a video game. 

Yes, us C++ devs should just shut up and get to the back of the bus (and keep using VC6, who needs updates!  I mean, improving standards compliance and new features are so confusing to us poor old C++ developers.  We're dinosaurs, I swear, if it wasn't for C++ I'd still be doing COBOL...)

staceyw wrote:


Those scientists are just keeping the research dollars going.  I frooze my *ss off this winter till April/May.  Maybe it is reversed.  But then they need to modify the research.

Of course, you realize that global climate change can mean different things for different areas.  But it is a solid fact that the average temperature is rising.

In this situation, forget about global warming.  They're saving money!  Being green saves green.  In more ways than one, really, as preventing climate change will save more money in the long run than not.

JoshRoss wrote:



DoomBringer wrote:  Nice timing, since I'm writing a plugin for outlook... (btw, which can really, really suck at points!)

It is far more difficult in Outlook to learn the object model, by tinkering, than it is in Excel.  With Excel, you can record a macro, change some of the code, and run it. That process of interaction is very powerful.  There is simply no comparable approach in Outlook.

There are many ugly parts.  I've pulled many hairs out.  But I have learned much.

Nice timing, since I'm writing a plugin for outlook... (btw, which can really, really suck at points!)

Oh man, this brings back the memories of working on CICS.  COBOL!  JCL!!  OMG!

Who was the off-camera voice asking questions?
Also, yell at those other people who were banging around.

All that managed stuff is nice, but has anything been done in native code (this is me commenting without watching the video)?  I just finished a whole bunch of WM5.0 native code (there are several reasons for this...) and was curious.

:O

I've seen the hard disk failure thing already.  It was useful, but the backup process it tried to launch wasn't as slick it could have been.